brand-guidelines

Extract brand guidelines from design assets into a structured YAML configuration.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill brand-guidelines-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brand-guidelines
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/brand-guidelines
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill brand-guidelines-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • 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.
  • Document logo usage rules including minimum sizes, clear space, and accessibility considerations.
  • Validate consistency across assets and platforms against established tokens and guidelines.

Quick Start

Use the brand guidelines skill to generate a .harness/brand.yml based on current design tokens and assets.

Frequently Asked Questions about brand-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract brand guidelines from design tokens into a reusable configuration?

Extract brand guidelines by codifying design tokens, CSS references, and messaging rules into a structured YAML configuration file. This process consolidates colors, typography, and voice rules into a single brand.yml file for consistent cross-platform usage.

What is a brand configuration file and when do I need one for design systems?

A brand configuration file is a structured YAML document that codifies color palettes, typography, spacing, and voice tone from design assets. You need one to establish brand consistency and provide a referenceable blueprint for content and development agents.

Can I audit existing marketing materials for brand compliance against design tokens?

Yes, you can audit existing marketing materials by validating their consistency against established design tokens and messaging guidelines. The process checks color palettes, typography, logo usage, and voice tone to ensure cross-platform brand compliance.

How do I document logo usage rules and accessibility considerations in a brand blueprint?

Document logo usage rules by codifying minimum sizes, clear space requirements, and accessibility considerations into a structured brand configuration file. This ensures logo usage stays consistent and accessible across all design systems and marketing materials.

Does this approach work with CSS references and design tokens for maintaining brand consistency?

Yes, this approach validates brand consistency by directly referencing CSS and design tokens. It extracts color palettes and typography rules from existing project configurations to generate a unified brand.yml file for ongoing content compliance.

What's the best way to turn design tokens into a reusable brand blueprint for multiple agents?

The best way to turn design tokens into a reusable brand blueprint is to generate a structured brand.yml file in a designated directory. This configuration file codifies voice, tone, and visual rules for all downstream content and development agents to reference.