- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rampstackco/claude-skills --skill brand-style-guide -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rampstackco/claude-skills --skill brand-style-guide -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rampstackco/claude-skills --skill brand-style-guide -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add rampstackco/claude-skills --skill brand-style-guide -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/rampstackco/claude-skills/tree/HEAD/dist/codex/.agents/skills/brand-style-guideVom Herausgeber
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.
brand-identity)brand-voice for the voice doc, then integrate)design-standards or design-system)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.
The narrative behind the brand. Why it exists, what it stands for, what it rejects.
Every variant of every mark, with rules.
The full color system with rules.
The full type system.
What pictures look like in this brand.
How the brand sounds. (Pulled from brand-voice work if done separately.)
The brand applied to real contexts.
The boundaries, illustrated.
The dos and don'ts section is what people actually reference in practice. Make it the easiest section to scan.
references/style-guide-template.md.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.
references/style-guide-template.md - Fillable section-by-section template.references/maintenance-playbook.md - How to keep the guide current after launch.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 when
---name: brand-style-guidedescription: Build or audit a comprehensive brand style guide that documents the full brand system including story, logo…---# dist/codex/.agents/skills/brand-style-guide/SKILL.mdÜbersicht
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.
FAQ
Laden Sie dist/codex/.agents/skills/brand-style-guide/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/rampstackco/claude-skills.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.