define-brand-guidelines

# Brand Guidelines Skill

Create the BRAND_GUIDELINES.md document that defines HOW to communicate with your customer. This document drives all copy and messaging: app UI, marketing, support, emails, everything.

> **Prerequisite**: CUSTOMER.md must exist. Brand guidelines without customer definition is just aesthetic preference. The voice must resonate with WHO you're talking to.

## Overview

This skill supports both **creating new brand guidelines** and **refining existing ones**.

This skill guides you through:
0. **Prerequisite Check** - Verify CUSTOMER.md exists; stop if not
1. **Discovery** - Questions about brand personality, voice, language preferences
2. **Draft Generation** - Create BRAND_GUIDELINES.md based on inputs
3. **Refinement** - Test with sample copy, iterate until voice feels right

## Workflow

### Phase 0: Prerequisite Check

**CRITICAL**: Before anything else, check for CUSTOMER.md:

1. Use Glob to search for `**/CUSTOMER.md` in the current directory
2. **If NOT found**: Stop immediately and inform the user:

```
"I can't create brand guidelines without knowing WHO you're talking to.

Please create your CUSTOMER.md first using /define-customer.

Brand voice without customer definition is just aesthetic preference - it won't resonate with anyone specific."
```

Do NOT proceed. End the workflow here.

3. **If found**: Read the CUSTOMER.md and extract key context:
   - ICP definition (who they are)
   - Pain points (what problems they have)
   - What they value (in a solution)
   - Anti-personas (who they're NOT)
   - Any language/communication hints

**IMPORTANT - Pre-fill Recommendations**: Use CUSTOMER.md to infer recommended options for all questions. Examples:

| If CUSTOMER.md says... | Recommend... |
|------------------------|--------------|
| ICP values "speed", "efficiency", "no patience" | Direct communication, short copy |
| ICP is technical (developers, engineers) | Technical language okay, precision matters |
| ICP values "data", "st