brand-book
Skill0 starsChanged 7 days agoMITView on GitHub
Write the brand book. Use when the brief and style choices are settled, or an accepted brand book needs a new section or a rework.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- TucsenRoman/claude-skillstheir own version, first seen Oct 20, 2026
- Vicentehersant/vhs-agents-and-skillstheir own version, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- TucsenRoman/claude-skills★ 0same name
- Vicentehersant/vhs-agents-and-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brand-directionsSkill
- brandfileSkill
- brand-interviewSkill
- brand-probeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Write BRAND.md, the file agents follow, and take it to acceptance.
- Very specific: line 10
Run node brand/tools/brand.mjs status (if brand/tools/ is missing or next is none, hand off to brandfile).
- Very specific: line 12
Write to brand/work/candidate/BRAND.md.
- Distinctive: line 25
Turned down: Write what was rejected beside what was chosen, with the reason.
- Very specific: line 26
No claims: Write unknown for what is unknown.
- Distinctive: line 36
Treat a stray in a probe report as a defect in the book until shown otherwise.
≈ “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.
Files
Brand Book
Write BRAND.md, the file agents follow, and take it to acceptance. Done when the person has accepted the page, accept has run, and the pointer is added or declined.
Run node brand/tools/brand.mjs status (if brand/tools/ is missing or next is none, hand off to brandfile); if next names another skill, hand off to it. Read brand/work/brief.md, brand/work/selection.md if it exists, and the format; for a book in Russian, also the Russian notes.
Write to brand/work/candidate/BRAND.md. For a rework, start from a copy of brand/BRAND.md and brand/assets/, and change only what the brief's scope covers. Send a gap back to its owner:
- a choice you cannot write as a rule: blank its Choice in
brand/work/selection.md, put the question in its Why, and hand off tobrand-directions; - a missing fact: add it under "Open questions" in the brief, set
confirmed: no, and hand off tobrand-interview.
Write a diff
The book is a diff against what a capable agent does anyway. Every line traces to something the person said or chose, or a file you found. Mark anything else as an assumption where it stands and list it in {#open}. Keep the book under about 3,000 words.
- Testable rules. Write each rule so an outsider or a script can say "violated" without asking a designer: a number or ratio tied to something measurable, such as the height of the mark. What cannot be formalized gets a pair of examples and the name of whoever decides.
- Use first. Open with what to use: "Use
var(--primary)for the one action". Give a prohibition only for this brand, with its reason: a generic list of what looks machine-made only shifts the fashion and can ban the brand's own traits. - Structure, not just values. Fill
{#layout}. An axis nobody decided reads "not decided, ask the owner". - Constant and variable. For each element, say what never changes, what may, and who allows an exception. Keep a quirk that is theirs, with a line saying so.
- Turned down. Write what was rejected beside what was chosen, with the reason.
- No claims. Write
unknownfor what is unknown. Promise nothing about revenue and quote no brand-consistency statistics.
Fonts and files
Put the full file of each font the book names in brand/work/candidate/assets/fonts/ and the logo files in brand/work/candidate/assets/, so build can check coverage and the book works away from the project. Take an open font whole from its source, such as google/fonts, with its license file beside it. For a commercial font, ask for the file they are licensed to use; with no file, write —.
Build and probe
Run node brand/tools/brand.mjs build and fix every error. Leave the values behind warnings as they are and put each warning to the person at the stop. Write brand/work/candidate/CHANGELOG-entry.md: what this version decides, why, and what people using the brand must do. Then hand off to next; the person sees the page only once probes are on it.
Treat a stray in a probe report as a defect in the book until shown otherwise. Fix the rule, not the output, rebuild, and probe again if the fix touches what the tasks depend on.
Stop: they accept
Give the path brand/work/candidate/index.html, opening it if you can. Point to the "To check" box, the assumptions in {#open}, and the runs side by side. Ask whether this is their brand: fit, not liking.
They often answer by the page's labels: "color.accent is too loud". Edit the candidate and rebuild, since index.html is generated. Send a rejected style back to brand-directions as above. The book is accepted when they say so; a reaction to a detail is not acceptance.
Then run node brand/tools/brand.mjs accept and offer the pointer. With their yes, add it in that file's language to AGENTS.md or CLAUDE.md, whichever exists, or ask which to create. If they decline, tell them agents here will not know the book exists.
## Brand
Before work people will see (interface, copy, emails, images), read brand/BRAND.md. It also says how to change the brand.Committing is their call. Tell them brand/work/ stays out of git because the brief can hold competitors and prices, and fonts and logos in brand/assets/ keep their own licenses.
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.

