agentleFS
luminary19luminary19/atelier/skills/forge-model/SKILL.md

forge-model

Skill2 starsChanged 5 months agoNo licenceView on GitHub

Forge suite — polygonal and box modeling via Blender bpy + bmesh + modifier stacks. Produces a clean, export-ready .blend/mesh datablock (quad base mesh + non-destructive modifier stack) plus a headless QA render PNG: primitives, extrude, inset, bevel, loop cuts, bridge loops, modifier stacks (Mirror, Array, Solidify, Bevel, Subsurf, Shrinkwrap, WeightedNormal, SmoothByAngle), depsgraph-evaluated geometry reads, and programmatic mesh validation. Use whenever asked to "model a polygonal mesh", "box-model a character/prop", "model a hard-surface/organic mesh", "make a hard-surface asset", "create a base mesh", "add bevel", "add subdivision", "add array modifier", "add mirror modifier", "extrude/inset faces", or "sculpt base". For a toleranced mechanical part use forge-parametric; for scatter/L-system/SDF use forge-procedural; for retopo/LOD/topology repair use forge-topology. Hands off to forge-uv (seams), forge-material (PBR shading), forge-topology (retopo/LOD), forge-render (headless QA render), and forge-validate (manifold/watertight gate). HEADLESS-ONLY: driven from code, output verified by reading a PNG. Part of the Forge suite.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.