Brand guidelines examples worth stealing from (and what they all miss)

A brand guidelines document has one job: letting someone who wasn't in the room make the same call the brand team would have made. Every page either serves that job or decorates it. The test is concrete: hand the document to a freelancer, give them a task the document doesn't literally show, and see whether their output lands on-brand. Documents that pass share four properties: exact values (hex, not 'our blue'), rules with boundaries ('minimum clear space equals the height of the logomark'), decisions about hierarchy (which color leads, which supports, what never appears together), and visible counterexamples, because a don't communicates faster than a paragraph of dos.

• NASA Graphics Standards Manual (1976). Still the reference for rule-writing: every rule is measurable (clear space, reproduction sizes, forbidden treatments), which is why contractors could apply it for decades without asking. Steal: rules phrased so compliance is checkable.
• Spotify Design Guidelines. The strongest example of voice: the document sounds like the brand it governs. Steal: write guidelines in the brand's own tone, because the document itself is the first artifact people copy.
• Uber Brand System. Built for scale across hundreds of markets: a small set of core elements (logo, type, a disciplined palette, motion) with explicit flex zones. Steal: separating what's fixed from what's local, so growth doesn't fork the brand.
• Atlassian Design System. The rare document that bridges marketing brand and product UI in one system: the same foundations feed campaign pages and the software itself. Steal: one source of truth across brand and product, not two documents that drift apart.
• Slack Media Kit. Short, public, and mostly prohibitions: exact logo files, exact clear space, a list of don'ts. Steal: for external audiences, a small enforceable document beats a comprehensive unread one.
• Starbucks Creative Expression. A public site, not a PDF, organized by expression (color, voice, typography) with seasonal flexibility built in. Steal: publishing guidelines as a living site so they can change without re-issuing a document.
• Mailchimp Content Style Guide. The writing-first example: voice, tone by situation, grammar calls, all public. Steal: voice deserves rules as concrete as color's; 'friendly but not silly' becomes real with before/after examples.
• IBM Design Language. The deep end: typography, color, motion, illustration, and photography as one philosophical system. Steal: the grid and motion sections, the two areas most guidelines skip entirely.

Notice what the lesson never is: the visual style itself. Copying Uber's palette produces a worse Uber, not a better you. What transfers is the decision structure: what each document chose to fix, what it left flexible, and how it made rules checkable.

1. Logo: files, clear space in measurable units, minimum sizes, approved and forbidden treatments.
2. Color: exact values (hex/RGB/CMYK) with roles: which is primary, which are surfaces, what text sits on what, and the combinations that never appear. Light and dark mode both, or the dark theme will be improvised.
3. Typography: families with jobs (display, body, mono), weights that exist, a scale, and line-length limits.
4. Voice: tone by situation with before/after pairs, not adjectives.
5. Imagery: what photography and illustration look like, with real counterexamples.
6. Do/don't pairs throughout: the fastest-reading format in the whole document.

Every example above assumes a human reader with taste and time. But an increasing share of brand-touching output is now produced by AI tools: site builders, coding agents, content generators. A PDF is invisible to all of them, which is how companies with beautiful guidelines still ship AI-built pages in the same default purple-gradient look as everyone else. The fix is a second projection of the same decisions in a format machines consume: exact tokens, the type system, spacing, and the do/don't rules as a DESIGN.md an agent reads or a token file a tool imports. Same brand, one source of truth, two renderings: one for people, one for the tools doing the building.

That second rendering is what an Identity Forge kit is. Every kit carries the machine-executable core of brand guidelines (28 semantic color tokens in light and dark, a font pairing with jobs, scale, motifs, do's and don'ts) exportable as DESIGN.md for agents, paste-ready prompts for Lovable, v0, and Bolt, Tailwind and DTCG tokens, or a shadcn theme. Start from a kit and you get the hard, checkable half of a guidelines document generated; the human half (logo rules, voice, imagery) is yours to write on top.