fusion-360-addin
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Guidelines and information for use when creating Addins and Scripts for Autodesk Fusion 360
In this repository12 other files it gives its agents.
- api-conventionsSkill
- csharp-styleSkill
- database-conventionsSkill
- default-gitignore-filesSkill
- git-workflowSkill
- godot-game-engineSkill
- logging-conventionsSkill
- npm-registrySkill
- postgres-styleSkill
- python-styleSkill
- typescript-styleSkill
- ui-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
If the user is ambiguous as to wheter they want a Script or Addin, ask the user
- Distinctive: line 9
Use Python as the language unless otherwise specified
- Distinctive: line 12
If Claude identifies any implementation ideas that conflict with Fusion's Addin/Script framework, it should notify the user and work to …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Guidelines
- If the user is ambiguous as to wheter they want a Script or Addin, ask the user
- Use Python as the language unless otherwise specified
- As part of any implemntation plan, Claude should provide information on what is needed for publishing to the Autodesk's App Store for Fusion 360 addins and scripts
- Claude should also think about creating documentation for the Addin during development
- If Claude identifies any implementation ideas that conflict with Fusion's Addin/Script framework, it should notify the user and work to find a plan that accomplishes the goal within the limitations.
Documentation
- https://help.autodesk.com/view/fusion360/ENU/?guid=GUID-C1545D80-D804-4CF3-886D-9B5C54B2D7A2
- https://aps.autodesk.com/marketplace/publisher-center/fusion-publisher-guidelines
- https://marketplace.autodesk.com/search?productIds=FSN
- https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/bd-p/fusion-api-scripts-forum-en
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

