Brand guidelines

Skill TheWatcher01/skills/.claude/skills/brand-guidelines

Applies consistent brand colors, typography, and visual identity to any output (documents, slides, web pages, components). Use when brand colors, style guidelines, visual formatting, or company design standards need to be applied.From its SKILL.md

Install

npx -y skills add TheWatcher01/skills --skill brand-guidelines

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 657 tokens by cl100k_base, as published. Nobody here has run it

Brand Styling System

Overview

This skill provides a framework for applying consistent brand identity across all outputs. Define your brand once, apply everywhere.

Keywords: branding, corporate identity, visual identity, styling, brand colors, typography, visual formatting, visual design, theming

How to Use

1. Define Your Brand (or use the default)

If no brand is specified, ask the user for their brand guidelines. A complete brand definition includes:

brand:
  name: "Your Brand"
  colors:
    primary:
      dark: "#141413"      # Primary text / dark backgrounds
      light: "#faf9f5"     # Light backgrounds / text on dark
    neutral:
      mid: "#b0aea5"       # Secondary elements
      light: "#e8e6dc"     # Subtle backgrounds
    accent:
      primary: "#d97757"   # Primary accent (CTAs, highlights)
      secondary: "#6a9bcc" # Secondary accent (links, info)
      tertiary: "#788c5d"  # Tertiary accent (success, nature)
  typography:
    headings:
      font: "Poppins"
      fallback: "Arial, sans-serif"
      min_size: "24pt"
    body:
      font: "Lora"
      fallback: "Georgia, serif"

2. Apply to Outputs

Once brand is defined, apply consistently to:

Slides/Presentations (python-pptx): Use RGBColor for precise matching
Web pages/Components: Use CSS custom properties
Documents: Apply font and color hierarchy
Diagrams: Use accent color cycling

Application Rules

Typography

Headings (24pt+): Use heading font
Body text: Use body font
Auto-fallback if custom fonts unavailable
Preserve text hierarchy and formatting

Colors

Dark backgrounds → light text, light backgrounds → dark text
Accent colors cycle through primary → secondary → tertiary for variety
Maintain contrast ratios (WCAG AA minimum)
Non-text shapes use accent colors

CSS Variables Template

:root {
  --brand-dark: #141413;
  --brand-light: #faf9f5;
  --brand-neutral: #b0aea5;
  --brand-neutral-light: #e8e6dc;
  --brand-accent-1: #d97757;
  --brand-accent-2: #6a9bcc;
  --brand-accent-3: #788c5d;
  --font-heading: 'Poppins', Arial, sans-serif;
  --font-body: 'Lora', Georgia, serif;
}

Technical Details

Font Management

Use system-installed fonts when available
Provide automatic fallbacks for cross-platform compatibility
No font installation required — works with existing system fonts

Color Application

Use RGB/hex values for precise brand matching
For python-pptx: use RGBColor class
For web: use CSS custom properties
Maintain color fidelity across systems

What ships with it: 1 file

11.1 KB alongside SKILL.md

LICENSE.txt11.1 KB

Gives 2 of the 12 instructions most marketing audience skills give in 657 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

Apply Poppins font to headingsin 41 of 690, across 6 files
Apply Lora font to body textin 41 of 690, across 6 files
Use Arial fallback for headingsin 39 of 690, across 4 files
Use Georgia fallback for body textin 39 of 690, across 4 files
Maintain text hierarchy and formattinghere, and in 39 of 690, across 4 files
Use accent colors for non-text shapeshere, and in 38 of 690, across 3 files
Use RGB values for precise color matchingin 38 of 690, across 3 files
Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
Use active voice instead of passive voicein 26 of 690, across 10 files
Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

ask the user for brand guidelines if none are specified
apply the brand definition consistently to all outputs
use the heading font for headings
use the body font for body text
auto-fallback if custom fonts are unavailable
cycle accent colors for variety

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.