geometric-folding-fabrication
Skill0 starsChanged 5 months agoNo licenceView on GitHub
Geometric fabrication — folding design theory (MIT 6.849), CAD/CAM surface interrogation (MIT 2.158J — NURBS, curvature, offsets/toolpaths, developable surfaces, intersection robustness, meshing, inspection), the linear-algebra machinery (MIT 18.06 rigidity/stiffness/SVD), algorithmic foundations, and rhino-mcp-driven modeling. Use for origami-inspired modeling, foldable/deployable structures, rigidity/DOF analysis, panelization, unfolding to flat cut patterns, NURBS/curvature/offset/developability questions, CNC toolpath or sheet-metal geometry, 3D-print design (FDM: grounding/no-floating-geometry, supports, orientation, toolpaths), modular/repeated-part assembly, or modeling under material limits (minimum panel size, sheet size, kerf, thickness). Works with or without rhino-mcp (theory + analysis stand alone). Quick flat-foldability theorem lookups → geometric-folding skill.
In this repository21 other files it gives its agents.
- adsense-content-approval-strategySkill
- apple-buildSkill
- bulk-data-via-script-not-tokensSkill
- consulting-deck-craftSkill
- data-go-kr-api-quirksSkill
- design-policySkill
- docs-toc-shards-styleSkill
- external-content-citation-policySkill
- feature-flag-removalSkill
- geometric-foldingSkill
- git-commit-message-qualitySkill
- kakao-map-client-nav-relayoutSkill
- leaflet-marker-hitboxSkill
- macos-nativeSkill
- mit-ocw-vaultSkill
- obsidian-dailySkill
- obsidian-knowledgeSkill
- ssg-determinismSkill
- swiftuiSkill
- tier-grading-systemSkill
- writing-tone-personalSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.