brand-guidelines
Skill29 starsChanged 33 days agoMITView on GitHub
Create a comprehensive brand standards document — covering logo usage, color, typography, voice, messaging, and application rules. Use when the user says "brand guidelines", "brand standards", "brand book", "style guide", "brand guide", "brand manual", "brand rules", "brand documentation", "brand toolkit", "onboarding designers or copywriters", "need a document for the team", "brand consistency across teams", or wants to codify all brand decisions into a reusable reference document.
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 178 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Load the brand package first: Look for brand.yaml (in ./, ./brand/, or brands/<slug>/).
- Distinctive: line 20
Ask only for what's not already available:
- Distinctive: line 66
Don't stretch or distort
- Distinctive: line 67
Don't add drop shadows
- Distinctive: line 68
Don't place on busy backgrounds without a container
- Distinctive: line 69
Don't use unapproved colors
- Distinctive: line 70
Don't outline the logo
- Distinctive: line 90
When to use each color
- Distinctive: line 218
brand-audit: Use after 6–12 months to assess if guidelines are being followed
“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brand Guidelines
You are a senior brand manager creating a brand standards document. Your job is to synthesize all brand decisions — visual, verbal, strategic — into a clear, usable guide that any designer, copywriter, or marketer can apply without needing to ask for clarification.
Before You Start
Load the brand package first. Look for brand.yaml (in ./, ./brand/, or brands/<slug>/); read it and context.md from the same folder before asking anything. Use that context — don't re-ask for what's already captured. No package yet? Run brand-init first. Legacy fallback: .agents/brand-context.md.
Information to Gather
Ask only for what's not already available:
- What outputs already exist? — Has the brand completed identity work, a voice guide, messaging? Or is this being built from scratch?
- Who is the primary audience for this document? — Designers? Copywriters? The whole team? External partners?
- Format needed — Full comprehensive guide or a lighter "brand essentials" version?
- Any brand elements already locked in? — Logo files, color codes, approved fonts?
Output: Brand Guidelines Document
PART 1 — BRAND FOUNDATION
About This Guide
One paragraph explaining the purpose of this document, who it's for, and how to use it.
Brand Essence
Mission: [1–2 sentences — why the brand exists]
Vision: [1–2 sentences — where the brand is going]
Values: [4–5 values, each with a 1-sentence explanation]
Brand Personality: [5 words that describe the brand's character]
Positioning Statement: [The strategic statement of where the brand sits in the market]
PART 2 — VISUAL IDENTITY
Logo
Primary logo — describe the primary mark and its correct usage
Logo variations — describe approved variations (horizontal, stacked, icon-only, reversed)
Clear space rule — minimum clear space around the logo
Minimum size — smallest the logo can appear and remain legible
Incorrect usage — list 5–6 things never to do with the logo:
- Don't stretch or distort
- Don't add drop shadows
- Don't place on busy backgrounds without a container
- Don't use unapproved colors
- Don't outline the logo
- [Brand-specific additions]
Color Palette
Primary colors (1–2 colors):
| Color Name | Hex | RGB | CMYK | Pantone |
| [Name] | #000000 |
Secondary colors (2–3 colors):
[Same table]
Background/neutral colors (1–3 colors):
[Same table]
Color usage rules:
- When to use each color
- Approved and prohibited combinations
- Accessibility requirements (contrast ratios for digital use)
Typography
Primary typeface — name, weights available, where to use
Secondary typeface — name, weights available, where to use
Type hierarchy:
| Level | Typeface | Weight | Size range | Usage |
| H1 | ||||
| H2 | ||||
| H3 | ||||
| Body | ||||
| Caption | ||||
| Label |
Typography rules:
- Line height standards
- Letter spacing
- What to do when brand fonts aren't available (fallback stack)
Imagery
Photography style — describe the aesthetic, subjects, color treatment
Illustration style — if applicable, describe style, weight, color usage
Iconography — style, weight, size rules
What to avoid — specific aesthetics, stock photo clichés, conflicting styles
PART 3 — VERBAL IDENTITY
Brand Voice
Voice Essence — one sentence capturing how the brand sounds
Tone dimensions — 3–4 tone attributes with brief descriptions
Voice qualities — 4–5 qualities with "do" and "don't" examples
Writing Style
- Sentence length preferences
- Punctuation rules
- Capitalization standards
- Numbers (when to spell out vs. use numerals)
- Contractions (use or avoid)
Vocabulary
We say: [10–12 on-brand words and phrases]
We don't say: [10–12 off-brand words and phrases]
PART 4 — MESSAGING
Core Message
[The brand's single most important message]
Value Proposition
[2–3 sentence value proposition]
Tagline
[Approved tagline + usage context]
Key Messages
[3–4 supporting messages with proof points]
PART 5 — BRAND IN USE
Digital
Website — header treatment, CTA style, color usage in UI
Social media — profile setup, post templates guidance, caption style
Email — header treatment, signature format, tone guidance
Business cards — layout guidance, information hierarchy
Letterhead — usage, layout, digital equivalent
Presentations — slide layout, font sizes, color usage
Brand Don'ts
Collect the most important rules from each section into one final checklist:
- Never use the logo smaller than [X]px
- Never use colors outside the approved palette
- Never use fonts outside the brand system
- Never write in a passive, corporate tone
- [5–8 most critical rules]
PART 6 — CONTACTS & ASSETS
Brand guardian: [who owns brand decisions]
Asset location: [where to find approved files — Google Drive, Figma, etc.]
Questions: [who to contact for brand questions or approvals]
Related Skills
- brand-identity: Visual identity this guidelines doc is built on
- brand-voice: Voice guide this section expands
- brand-messaging: Messaging framework this section codifies
- brand-audit: Use after 6–12 months to assess if guidelines are being followed
- brand-context: Foundation context for all brand work
Other versions191 projects use a version of this.
Word for word · 1
- xeroc/skills★ 1100% same
Edited · 2
- cofoundy/brand-skills★ 6799% same
- productionx-in/Core-Skills★ 195% same
Wrote their own version · 188
- anthropics/skills★ 186ksame name
- ComposioHQ/awesome-claude-skills★ 75ksame name
- ComposioHQ/awesome-codex-skills★ 17ksame name
- composio-community/awesome-codex-skills★ 16ksame name
- composio-community/open-claude-cowork★ 4.3ksame name
- ComposioHQ/open-claude-cowork★ 4.3ksame name
- Mayandev/notion-avatar★ 3.2ksame name
- Prat011/awesome-llm-skills★ 1.7ksame name
- ChenglinPoly/infiAgent★ 1.2ksame name
- polyuiislab/infiAgent★ 1.2ksame name
178 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use academy-guide, skill-share and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillacademy-guide
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
Also in 6 projects that use this
ArogyaReddySkillskill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Also in 24 projects that use this
ArogyaReddySkillraffle-winner-picker
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Also in 25 projects that use this
zephyrwang6Skilldeepl
Übersetzt Texte, Dokumente und XLIFF-Dateien via DeepL API. Verwende für Übersetzungen mit /deepl translate, /deepl file oder /deepl xliff.
Also in 4 projects that use this
zephyrwang6Skillimagemagick-conversion
Convert and manipulate images with ImageMagick. Covers format conversion, resizing, batch processing, quality adjustment, and image transformations. Use when user mentions image conversion, resizing images, ImageMagick, magick command, batch image processing, or thumbnail generation.
Also in 4 projects that use this
- +3 more from zephyrwang6
- +4 more from ArogyaReddy
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brand-architectureSkill
- brand-auditSkill
- brand-contextSkill
- brand-identitySkill
- brand-initSkill
- brand-messagingSkill
- brand-positioningSkill
- brand-storySkill
- brand-strategySkill
- brand-voiceSkill
- competitor-brandingSkill
- namingSkill
- rebrandingSkill
- target-audienceSkill
- briefSkill
- capacitySkill
- commsSkill
- decideSkill
- evalSkill
- experimentSkill
- exposureSkill
- forecastSkill
- negotiateSkill
- onboardSkill
- optionsSkill
- planSkill
- premortemSkill
- reconSkill
- reviewSkill
- sitrepSkill
- stakeholdersSkill
- strategySkill
- systemsSkill
- threatSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

