
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 and needs to be documented for handoff to designers, developers, vendors, or future team members.
- Installs
- 393
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rampstackco/claude-skills --skill brand-style-guide- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads brand-style-guide automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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-voicefor the voice doc, then integrate) - Building UI components (use
design-standardsordesign-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.
- Primary logo (with construction grid showing relationships)
- Wordmark
- Symbol / glyph
- Lockup variations (horizontal, stacked, etc.)
- Monogram (if part of system)
- Clear space rules (minimum spacing around logo)
- Minimum sizes (smallest acceptable size for print and digital)
- Acceptable color treatments (full color, single color, knock-out, reverse)
- Forbidden treatments (stretching, rotating, recoloring, drop shadows, gradients - whatever is forbidden)
- File formats and where to find them
3. Color
The full color system with rules.
- Primary palette (signature colors)
- Secondary palette
- Neutrals scale
- Semantic colors (success, warning, error, info)
- Light mode and dark mode variants
- Per color: hex, RGB, HSL, CMYK, Pantone (if print-relevant)
- Contrast ratios documented
- Allowed pairings
- Forbidden pairings
- Usage hierarchy (primary first, secondary supporting, neutrals dominant)
4. Typography
The full type system.
- Display typeface (with sample sizes)
- Body typeface (with sample sizes)
- Monospace (if applicable)
- Type scale (specific sizes used)
- Weight and style usage (which weights for which contexts)
- Line height ratios
- Letter spacing standards
- Web fallback stacks
- Open-source alternatives for licensing-restricted contexts
- Forbidden treatments (all caps overuse, fake italics, etc.)
5. Imagery and illustration
What pictures look like in this brand.
- Photography direction with example library
- Illustration style with example library
- Iconography system with the full icon set (or rules for adding to it)
- Forbidden imagery (stock photo cliches, specific things never to show)
- Photo treatment rules (color treatment, crops, composition)
6. Voice and tone
How the brand sounds. (Pulled from brand-voice work if done separately.)
- Voice attributes (3 to 5 adjectives with "we are X, not Y" framing)
- Tone shifts by context (onboarding, error, marketing, support, legal)
- Vocabulary preferences (words we use, words we avoid)
- Grammar and style rules
- Examples (good and bad copy side by side)
7. Applications
The brand applied to real contexts.
- Web (homepage, product pages, blog template)
- Email (template, signature, transactional)
- Social (post templates, profile imagery, story formats)
- Print (business cards, letterhead, print ads)
- Packaging (if applicable)
- Signage (if applicable)
- Internal documents (slides, reports, proposals)
- Each with examples showing what good looks like
8. Dos and don'ts
The boundaries, illustrated.
- Logo dos and don'ts (visual examples of correct and incorrect use)
- Color dos and don'ts (combinations to use, combinations to avoid)
- Type dos and don'ts (treatments to use, treatments to avoid)
- Composition dos and don'ts (layout patterns that work, ones that do not)
- Voice dos and don'ts (phrases that fit, phrases that do not)
The dos and don'ts section is what people actually reference in practice. Make it the easiest section to scan.
Workflow
- Inventory the inputs. What identity work is finished? What voice work is finished? What is missing?
- Confirm the format. Is this a PDF, a web page, a Notion doc, a printed book, or all of the above? Different formats have different production requirements.
- Section by section, draft. Use the template in
references/style-guide-template.md. - Stress-test with real examples. For every rule, find a real application example. Rules without examples get ignored.
- Get review from the people who will use it. Designers, developers, marketers. They will surface gaps.
- Version control. Style guides evolve. Date the doc. Note what changed in each version.
- Publish in the format the team will actually open. A 200-page PDF that lives on a shared drive is dead weight. A web page or Figma file with a clear URL gets used.
Failure patterns
- Skipping the "what we are not" sections. Without rejection rules, anything becomes acceptable.
- Document with no examples. Rules without visual examples are abstract and ignored.
- Document with only examples. Examples without rules cannot be applied to new situations.
- Static PDF that no one opens. Ship the guide in the format the team uses daily (web page, Figma, Notion, etc.).
- No version history. When the brand evolves, no one knows which rules changed or when.
- Aspirational rules. Rules the brand does not actually follow get treated as suggestions. Document what is actually true, not what is wished.
- Treating "dos and don'ts" as filler. This section is what people use most. Invest in it.
Output format
Default output is a multi-section markdown document or a structured set of files, plus a presentation-ready version (web page, PDF, or Figma) for sharing with stakeholders.
Recommended structure:
brand/
style-guide.md (the canonical document)
story.md (or as a section)
logo/
construction.md
files/ (SVG, PNG, etc.)
colors.md
typography.md
imagery/
photography.md
illustration.md
icons/
icons.md
files/
voice.md
applications/
web.md
email.md
social.md
print.md
dos-and-donts.md
For consumer-facing presentation, build a web page version that imports from these source files. The source files are canonical. The presentation is a view of them.
Reference files
references/style-guide-template.md- Fillable section-by-section template.references/maintenance-playbook.md- How to keep the guide current after launch.
FAQ
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 and needs to be documented for handoff to designers, developers, vendors, or future team members.
How do I install brand-style-guide?
Run npx skills add https://github.com/rampstackco/claude-skills --skill brand-style-guide in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/brand-style-guide/ (personal) or .claude/skills/brand-style-guide/ (project).
Which AI agents can use brand-style-guide?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is brand-style-guide safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains brand-style-guide?
It is published by rampstackco in rampstackco/claude-skills. It has 393 recorded installs.
More from rampstackco/claude-skills
art-direction
rampstackco/claude-skills
Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables. Use creative-direction instead when the ask is the project-wide aesthetic brief that this skill consumes as input.
brand-identity
rampstackco/claude-skills
Design or evaluate a brand visual identity system covering logo, color, typography, imagery direction, iconography, and motion principles. Use this skill whenever the user wants to design a logo, build a visual identity, define brand colors, choose brand typography, develop iconography, plan brand imagery, or evaluate an existing identity for cohesion. Triggers on logo design, brand identity, visual identity, brand mark, wordmark, monogram, color palette, brand colors, brand typography, type system, iconography, brand imagery, motion design, brand system, identity system. Also triggers when the user has a brand direction approved and now needs the visual artifacts that express it.
creative-direction
rampstackco/claude-skills
Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) and produce a structured aesthetic brief that downstream content, copy, design, and art-direction skills consume as required input. The aesthetic depth layer, distinct from creative-brief (operational kickoff: scope, audience, deliverables, constraints). Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling, or when multiple downstream aesthetic-producing skills need a shared brief. Triggers on creative direction, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes. Does NOT fire for a general kickoff brief (use creative-brief), tactical single-piece work, already-documented direction, purely functional output, or locked production-stage work.
landing-page-copy
rampstackco/claude-skills
Write landing page copy with attention to the hero, value proposition, social proof, objection handling, and conversion-focused CTAs. Use this skill whenever the user wants to write a landing page, sales page, hero section, or any conversion-focused web copy. Triggers on landing page, sales page, hero copy, value proposition, headline, subheadline, hero section, CTA copy, conversion copy, opt-in page, squeeze page. Also triggers when the user has a marketing campaign or product launch needing dedicated conversion copy. Use cro-optimization instead when the page already exists and the ask is to lift its conversion rate through testing rather than to write the copy.
chatbot-flow-design
rampstackco/claude-skills
Designing conversational flows for website chatbots and AI agents. Intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics. Honest about scripted-bot (rigid trees, fail edge cases), hallucinating-bot (LLM without structure, makes things up), and structured-guided-conversation (LLM-powered with intent architecture and fallback discipline) patterns. Distinguishes chatbot DESIGN (this skill) from chatbot IMPLEMENTATION (engineering and platform work). Triggers on chatbot, conversational AI, AI agent, chat widget, intent design, conversational flow, bot escalation, LLM grounding. Also triggers when a chatbot is hallucinating, when a scripted bot is failing edge cases, or when a chatbot is being scoped for the first time.
Popular marketing & seo skills
reddit-automation
flowkit-labs/skills
Find Reddit threads where people are genuinely asking for what you offer, then draft short, genuinely helpful replies — disclosing your affiliation honestly and naming your product only when it truly answers the question. Two moves: discovery — scan the right subreddits for real needs (recommendation asks, expressed pain, competitor mentions) and rank the few threads where you can actually help; drafting — write from real experience, respect each community's self-promo rules, and keep a human in the loop to review and post. This markets on Reddit the honest way: contribute value, disclose who you are, never astroturf. Distilled from the playbook behind doany.ai's Reddit agent. Triggers on "find reddit opportunities", "reddit marketing", "reddit automation", "reply on reddit for my product", "reddit community engagement", "reddit lead gen", or any ask to turn Reddit threads into genuine, disclosed marketing replies.
twitter-automation
101-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
magentosh/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
qu-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
product-launch-video
heygen-com/hyperframes
Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route here too — the brief carries the show-it-as-is intent. Unclear → /hyperframes.
twitter-automation
skills-shell/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet