Ai Topic

[YoDoug]

Are you gonna have it make documentation for everything once its all finalized. This would be gold!

I have been going back to our older cells. I make the same project structure, master folder, then subs for robot, PLC, C#, etc. Then I have it review all and make a skill.md doc for the cell. Then that doc can be used as a reference to make documentation. I make one complete doc. I have it start with a cell overview, then topology map of devices. Then operator instructions and troubleshooting. Then lastly IO maps and higher level maintenance troubleshooting.

I also create a Git Repo for the entire cell on our network. That way it is all revision controlled and backed up together. It also makes for easier troubleshooting. If I "get hit by a bus tomorrow" as the saying goes, Anyone else can upload that skill.md doc for each cell to Claude and get all the help they need to fix and maintain the cell.

[Zoffen]

Needed some sort of basic "Help" document describing each module in our ERP system and what other modules it interacts with. Told Claude to do a deep dive on the whole software and figure out what everything does and how each module relates to eachother. 5 minutes later I had a an interactive help form that shows all that info. This would have take me days (maybe a week because it sooo boring to do) but now took 5 minutes. Thanks C-Money.

Example:
MODULE 301 - TOOL ASSEMBLIES
============================================================

OVERVIEW
----------------------------------------
Defines tool assemblies used in CNC machines. Each TA is a combination of a holder, optional extensions, and a cutting tool with calculated projections and TopSolid CAD models.

Key Features:
  - Assembly definition: MainHolder + MainExt1-5 + MainTool
  - Tool projection calculations
  - TopSolid assembly creation (V3 and V4 methods)
  - TopSolid assembly preview
  - Batch assembly creation for all TAs
  - CAM synchronization with VF4 machine magazine
  - Add TA assembly to active CAM document
  - TopSolid methods execution
  - Assembly PDF/image viewer
  - Alternate CAM tool/holder UUID assignment
  - Favorites system
  - TopSolid availability check (disables TS functions when not running)

RELATED MODULES
----------------------------------------
  - Module 300 (Items): Holder/extension/tool components
  - Module 302 (TA Instances): Physical instances of this assembly
  - Module 302.01-302.04 (Tool Magazines): TAs loaded into machine magazines
  - Module 307 (TopSolid): CAD assembly creation and PDM storage

[megatronprime]

I have been going back to our older cells. I make the same project structure, master folder, then subs for robot, PLC, C#, etc. Then I have it review all and make a skill.md doc for the cell. Then that doc can be used as a reference to make documentation. I make one complete doc. I have it start with a cell overview, then topology map of devices. Then operator instructions and troubleshooting. Then lastly IO maps and higher level maintenance troubleshooting.

I also create a Git Repo for the entire cell on our network. That way it is all revision controlled and backed up together. It also makes for easier troubleshooting. If I "get hit by a bus tomorrow" as the saying goes, Anyone else can upload that skill.md doc for each cell to Claude and get all the help they need to fix and maintain the cell.

Have you tried azure dev ops and pipes?
You can automate your build routines so you can make updates and deploy updates from your phone, it's somehow free, that might be because of partnership, but that only costs between 0-100$ a year.