Brand guidelines
Skill nimadorostkar/Claude-Skills-collection/skills/design/brand-guidelines
A curated library of 137 production-grade skills for Claude and other AI coding agents.
npx -y skills add nimadorostkar/Claude-Skills-collection --skill brand-guidelinesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when applying or documenting a brand identity. Covers extracting a system from existing assets, documenting colour, type, and voice, and applying a brand consistently across new work.
SKILL.md
5.4 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
Brand Guidelines
Purpose
Apply a brand consistently, and document it well enough that someone else can too. A brand that exists only in one designer's judgment is not a brand; it is a taste.
When to Use
- Applying an existing brand to new material.
- Documenting a brand that has never been written down.
- Auditing material for brand consistency.
- Extracting a system from a set of existing assets.
Capabilities
- Extracting colour, type, spacing, and voice from existing assets.
- Documenting a usable brand system.
- Applying a brand across media.
- Auditing for drift.
Inputs
- Existing brand assets, or a brand guideline document.
- The material to be produced or audited.
- The medium and its constraints.
Outputs
- A documented system: colour, type, spacing, imagery, voice.
- Material that is on-brand and can be verified as such.
- A list of the places the brand has drifted.
Workflow
- Extract before inventing — If a brand exists in assets but not in a document, derive it: sample the colours, identify the typefaces, measure the spacing, read the copy for voice. What is consistent across the assets is the brand; what varies is drift.
- Document the decisions, not just the values — "Primary blue #2563EB, used for actions and links only. Never for large fills." The constraint is the useful part.
- Cover the cases people get wrong — Minimum logo size, clear space, what to do on a dark background, what happens when the brand colour fails contrast.
- Document the voice — It is half the brand and it is nearly always omitted. Give examples of on-brand and off-brand copy.
- Apply, then audit — Check the output against the system rather than against instinct.
Best Practices
- A brand guideline without a "do not" section is not usable. The prohibitions are what prevent drift.
- Colour is where drift starts. Two similar blues in circulation becomes five within a year.
- The brand's primary colour frequently fails accessibility contrast for text. Document what to use instead, before someone ships an unreadable button.
- Voice examples do more than adjectives. "Confident, not arrogant" means nothing; a before-and-after pair of sentences means something.
- Logo misuse — stretching, recolouring, placing on a busy photograph — is universal and is prevented only by showing the wrong version explicitly.
- A brand that cannot survive being applied by a non-designer is not documented well enough.
Examples
A brand system documented so that it can be applied:
## Colour
| Token | Hex | Use | Never |
|----------------------|----------|------------------------------------------|------------------------------|
| brand/primary | #2563EB | Primary actions, links, active states | Large fills; body text |
| brand/primary-dark | #1D4ED8 | Hover and pressed states only | Anything else |
| brand/ink | #111827 | Body text, headings | — |
| brand/paper | #FFFFFF | Backgrounds | — |
| brand/accent | #F59E0B | Warnings, highlights. Sparingly. | More than one per screen |
**Contrast:** `brand/primary` on white is 4.6:1 — it passes for body text but only
just. For text below 16px, use `brand/primary-dark` (7.1:1). Never place
`brand/accent` text on white: it is 2.1:1 and unreadable.
## Type
Display : Söhne, 600 weight. Headings only. Tracking -0.02em above 32px.
Text : Söhne, 400/500. Body, UI, everything else.
Never : a third typeface. Hierarchy comes from size and weight.
## Voice
We are direct and specific. We do not hedge, and we do not perform enthusiasm.
| Off-brand | On-brand |
|----------------------------------------------------|---------------------------------------------|
| "Oops! Something went wrong." | "We couldn't save your changes. Try again." |
| "We're thrilled to announce an exciting new..." | "Exports now include line items." |
| "Please kindly note that you may wish to consider" | "You can also..." |
## Logo
- Minimum width: 24px (digital), 20mm (print).
- Clear space: the height of the mark, on all four sides.
- On photography: use the white version, on an area of the image with
low detail. Never on a busy background.
- Never: stretch, rotate, recolour, add effects, or place inside a shape
that is not part of the mark.
Notes
- The contrast note above is the kind of detail that separates a usable guideline from a decorative one. A brand colour that fails contrast for small text will be used for small text unless the document says what to use instead.
- Voice tables with a wrong/right pair are the most effective format for the writing half of a brand. Adjectives are not actionable.
- Audit quarterly. Brand drift is gradual, and it is only visible when the current material is placed next to the guideline.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most marketing audience skills give in ~1.1k tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- extract the brand system from existing assets
- document brand constraints and not just values
- cover common misuse cases and edge cases
- include explicit prohibitions
- document brand voice with correct and incorrect examples
- apply the brand then audit against the rules
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.