agentleFS
brainbytes-devbrainbytes-dev/everything-claude-marketing/skills/brand/brand-guidelines/SKILL.md

brand-guidelines

Skill9 starsChanged 8 months agoMITView on GitHub

Create and enforce comprehensive brand guidelines covering visual identity, messaging, and usage rules.

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 11

    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
  1. Distinctive:

    Do you need multi-language or multi-market variations?

    line 25
  2. Distinctive:

    Do not stretch or distort

    line 47
  3. Distinctive:

    Do not change colors

    line 48
  4. Distinctive:

    Do not add effects (shadows, gradients, outlines)

    line 49
  5. Distinctive:

    Do not place on busy backgrounds without sufficient contrast

    line 51
  6. Distinctive:

    Do not rearrange elements

    line 52
  7. Distinctive:

    Do not use outdated versions

    line 53
  8. Distinctive:

    Asset library: Every guideline should link directly to the downloadable asset.

    line 176
  9. Distinctive:

    Quick-reference card: Create a one-page cheat sheet with colors, fonts, logo, and voice for daily use.

    line 180
  10. Distinctive:

    No flexibility spectrum: Not distinguishing between "must follow exactly" (logo) and "use judgment" (imagery mood).

    line 189
  11. Distinctive:

    Before shipping brand guidelines, verify:

    line 193

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brand Guidelines

When to Activate

  • Building brand guidelines from scratch for a new brand or startup
  • Updating outdated brand guidelines after a rebrand or evolution
  • Teams or agencies are misusing the brand (wrong colors, distorted logos, off-message copy)
  • Scaling the brand across new markets, products, or partners
  • Onboarding external vendors, freelancers, or co-branding partners
  • Preparing brand assets for licensing, franchising, or partnerships

First Questions

  1. Who will use these guidelines? (Internal teams, agencies, partners, franchisees?)
  2. What brand assets exist today? (Logo files, color codes, fonts, templates?)
  3. What are the most common brand misuses you see?
  4. How mature is your brand? (Startup finding its way vs established brand codifying rules?)
  5. What format should the guidelines live in? (PDF, web-based, Figma, Notion?)
  6. Do you need multi-language or multi-market variations?
  7. What level of brand flexibility do sub-teams need?

Brand Guidelines Document Structure

A complete brand guidelines document follows this hierarchy:

1. Brand Foundation

  • Brand story and origin
  • Mission, vision, and values
  • Brand positioning statement
  • Target audience overview
  • Brand personality and voice summary

