# Brand Style Guide

Build or audit a comprehensive brand style guide that documents the full brand system...

- Repository: https://github.com/rampstackco/claude-skills (1014 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rampstackco/claude-skills --skill brand-style-guide -g -a claude-code -y`
Codex: `npx skills add rampstackco/claude-skills --skill brand-style-guide -g -a codex -y`
Cursor: `npx skills add rampstackco/claude-skills --skill brand-style-guide -g -a cursor -y`
Gemini CLI: `npx skills add rampstackco/claude-skills --skill brand-style-guide -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rampstackco/claude-skills`

## Description

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 and needs to be documented for handoff to designers, developers, vendors, or future team members.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 brand in real contexts
- Decisions on what is mandatory vs flexible vs forbidden

---

## The framework: 8 sections

A complete style guide has eight sections. Most guides skip 2 or 3 of them and create downstream confusion. Build all 8 from the start.

### 1. Story
The narrative behind the brand. Why it exists, what it stands for, what it rejects.

- Origin / founding story
- Mission and vision
- Values (3 to 5, with what each means in practice)
- Positioning statement
- Audience (with the level of specificity from the brief)
- What we are not (the things we explicitly reject)

### 2. Logo system
Every variant of every mark, with rules.

The rest: https://github.com/rampstackco/claude-skills/blob/HEAD/dist/codex/.agents/skills/brand-style-guide/SKILL.md