style-bible
Skill2 starsChanged 26 days agoMITView on GitHub
Use when your brand's style bible must be created or revised (motifs, palette, typography, references, do/don't) or a sibling brand needs its section. Runs the creative-director in a fresh context and writes a versioned manual in the NASA 1976 standards-manual structure, with every fact routed to /verify.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-reviewSkill
- ai-mesh-cleanSkill
- cad-buildSkill
- couponSkill
- curriculumSkill
- dfm-reviewSkill
- fileSkill
- gddSkill
- ip-checkSkill
- led-budgetSkill
- lesson-learnedSkill
- makerworld-publishSkill
- material-pickSkill
- mcp-new-toolSkill
- ortho-sheetSkill
- pi-power-budgetSkill
- preprint-checkSkill
- promo-planSkill
- qa-gateSkill
- render-criticSkill
- research-oneSkill
- research-topicSkill
- retopoSkill
- safety-sheetSkill
- sculptSkill
- slicer-questionSkill
- tech-packSkill
- unit-costSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read the existing style-bible.md if present.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Overview
Build or revise: $ARGUMENTS
Output on disk, in your brand folder (default work\brand\<brand-slug>\, or the folder you name): style-bible.md, its references.md, one rendered moodboard with its script under moodboards\, and a claims table for /verify.
When to use
A brand needs its visual law written down, or a shipped product exposed a gap in it. Not for voice and tone (a separate guide from the creative-director), not for a single product's art direction (write a brief under <brand folder>\briefs\), not for garment print files (/tech-pack).
Steps
- Read the existing
style-bible.mdif present; merge, never duplicate. Link facts fromknowledge\instead of restating them. - Divergent pass: at least 20 motif or direction candidates in
<brand folder>\ideation\YYYY-MM-DD-<section>.md, the chosen set marked with one line of reasoning each. - Write the manual in the structure of the 1976 NASA Graphics Standards Manual (https://www.nasa.gov/wp-content/uploads/2015/01/nasa_graphics_manual_nhb_1430-2_jan_1976.pdf): 1 Identity (motifs, mark language, lockups, clear space); 2 Reproduction art (palette: hex, RGB, CMYK; Pantone only via an official Pantone source); 3 Typography (typefaces, each with licence URL and allowed uses: web, print, embossed, 3D-printed glyphs); 4 Packaging; 5 Publications and social; plus Mood, References (20 or more), Do/Don't, Changelog.
- Every fact becomes a row in
research\inbox\brand\style-bible-<section>.md(researcher table format), with the page to check: font licences https://helpx.adobe.com/fonts/web/font-licensing/font-licensing.html and https://openfontlicense.org/ofl-faq/; Pantone in Adobe apps https://helpx.adobe.com/illustrator/kb/pantone-color-books-illustrator.html; contrast https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html. In the manual, mark each such value[pending /verify]until aresearch\verified\brand\...path replaces the tag. references.md: one row per reference with creator, URL, licence, fetched date. No credit, no row.- Render one moodboard headless:
<blender_exe> --background --python <brand folder>\moodboards\<slug>.py(Blender fromconfig\paths.yaml); open the PNG. If Blender is not configured, compose the board with Python instead and say so. - Append a dated
## Changelogline. Return paths, the claims-table path for/verify, numbered NEEDS MAKER questions.
Common rationalizations
| Rationalization | Reality |
| "I know this font is open-licensed." | Fetch the licence page or tag it [pending /verify]. Recalled facts are where errors come from. |
| "Hex is enough; CMYK and Pantone can come later." | A palette without its reproduction values is not a standards manual. Fill every column or mark it open. |
| "Ten motifs are already great, skip the pass." | The divergent pass is the deliverable. Twenty candidates, then choose. |
| "The moodboard script is a detail." | Without the script beside it the board cannot be regenerated. |
Red flags (stop and fix)
- A value in the manual with neither a
research\verified\path nor a[pending /verify]tag. - A reference row missing creator, URL, licence or date.
- A moodboard PNG that was not opened, or with no script beside it.
- A changed value with no changelog line.
Verification
style-bible.mdexists in the brand folder with all NASA-structure sections and a## Changelogline for this run.- Ideation file lists 20 or more candidates with the chosen ones marked.
references.mdhas 20 or more rows, each with creator, URL, licence, fetched date.- Moodboard PNG and its script exist side by side; the PNG was opened.
- Claims table written under
research\inbox\brand\and its path returned.
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.

