Cheggin/brand-guidelines
skills/brand-guidelines/SKILL.md
Extract and codify brand guidelines from design assets into a reusable brand configuration. Use when the user needs to establish brand consistency, extract color palettes and typography from design tokens or CSS, document voice and tone guidelines, create a brand configuration file for other agents to reference, or audit existing content for brand compliance.
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add Cheggin/skill-chain brand-guidelinesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 8:33 PM33.9s1 file scanned
SKILL.md
- name:
- brand-guidelines
- description:
- Extract and codify brand guidelines from design assets into a reusable brand configuration. Use when the user needs to establish brand consistency, extract color palettes and typography from design tokens or CSS, document voice and tone guidelines, create a brand configuration file for other agents to reference, or audit existing content for brand compliance.
- user-invocable:
- true
- group:
- strategy
- prerequisites:
- [competitor-research]
- next:
- [website-creation, social-media]
- workflows:
- [full-startup, build-lander]
Brand Guidelines Generator
Extract color palette, typography, spacing, component usage rules, and voice/tone from design assets and project configuration into a structured brand file that all content and development agents reference.
Workflow
1. Extract Visual Identity
Read existing design tokens, Figma exports, or CSS variable definitions to identify:
- Color palette: Primary, secondary, neutral, and semantic colors with hex values and documented accessible contrast ratios
- Typography: Font families, sizes, weights, and line heights for each text level (H1-H6, body, caption, etc.)
- Spacing and layout: Grid system, spacing scale, breakpoints, and layout conventions
2. Document Component Usage
For each major component, document:
- Intended use cases (do's)
- Misuse patterns (don'ts)
- Required variants (sizes, states, themes)
3. Capture Voice and Tone
Read SOUL.md or equivalent voice/tone documentation to capture:
- Writing style (active/passive voice, person, sentence length)
- Vocabulary preferences and words to avoid
- Tone variations by context (marketing, support, documentation)
4. Document Logo Usage
Capture logo rules including minimum size, clear space requirements, approved color variants, and prohibited modifications.
5. Write Brand Configuration
Write all guidelines to a structured YAML file (e.g., .harness/brand.yml):
colors:
primary: "#1A73E8"
secondary: "#..."
neutral:
100: "#..."
900: "#..."
semantic:
success: "#..."
error: "#..."
typography:
heading:
family: "Font Name"
weight: 600
body:
family: "Font Name"
size: "16px"
lineHeight: 1.5
voice:
style: "active voice, second person"
sentenceLength: "under 20 words"
tone: "confident but approachable"
6. Validate Compliance
Audit existing content and code against the documented brand guidelines. Flag violations including:
- Colors not in the approved palette
- Typography deviations from the type scale
- Content that doesn't match the documented voice/tone
Anti-Patterns
- Listing colors as "blue" and "red" without hex values or usage context
- Typography section missing font weights or line heights
- No voice/tone section, leaving content agents to guess the writing style
- Brand file that exists but is never referenced by other agents
Related Skills
Cheggin/make-interfaces-feel-better
development
VerifiedTrustedCommunity
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
1SKILL.mdUpdated Apr 29, 2026
Cheggin/writer-memory
documentation
VerifiedTrustedCommunity
Agentic memory system for writers - track characters, relationships, scenes, and themes
SKILL.mdUpdated Apr 25, 2026
Cheggin/wiki
documentation
VerifiedTrustedCommunity
LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)
SKILL.mdUpdated Apr 25, 2026
Cheggin/website-creation
development
VerifiedTrustedCommunity
Build production-quality SaaS websites with opinionated design presets. Use when creating any startup website. The user MUST pick a design style before building. Enforces shadcn/ui, Figma design principles, specific CSS values per style, and anti-AI-writing. Load alongside anti-ai-writing skill. LIGHT MODE ONLY.
SKILL.mdUpdated Apr 25, 2026