Agent skill

Brand Style Guide

by rampstackco in rampstackco/claude-skills

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.

MITAuto-check passedMedia & Creative

Install Brand Style Guide

skills CLI

$ npx skills add rampstackco/claude-skills --skill brand-style-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install rampstackco/claude-skills brand-style-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brand-style-guide .claude/skills/brand-style-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "brand-style-guide" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide into .claude/skills/brand-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-style-guide", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add rampstackco/claude-skills --skill brand-style-guide -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install rampstackco/claude-skills brand-style-guide --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brand-style-guide .agents/skills/brand-style-guide && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "brand-style-guide" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide into .agents/skills/brand-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-style-guide", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rampstackco/claude-skills --skill brand-style-guide -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install rampstackco/claude-skills brand-style-guide --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brand-style-guide .cursor/skills/brand-style-guide && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "brand-style-guide" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide into .cursor/skills/brand-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-style-guide", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/rampstackco/claude-skills.git --path skills/brand-style-guide

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add rampstackco/claude-skills --skill brand-style-guide -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install rampstackco/claude-skills brand-style-guide --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brand-style-guide .gemini/skills/brand-style-guide && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "brand-style-guide" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide into .gemini/skills/brand-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-style-guide", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install rampstackco/claude-skills brand-style-guide

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add rampstackco/claude-skills --skill brand-style-guide -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brand-style-guide .github/skills/brand-style-guide && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "brand-style-guide" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide into .github/skills/brand-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-style-guide", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rampstackco/claude-skills --skill brand-style-guide -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install rampstackco/claude-skills brand-style-guide --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brand-style-guide .opencode/skills/brand-style-guide && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "brand-style-guide" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/brand-style-guide into .opencode/skills/brand-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-style-guide", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: brand-style-guide
GitHub stars: 940
Token cost: ~2.1k tokens
SKILL.md length: 1,013 words
Files: 4 (incl. references)
Skills in repo: 103
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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.

