agentleFS
Sign inStart free
luminary19luminary19/atelier/skills/forge-standards/SKILL.md

forge-standards

Skill2 starsChanged 5 months agoNo licenceView on GitHub

Forge suite — the "3D design tokens" layer. Defines and enforces every project-wide 3D constant before any geometry or texture is authored: coordinate system and handedness per export target (Blender Z-up RH → glTF/Three.js Y-up RH vs. Unreal Z-up LH → FBX), unit scale (meters in Blender, cm in UE5, the 100× correction), axis-swap matrices, real-world scale references, naming conventions (SM_/SK_/T_/M_/MI_ prefixes, _BC/_N/_ORM texture suffixes), pivot/origin placement rules per object class, per-platform polycount budgets (PC/console/mobile/web), texel density targets (px/m), UV utilization floors, ORM channel-pack policy, LOD ratios, and FORGE_STANDARDS.json schema. Use whenever DEFINING the 3D standards for a project (after the brief writes FORGE.md), resolving a "sideways mesh" or "100× scale" bug, establishing naming rules, budgeting polys or texel density, deciding pivot placement for a prop type, or generating the machine-readable standards file that other Forge skills ingest. Bootstrapping a brand-new 3D project (writing FORGE.md, "set up a 3D project") is `forge-brief`'s job — it runs first, then calls this skill. HEADLESS-ONLY: driven from code, output verified by reading a PNG. Part of the Forge suite.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 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.

  • 4

    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.

Check your setup, free