forge-brief
Skill2 starsChanged 5 months agoNo licenceView on GitHub
Forge suite — define the 3D asset brief and write FORGE.md (the project-memory file every other Forge skill reads). Produces: a completed FORGE.md at the project root with target engine, coordinate system, poly/texel budgets, render settings, PBR workflow, the determinism contract (seed + sample counts for idempotent rebuilds), output paths, and (when ATELIER.md is present) the extracted world/aesthetic/signature-moment/OKLCH-hue that drives look-dev. Use this FIRST whenever starting any Forge 3D pipeline — including "define the asset", "set up a 3D project", "what are the budgets for this mesh", "create FORGE.md", "brief a 3D asset", "extract the aesthetic from ATELIER.md for Blender", "what engine is the target", "set poly budget", "set texel density", "configure render engine". (The bare "init Forge" / "forge init" phrase is owned by the `forge` router's `init` mode, which scaffolds FORGE.md inline and then calls this skill — this skill does not claim that trigger.) HEADLESS-ONLY: driven from code, output verified by reading a PNG. Part of the Forge suite.
In this repository38 other files it gives its agents.
- atelier-componentsSkill
- atelier-copySkill
- atelier-dataSkill
- atelier-datavizSkill
- atelier-directionSkill
- atelier-foundationsSkill
- atelier-hardenSkill
- atelier-layoutSkill
- atelier-motionSkill
- atelier-perf-a11ySkill
- atelier-redesignSkill
- atelier-reviewSkill
- atelier-scrollSkill
- atelierSkill
- atelier-typographySkill
- atelier-uxSkill
- atelier-webglSkill
- codex-imagegenSkill
- codex-imagegen-tasteSkill
- forge-animateSkill
- forge-dataSkill
- forge-exportSkill
- forge-intakeSkill
- forge-lightSkill
- forge-materialSkill
- forge-modelSkill
- forge-optimizeSkill
- forge-parametricSkill
- forge-proceduralSkill
- forge-renderSkill
- forge-rigSkill
- forge-simSkill
- forgeSkill
- forge-standardsSkill
- forge-textureSkill
- forge-topologySkill
- forge-uvSkill
- forge-validateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 3 are distinctive, and 10 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.
10
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.