applying-brand-guidelines
Skill1 starsChanged 55 days agoMITView on GitHub
Apply a brand system PROGRAMMATICALLY to generated documents and decks — colors, typography, layout and messaging — then validate the output against the guidelines and report violations. Use for ''brand this document'', ''apply our brand guidelines'', ''make this on-brand'', ''check brand compliance'', or in French ''applique la charte graphique'', ''mets ca aux couleurs de la marque'', ''verifie la conformite de marque''. Ships apply_brand.py and validate_brand.py. NOT for DESIGNING the identity (that is brand-identity) and NOT a design critique (that is critique-brand-consistency).
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- anthropics/claude-cookbooksedited, first seen Oct 24, 2026
- GoogleMakesMeBetter/claude-skills-collectionedited, first seen Feb 9, 2026
- nilecui/SkillsBaseedited, first seen Dec 27, 2025
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- anthropics/claude-cookbooks★ 54k96% same
- nilecui/SkillsBase★ 2796% same
- GoogleMakesMeBetter/claude-skills-collection★ 196% same
Wrote their own version · 0
None found.
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 repository45 other files it gives its agents.
- ad-creativeSkill
- agent-ecosystem-watchSkill
- ai-logic-osSkill
- album-masteringSkill
- alexandriaSkill
- alignment-osSkill
- analyzing-financial-statementsSkill
- blueprint-osSkill
- brainstorm-osSkill
- builder-osSkill
- changelog-adoptSkill
- cleanupSkill
- cold-emailSkill
- content-strategySkill
- creating-financial-modelsSkill
- design-osSkill
- diagramSkill
- duoSkill
- execution-osSkill
- growth-engineSkill
- habit-tracker-osSkill
- higgsfield-generateSkill
- higgsfield-soul-idSkill
- identity-shift-osSkill
- intuitive-osSkill
- journal-osSkill
- launch-strategySkill
- marketing-strategistSkill
- market-research-osSkill
- market-researchSkill
- mindset-osSkill
- monitorSkill
- nuclear-cleanupSkill
- omg-auditsSkill
- pixelragSkill
- product-marketing-contextSkill
- project-tidySkill
- ramflushSkill
- secrets-vaultSkill
- seductive-osSkill
- social-contentSkill
- staxSkill
- stepper-osSkill
- storyteller-osSkill
- watchSkill
The file
We split this skill into the rules it gives an agent
10 rules. 10 are common, 0 are distinctive, and 0 are very specific to this project.
10
Common
Most of the 3 edited versions we read keep these.
0
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
- Common: line 47
Never distort, rotate, or apply effects
- Common: line 79
No 3D effects or gradients
- Common: line 100
Clear: Avoid jargon, use simple language
- Common: line 101
Active: Use active voice, action-oriented
- Common: line 119
Use comma separators for thousands
- Common: line 136
All colors match brand palette exactly
- Common: line 138
No typos or grammatical errors
- Common: line 153
When creating any document:
- Common: line 154
Start with brand colors and fonts
- Common: line 157
Use consistent formatting throughout
“Common” is measured: kept by at least 6 in 10 of the 3 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
Corporate Brand Guidelines Skill
This skill ensures all generated documents adhere to corporate brand standards for consistent, professional communication.
Brand Identity
Company: Acme Corporation
Tagline: "Innovation Through Excellence" Industry: Technology Solutions
Visual Standards
Color Palette
Primary Colors:
- Acme Blue: #0066CC (RGB: 0, 102, 204) - Headers, primary buttons
- Acme Navy: #003366 (RGB: 0, 51, 102) - Text, accents
- White: #FFFFFF - Backgrounds, reverse text
Secondary Colors:
- Success Green: #28A745 (RGB: 40, 167, 69) - Positive metrics
- Warning Amber: #FFC107 (RGB: 255, 193, 7) - Cautions
- Error Red: #DC3545 (RGB: 220, 53, 69) - Negative values
- Neutral Gray: #6C757D (RGB: 108, 117, 125) - Secondary text
Typography
Primary Font Family: Segoe UI, system-ui, -apple-system, sans-serif
Font Hierarchy:
- H1: 32pt, Bold, Acme Blue
- H2: 24pt, Semibold, Acme Navy
- H3: 18pt, Semibold, Acme Navy
- Body: 11pt, Regular, Acme Navy
- Caption: 9pt, Regular, Neutral Gray
Logo Usage
- Position: Top-left corner on first page/slide
- Size: 120px width (maintain aspect ratio)
- Clear space: Minimum 20px padding on all sides
- Never distort, rotate, or apply effects
Document Standards
PowerPoint Presentations
Slide Templates:
- Title Slide: Company logo, presentation title, date, presenter
- Section Divider: Section title with blue background
- Content Slide: Title bar with blue background, white content area
- Data Slide: For charts/graphs, maintain color palette
Layout Rules:
- Margins: 0.5 inches all sides
- Title position: Top 15% of slide
- Bullet indentation: 0.25 inches per level
- Maximum 6 bullet points per slide
- Charts use brand colors exclusively
Excel Spreadsheets
Formatting Standards:
- Headers: Row 1, Bold, White text on Acme Blue background
- Subheaders: Bold, Acme Navy text
- Data cells: Regular, Acme Navy text
- Borders: Thin, Neutral Gray
- Alternating rows: Light gray (#F8F9FA) for readability
Chart Defaults:
- Primary series: Acme Blue
- Secondary series: Success Green
- Gridlines: Neutral Gray, 0.5pt
- No 3D effects or gradients
PDF Documents
Page Layout:
- Header: Company logo left, document title center, page number right
- Footer: Copyright notice left, date center, classification right
- Margins: 1 inch all sides
- Line spacing: 1.15
- Paragraph spacing: 12pt after
Section Formatting:
- Main headings: Acme Blue, 16pt, bold
- Subheadings: Acme Navy, 14pt, semibold
- Body text: Acme Navy, 11pt, regular
Content Guidelines
Tone of Voice
- Professional: Formal but approachable
- Clear: Avoid jargon, use simple language
- Active: Use active voice, action-oriented
- Positive: Focus on solutions and benefits
Standard Phrases
Opening Statements:
- "At Acme Corporation, we..."
- "Our commitment to innovation..."
- "Delivering excellence through..."
Closing Statements:
- "Thank you for your continued partnership."
- "We look forward to serving your needs."
- "Together, we achieve excellence."
Data Presentation
Numbers:
- Use comma separators for thousands
- Currency: $X,XXX.XX format
- Percentages: XX.X% (one decimal)
- Dates: Month DD, YYYY
Tables:
- Headers in brand blue
- Alternating row colors
- Right-align numbers
- Left-align text
Quality Standards
Before Finalizing
Always ensure:
- Logo is properly placed and sized
- All colors match brand palette exactly
- Fonts are consistent throughout
- No typos or grammatical errors
- Data is accurately presented
- Professional tone maintained
Prohibited Elements
Never use:
- Clip art or stock photos without approval
- Comic Sans, Papyrus, or decorative fonts
- Rainbow colors or gradients
- Animations or transitions (unless specified)
- Competitor branding or references
Application Instructions
When creating any document:
- Start with brand colors and fonts
- Apply appropriate template structure
- Include logo on first page/slide
- Use consistent formatting throughout
- Review against brand standards
- Ensure professional appearance
Scripts
apply_brand.py: Automatically applies brand formatting to documentsvalidate_brand.py: Checks documents for brand compliance
Notes
- These guidelines apply to all external communications
- Internal documents may use simplified formatting
- Special projects may have exceptions (request approval)
- Brand guidelines updated quarterly - check for latest version
Provenance
Vendored into OmegaOS from anthropics/claude-cookbooks @ 35f2eec — MIT (c) Anthropic. Upstream teaching notebooks live in ~/.omega/cookbooks/skills/notebooks/; the routing layer is the /cookbook skill.
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.