Works in 8 steps: Story → Logo system → Color → …
The user wants to create brand guidelines
SKILL.md covers When to use, When NOT to use, Required inputs and The framework: 8 sections, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Brand Style Guide is an agent skill from rampstackco/claude-skills. 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…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/maintenance-playbook.md` and `references/style-guide-template.md`).

It sits in Media & Creative, covering Brand strategy and identity, Logo and visual identity and Design systems. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

The user wants to create brand guidelines
Document an existing brand
Build a brand book
Audit an existing style guide for completeness

Example prompts

“/brand-style-guide”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Story
Logo system
Color
Typography
Imagery and illustration
Voice and tone
Applications
Dos and don'ts

What it can do on your machine

Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brand Style Guide loads about 2.1k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 178 tokens; SKILL.md has 1,013 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~178
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,013 words, ~2,111 tokens.

Download SKILL.mdSave it as .claude/skills/brand-style-guide/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: brand-style-guide
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.
category: brand
catalog_summary: The canonical reference document for the full brand system
display_order: 3

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.

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

Show full SKILL.md (405 more words)Show less

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.

Files

SKILL.md and 3 other files (references) in skills/brand-style-guide of rampstackco/claude-skills.

SKILL.md
README.md
references/maintenance-playbook.md
references/style-guide-template.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

Brand Style Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brand Style Guide compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Brand Style Guide this skillrampstackco/claude-skills	940	—	~2.1k	Automated safety check: Pass	MIT	yesterday
DesignOhh-889/skyroc	795	9 repos	~3.1k	Automated safety check: Pass	MIT	1 mo ago
Brand SystemsHermeticOrmus/LibreUIUX-Claude-Code	112	—	~2.3k	Automated safety check: Pass	MIT	4 days ago
Brand Dnathatrebeccarae/claude-marketing	162	—	~1.8k	Automated safety check: Pass	MIT	4 mo ago
Brand Identityarnabbagxd/Brand-building-skills	720	—	~1.3k	Automated safety check: Pass	MIT	3 mo ago
Brand Guidelinesnexu-io/open-design	100k	—	~346	Automated safety check: Pass	Apache-2.0	today

Similar skills

Design
Ohh-889/skyroc
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations…
795 GitHub starsUsed in 9 repos~3.1k tokens
Frontend & DesignAuto-check passed
Brand Systems
HermeticOrmus/LibreUIUX-Claude-Code
Brand identity building blocks: positioning, personality, archetypes, logo systems, color palettes, type pairing, voice, and guidelines documentation.
112 GitHub stars~2.3k tokensUpdated 4 days ago
Frontend & DesignAuto-check passed
Brand Dna
thatrebeccarae/claude-marketing
Extract brand identity from a website URL — voice, colors, typography, imagery, values, and target audience — into a structured brand-profile.json.
162 GitHub stars~1.8k tokensUpdated 4 mo ago
Media & CreativeAuto-check passed
Brand Identity
arnabbagxd/Brand-building-skills
Create a visual identity brief for a brand — logo direction, color palette, typography, imagery style, and design system foundations.
720 GitHub stars~1.3k tokensUpdated 3 mo ago
Media & CreativeAuto-check passed
Brand Guidelines
nexu-io/open-design
Apply Anthropic's official brand colors and typography to artifacts for consistent visual identity and professional design standards.
100k GitHub stars~346 tokensUpdated today
Media & CreativeAuto-check passed
Form Brand
jeremylongshore/tons-of-skills-marketplace
A skill your agent uses when asked to create a brand identity, define visual design direction, generate a color palette or type system, build a style guide, or establish the look and feel for a…
2.8k GitHub stars~2.1k tokensUpdated today
Frontend & DesignAuto-check: notes

More from rampstackco/claude-skills

All 103 skills in this repo

After Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
940 GitHub starsUsed in 1 repo~2.5k tokens
Auto-check passed
Analytics Strategy
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
940 GitHub starsUsed in 1 repo~2.4k tokens
Auto-check passed
Brand Voice
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
940 GitHub stars~2.2k tokensUpdated yesterday
Auto-check passed
Content And Copy
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
940 GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed
Content Strategy
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
940 GitHub stars~2.6k tokensUpdated yesterday
Auto-check passed
Cro Optimization
rampstackco/claude-skills
Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions.
940 GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed

Questions about Brand Style Guide

What does Brand Style Guide 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. Brand Style Guide is an agent skill from rampstackco/claude-skills. 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.

When should I use Brand Style Guide?

Brand Style Guide fits situations like: the user wants to create brand guidelines; document an existing brand; build a brand book; audit an existing style guide for completeness.

How do I install Brand Style Guide in Claude Code?

Run `npx skills add rampstackco/claude-skills --skill brand-style-guide -a claude-code`. Or copy the skill folder (skills/brand-style-guide in rampstackco/claude-skills) into .claude/skills/brand-style-guide in your project. Claude Code loads it when a task matches its description.

How do I install Brand Style Guide in Codex?

Run `npx skills add rampstackco/claude-skills --skill brand-style-guide -a codex`. Or copy the skill folder (skills/brand-style-guide in rampstackco/claude-skills) into .agents/skills/brand-style-guide in your project. Codex loads it when a task matches its description.

Can I use Brand Style Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill brand-style-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brand-style-guide, .gemini/skills/brand-style-guide, .github/skills/brand-style-guide and .opencode/skills/brand-style-guide in your project.

What does Brand Style Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Brand Style Guide is instructions for the agent only.

Does Brand Style Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Brand Style Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brand Style Guide use?

Brand Style Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brand Style Guide use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Brand Style Guide?

Skills that share tags, products or a category with Brand Style Guide: Design (Ohh-889/skyroc, 795 stars), Brand Systems (HermeticOrmus/LibreUIUX-Claude-Code, 112 stars), Brand Dna (thatrebeccarae/claude-marketing, 162 stars) and Brand Identity (arnabbagxd/Brand-building-skills, 720 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brand Style Guide?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 940 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Brand Style Guide

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Brand Style Guide

When to use

When NOT to use

Required inputs

The framework: 8 sections

1. Story

2. Logo system

3. Color

4. Typography

5. Imagery and illustration

6. Voice and tone

7. Applications

8. Dos and don'ts

Workflow

Failure patterns

Output format

Reference files

Files

Compare with similar skills

Similar skills

More from rampstackco/claude-skills

Related

Questions about Brand Style Guide