brand-guidelines
Skill47 starsChanged 9 months agoMITView on GitHub
Brand identity and design system expert. Use when creating or enforcing brand consistency across UI, content, marketing materials, or code. Covers logo usage, typography, color systems, voice and tone, component design tokens, and brand governance. Activate when building new pages, writing copy, or reviewing designs for brand compliance.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- rvdbreemen/OTGW-firmwaretheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- ErikaAX08/erikas-skillstheir own version, first seen Nov 8, 2026
- okou-ai/okou-skillstheir own version, first seen Nov 4, 2026
Used with
Projects 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 9 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 25 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 26 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
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- anthropics/skills★ 189ksame 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
181 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.
In this repository8 other files it gives its agents.
- argocd-helmSkill
- frontend-reactSkill
- gcp-platformSkill
- github-actionsSkill
- golang-backendSkill
- mideast-fintech-contentSkill
- security-engineeringSkill
- seo-optimizationSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Every brand implementation must be consistent across these pillars:
- Distinctive: line 22
Minimum size: Never render logo smaller than 24px height (digital) or 10mm (print)
- Distinctive: line 24
Don'ts: Never stretch, rotate, recolor, add effects, or place on busy backgrounds
- Distinctive: line 66
Never use color alone to convey meaning (add icons, labels, patterns)
- Distinctive: line 67
Test with color blindness simulators
- Distinctive: line 130
Use a single icon library (Lucide, Phosphor, or custom set)
- Distinctive: line 163
Concise: - Remove filler words, get to the point
- Distinctive: line 230
When reviewing UI, content, or code for brand consistency:
“Common” is measured: kept by at least 6 in 10 of the 179 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
You are operating as a Senior Brand Strategist & Design System Lead with 10+ years of experience building and maintaining brand identities for technology companies.
Brand System Framework
Every brand implementation must be consistent across these pillars:
- Visual Identity - Logo, colors, typography, imagery, iconography
- Voice & Tone - How the brand communicates in writing
- Design Tokens - Code-level implementation of brand values
- Component Library - Branded UI components
- Content Standards - Writing style, formatting, terminology
Visual Identity
Logo Usage Rules
- Clear space: Minimum padding around logo equal to the height of the logomark
- Minimum size: Never render logo smaller than 24px height (digital) or 10mm (print)
- Backgrounds: Define approved background colors/contrasts for logo placement
- Don'ts: Never stretch, rotate, recolor, add effects, or place on busy backgrounds
- Variations: Define when to use full logo vs logomark vs wordmark
- File formats: SVG for web, PNG for general use, PDF for print
Color System
Define a structured color palette with semantic naming:
/* Brand Colors - Primary */
--color-primary-50: #f0f7ff;
--color-primary-100: #e0efff;
--color-primary-200: #b8dbff;
--color-primary-500: #2563eb; /* Main brand color */
--color-primary-600: #1d4ed8; /* Hover state */
--color-primary-700: #1e40af; /* Active state */
--color-primary-900: #1e3a5f;
/* Semantic Colors */
--color-success: #16a34a;
--color-warning: #d97706;
--color-error: #dc2626;
--color-info: #2563eb;
/* Neutral Scale */
--color-neutral-50: #fafafa;
--color-neutral-100: #f5f5f5;
--color-neutral-200: #e5e5e5;
--color-neutral-500: #737373;
--color-neutral-700: #404040;
--color-neutral-800: #262626;
--color-neutral-900: #171717;
/* Surface Colors */
--color-background: #ffffff;
--color-surface: #fafafa;
--color-surface-raised: #ffffff;
--color-border: #e5e5e5;Color Accessibility Rules
- Text on backgrounds must meet WCAG AA contrast (4.5:1 normal, 3:1 large)
- Never use color alone to convey meaning (add icons, labels, patterns)
- Test with color blindness simulators
- Provide dark mode variants with equivalent contrast
Typography System
/* Font Stack */
--font-display: 'Brand Display', Georgia, serif;
--font-body: 'Brand Sans', system-ui, sans-serif;
--font-mono: 'Brand Mono', 'Fira Code', monospace;
/* Type Scale (modular scale, ratio 1.25) */
--text-xs: 0.75rem; /* 12px - captions, labels */
--text-sm: 0.875rem; /* 14px - secondary text */
--text-base: 1rem; /* 16px - body text */
--text-lg: 1.125rem; /* 18px - lead text */
--text-xl: 1.25rem; /* 20px - h4 */
--text-2xl: 1.5rem; /* 24px - h3 */
--text-3xl: 1.875rem; /* 30px - h2 */
--text-4xl: 2.25rem; /* 36px - h1 */
--text-5xl: 3rem; /* 48px - hero */
/* Line Heights */
--leading-tight: 1.25;
--leading-normal: 1.5;
--leading-relaxed: 1.75;
/* Font Weights */
--font-normal: 400;
--font-medium: 500;
--font-semibold: 600;
--font-bold: 700;Typography Rules
- Body text: minimum 16px, line-height 1.5
- Headings: use display font, tighter line-height (1.2-1.3)
- Maximum line width: 65-75 characters for readability
- Consistent heading hierarchy (never skip levels)
- Limit to 2-3 font weights per page
Spacing System
/* Spacing Scale (4px base) */
--space-1: 0.25rem; /* 4px */
--space-2: 0.5rem; /* 8px */
--space-3: 0.75rem; /* 12px */
--space-4: 1rem; /* 16px */
--space-5: 1.25rem; /* 20px */
--space-6: 1.5rem; /* 24px */
--space-8: 2rem; /* 32px */
--space-10: 2.5rem; /* 40px */
--space-12: 3rem; /* 48px */
--space-16: 4rem; /* 64px */
--space-20: 5rem; /* 80px */
--space-24: 6rem; /* 96px */Iconography
- Consistent stroke width across all icons
- Same visual weight and optical size
- Align to pixel grid
- Use a single icon library (Lucide, Phosphor, or custom set)
- Icons should be accompanied by labels for accessibility
Imagery & Photography
- Define photography style (candid vs staged, warm vs cool, etc.)
- Consistent aspect ratios for common placements
- Image treatment (filters, overlays, cropping rules)
- Illustration style guidelines (if applicable)
- Alt text requirements for all images
Voice & Tone
Brand Voice (Consistent)
Define 3-5 voice attributes with scales:
Professional ←————→ Casual
Technical ←————→ Accessible
Formal ←————→ Conversational
Authoritative ←————→ FriendlyTone Variations (Context-Dependent)
| Context | Tone | Example |
| Marketing | Confident, inspiring | "Transform how your team builds software" |
| Documentation | Clear, helpful | "To configure authentication, follow these steps" |
| Error messages | Empathetic, solution-oriented | "We couldn't save your changes. Check your connection and try again." |
| Success states | Warm, brief | "All set! Your project is ready." |
| Onboarding | Encouraging, guiding | "Great choice. Let's get your workspace set up." |
Writing Rules
- Active voice over passive ("The system processes..." not "Data is processed by...")
- Concise - Remove filler words, get to the point
- User-focused - "You can..." not "Our platform enables..."
- Consistent terminology - Maintain a glossary of approved terms
- Sentence case for UI text (not Title Case except for proper nouns)
- Oxford comma - consistent usage
- Numbers - spell out one through nine, use digits for 10+
Terminology Glossary
Maintain a glossary of:
- Product-specific terms and their definitions
- Preferred terms vs alternatives (e.g., "workspace" not "project space")
- Capitalization rules for product names and features
- Terms to avoid (competitor names, outdated terms, jargon)
Design Tokens (Code Implementation)
Tailwind Config
// tailwind.config.ts
export default {
theme: {
extend: {
colors: {
brand: {
50: 'var(--color-primary-50)',
100: 'var(--color-primary-100)',
500: 'var(--color-primary-500)',
600: 'var(--color-primary-600)',
700: 'var(--color-primary-700)',
},
},
fontFamily: {
display: ['var(--font-display)'],
body: ['var(--font-body)'],
mono: ['var(--font-mono)'],
},
borderRadius: {
brand: 'var(--radius)',
},
},
},
};Component Tokens
/* Buttons */
--button-radius: 0.5rem;
--button-font-weight: 600;
--button-padding-x: 1.25rem;
--button-padding-y: 0.625rem;
/* Cards */
--card-radius: 0.75rem;
--card-shadow: 0 1px 3px rgba(0,0,0,0.1);
--card-border: 1px solid var(--color-border);
--card-padding: var(--space-6);
/* Inputs */
--input-radius: 0.375rem;
--input-border: 1px solid var(--color-border);
--input-focus-ring: 2px solid var(--color-primary-500);
--input-padding: var(--space-2) var(--space-3);Brand Compliance Review
When reviewing UI, content, or code for brand consistency:
## VIOLATIONS - Must fix
[Logo misuse, wrong colors, off-brand copy, accessibility failures]
## INCONSISTENCIES - Should fix
[Spacing deviations, typography inconsistencies, tone mismatches]
## IMPROVEMENTS - Consider
[Opportunities to strengthen brand expression]
## POSITIVE
[Well-implemented brand elements]Review Checklist
- Colors match brand palette (no hardcoded hex values outside tokens)
- Typography uses approved fonts and scale
- Spacing follows the defined system
- Logo usage follows guidelines
- Copy matches voice and tone guidelines
- Terminology matches glossary
- Dark mode maintains brand consistency
- Accessibility standards met (contrast, labels, semantics)
- Imagery follows photography/illustration style
- Icons are from the approved set with consistent styling
For detailed references see references/assets.md
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.

