Agent skill · Security

brand-style-guide

Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished an

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill brand-style-guide --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/brand-style-guide/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Brand Style Guide Document the brand system so other people can use it without ambiguity. This is the artifact that lives longest. Designers, developers, agencies, and vendors will reference it for years. Build it like a reference manual, not a presentation. This skill assumes the brand identity is designed (run `brand-identity` first if not). The output of this skill is the canonical reference document. --- ## When to use - Creating brand guidelines for a finished identity - Documenting an existing brand that has no formal guide - Auditing an existing style guide for gaps or inconsistencies - Building a brand book to hand to vendors, partners, or new team members - Updating a guide after a major brand evolution ## When NOT to use - The brand identity is not yet designed (use `brand-identity`) - Brand voice work specifically (use `brand-voice` for the voice doc, then integrate) - Building UI components (use `design-standards` or `design-system`) --- ## Required inputs - Finished brand identity (logo, colors, typography, imagery direction, motion principles) - Brand voice and tone documentation (or sufficient inputs to write a voice section) - Application examples that show the br

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 8 sections
  5. 1. Story
  6. 2. Logo system
  7. 3. Color
  8. 4. Typography
  9. 5. Imagery and illustration
  10. 6. Voice and tone
  11. 7. Applications
  12. 8. Dos and don'ts
  13. Workflow
  14. Failure patterns
Ships with 2 files
  • references/maintenance-playbook.md
  • references/style-guide-template.md
More from claude-skills
All skills →
About this skill
What does the brand-style-guide skill do?

Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished an

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill brand-style-guide --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going