2. Logo System

  • Primary logo (horizontal, stacked, icon-only)
  • Logo variations (full color, single color, reversed/white, black)
  • Clear space rules (minimum padding around the logo, usually measured in units of the logo's own proportions)
  • Minimum size requirements (print and digital)
  • Logo placement guidelines
  • Co-branding and lock-up rules
  • Logo misuse examples — show exactly what NOT to do:
    • Do not stretch or distort
    • Do not change colors
    • Do not add effects (shadows, gradients, outlines)
    • Do not rotate
    • Do not place on busy backgrounds without sufficient contrast
    • Do not rearrange elements
    • Do not use outdated versions

3. Color Palette

  • Primary colors (1-3 colors that define the brand)
  • Secondary colors (2-4 supporting colors)
  • Accent colors (for CTAs, highlights, alerts)
  • Neutral palette (backgrounds, text, borders)
  • For each color, provide: HEX, RGB, CMYK, Pantone, HSL
  • Color ratio guidance (e.g., 60% primary, 30% secondary, 10% accent)
  • Accessibility notes: contrast ratios for text on backgrounds (WCAG AA minimum)
  • Color usage rules: which colors pair, which never touch

4. Typography

  • Primary typeface (headings) — name, weights, fallback
  • Secondary typeface (body) — name, weights, fallback
  • Monospace or specialty typefaces if applicable
  • Type scale (heading sizes H1-H6, body, caption, overline)
  • Line height, letter spacing, paragraph spacing
  • Web font loading strategy (if applicable)
  • Typographic hierarchy examples

5. Imagery and Photography

  • Photography style (candid vs staged, saturated vs muted, people vs product)
  • Image treatment (filters, overlays, duotone)
  • Illustration style if applicable
  • Iconography system (line, filled, rounded, sharp)
  • Stock photo guidance (approved sources, styles to seek, styles to avoid)
  • Image composition rules

6. Voice and Messaging

  • Brand voice attributes (reference the brand-voice skill)
  • Key messaging framework (tagline, elevator pitch, boilerplate)
  • Messaging by audience segment
  • Terminology guide (approved terms, deprecated terms)

7. Layout and Composition

  • Grid system (columns, gutters, margins)
  • White space philosophy
  • Component patterns (cards, banners, CTAs)
  • Template examples (social post, email header, presentation slide)

8. Digital-Specific Guidelines

  • Favicon and app icon specifications
  • Social media avatar and cover image templates
  • Email signature design
  • Motion and animation principles
  • Dark mode adaptations

9. Application Examples

  • Business cards, letterhead, envelopes
  • Presentation templates
  • Social media templates by platform
  • Ad templates by format
  • Merchandise and swag
  • Environmental/signage

Do's and Don'ts Framework

For every guideline section, include explicit do's and don'ts. Format them as visual pairs:

DO: Use the logo on solid backgrounds with sufficient contrast.
DON'T: Place the logo on a photograph without a background container.

DO: Use the primary blue (#1A73E8) for main CTAs.
DON'T: Use red for CTAs — it's reserved for error states.

DO: Use sentence case for headlines ("Start your free trial").
DON'T: Use title case or all caps ("Start Your Free Trial" / "START YOUR FREE TRIAL").

Brand Guidelines Template Outline

# [Brand Name] Brand Guidelines
## Version [X.X] | Last Updated [Date]

### Table of Contents
1. Introduction & How to Use This Guide
2. Brand Foundation
   2.1 Our Story
   2.2 Mission & Vision
   2.3 Values
   2.4 Positioning
3. Logo
   3.1 Primary Logo
   3.2 Logo Variations
   3.3 Clear Space & Sizing
   3.4 Misuse
4. Color
   4.1 Primary Palette
   4.2 Secondary & Accent
   4.3 Neutrals
   4.4 Accessibility
5. Typography
   5.1 Typefaces
   5.2 Type Scale
   5.3 Usage Rules
6. Imagery
   6.1 Photography
   6.2 Illustration
   6.3 Iconography
7. Voice & Tone
   7.1 Voice Attributes
   7.2 Tone by Context
   7.3 Terminology
8. Layout
   8.1 Grid System
   8.2 Components
   8.3 Templates
9. Digital
   9.1 Web
   9.2 Social
   9.3 Email
10. Applications
11. Resources & Asset Downloads

Enforcement Strategies

Guidelines only work if they are used. Consider:

  1. Accessible format. Web-based guidelines (Frontify, Zeroheight, Notion) beat PDFs. Searchable, linkable, updateable.
  2. Asset library. Every guideline should link directly to the downloadable asset. Do not make people hunt.
  3. Template-first approach. Provide templates for the 10 most common use cases. Most people do not read guidelines — they open templates.
  4. Brand review checkpoints. Build brand checks into approval workflows, not just the guidelines document.
  5. Version control. Date and version the guidelines. Announce updates. Archive old versions.
  6. Quick-reference card. Create a one-page cheat sheet with colors, fonts, logo, and voice for daily use.

Common Pitfalls

  1. Over-engineering. A 100-page guidelines PDF that nobody reads. Start with essentials, expand as needed.
  2. No real examples. Abstract rules without visual examples are unenforceable.
  3. Missing asset files. Guidelines without downloadable, production-ready assets are incomplete.
  4. Static documents. Guidelines that are never updated become obsolete. Treat them as living documents.
  5. Ignoring digital. Many guidelines are still print-centric. Digital-first brands need digital-first guidelines.
  6. No flexibility spectrum. Not distinguishing between "must follow exactly" (logo) and "use judgment" (imagery mood).

Quality Gate

Before shipping brand guidelines, verify:

  • Logo system includes all variations with clear usage rules and misuse examples
  • Color palette has complete specifications (HEX, RGB, CMYK, Pantone) with accessibility notes
  • Typography section names specific fonts with a complete type scale
  • At least 10 do/don't pairs are documented with visual examples
  • Asset files are production-ready and downloadable (SVG, PNG, font files, color swatches)
  • The guidelines include application examples showing the brand in context
  • A quick-reference card or cheat sheet exists for daily use
  • Guidelines have been tested with someone unfamiliar with the brand — can they produce on-brand work?
  • Version number and last-updated date are prominently displayed

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.