1---2name: brand-guidelines3description: Brand Guidelines4---5# Brand Guidelines67The canonical reference for [your-company]'s brand identity. Load this before creating any branded content.89## MCP connectors1011None required. This skill operates on local repo files only.1213## Personality traits1415| Trait | What it means | What it's NOT |16|-------|--------------|---------------|17| **Direct** | Say it plainly, skip the preamble | Blunt or rude |18| **Technical** | Grounded in real engineering | Jargon-heavy or gatekeeping |19| **Warm** | Peer-to-peer, peer conversation | Corporate or sycophantic |20| **Opinionated** | Take a clear stance, back it up | Arrogant or dismissive |21| **Playful** | Light touches of humor, not forced | Goofy or unprofessional |2223## Writing rules24251. **No em dashes** - never use --- or --; replace with `-` or `:`262. **No ghostwriter tells** - avoid "had a blast", "banger", "nails it", "game-changer"273. **First person** - "we" for the company, "I" for the CAO's personal content284. **Short sentences** - cut filler, tighten every line, one idea per sentence295. **Specific over generic** - numbers over adjectives, examples over claims306. **CAO's name** - always spell the CAO's name correctly (check CONTEXT.md)3132## Tone spectrum3334| Context | Tone | Example |35|---------|------|---------|36| LinkedIn post | Conversational, peer-to-peer | "Here's what broke when we..." |37| Blog article | Technical, teaching | "The query runs in 200ms because..." |38| Substack | Reflective, leadership journey | "Three months in, the numbers say..." |39| Sales email | Warm, direct, concise | "Saw your team ships dbt models - we built [your-product] for exactly this" |40| Product docs | Clear, precise, minimal | "Run `[your-cli] init` to connect your warehouse" |41| Slack community | Casual, helpful, brief | "Just shipped this - let us know what you think" |4243## Visual system4445### Colors4647| Name | Hex | Usage |48|------|-----|-------|49| Primary Black | `#1A1A1A` | Primary text, headings |50| Primary White | `#FAFAFA` | Backgrounds |51| Accent Blue | `#2563EB` | Primary accent, CTAs, links |52| Secondary Gray | `#6B7280` | Secondary text, borders |53| Light Gray | `#F3F4F6` | Card backgrounds, code blocks |5455### Typography5657| Element | Font | Weight |58|---------|------|--------|59| Headings | Inter | 600 (Semi-bold) |60| Body | Inter | 400 (Regular) |61| Code | JetBrains Mono | 400 |6263### Logo6465- Primary: horizontal lockup (icon + wordmark)66- Icon only: for small sizes (favicons, avatars)67- Minimum clear space: 1x icon height on all sides68- Never stretch, rotate, recolor, or add effects6970## Asset locations7172| Asset | Location |73|-------|----------|74| Logo files | `brand/assets/logo/` |75| Color palette | `brand/assets/colors/` |76| Font files | `brand/assets/fonts/` |77| Templates | `brand/assets/templates/` |78| Slide deck template | Canva template `[your-canva-template-id]` |79| Social media templates | `brand/assets/social/` |8081## Self-improvement8283After the CAO corrects brand usage in any content:84851. Identify which guideline was violated or missing862. If the correction reveals a rule not captured here, add it to the appropriate section873. If a tone example is outdated, replace it with the corrected version884. Update `brand/_insights.md` with the pattern (what was wrong, what the CAO wanted)895. If the correction applies across channels, update the Writing rules or Tone spectrum tables
getnao