$npx -y skills add getnao/sylph --skill brand-guidelinesThe canonical reference for [your-company]'s brand identity. Load this before creating any branded content.
| 1 | # Brand Guidelines |
| 2 | |
| 3 | The canonical reference for [your-company]'s brand identity. Load this before creating any branded content. |
| 4 | |
| 5 | ## MCP connectors |
| 6 | |
| 7 | None required. This skill operates on local repo files only. |
| 8 | |
| 9 | ## Personality traits |
| 10 | |
| 11 | | Trait | What it means | What it's NOT | |
| 12 | |-------|--------------|---------------| |
| 13 | | **Direct** | Say it plainly, skip the preamble | Blunt or rude | |
| 14 | | **Technical** | Grounded in real engineering | Jargon-heavy or gatekeeping | |
| 15 | | **Warm** | Peer-to-peer, peer conversation | Corporate or sycophantic | |
| 16 | | **Opinionated** | Take a clear stance, back it up | Arrogant or dismissive | |
| 17 | | **Playful** | Light touches of humor, not forced | Goofy or unprofessional | |
| 18 | |
| 19 | ## Writing rules |
| 20 | |
| 21 | 1. **No em dashes** - never use --- or --; replace with `-` or `:` |
| 22 | 2. **No ghostwriter tells** - avoid "had a blast", "banger", "nails it", "game-changer" |
| 23 | 3. **First person** - "we" for the company, "I" for the CAO's personal content |
| 24 | 4. **Short sentences** - cut filler, tighten every line, one idea per sentence |
| 25 | 5. **Specific over generic** - numbers over adjectives, examples over claims |
| 26 | 6. **CAO's name** - always spell the CAO's name correctly (check CONTEXT.md) |
| 27 | |
| 28 | ## Tone spectrum |
| 29 | |
| 30 | | Context | Tone | Example | |
| 31 | |---------|------|---------| |
| 32 | | LinkedIn post | Conversational, peer-to-peer | "Here's what broke when we..." | |
| 33 | | Blog article | Technical, teaching | "The query runs in 200ms because..." | |
| 34 | | Substack | Reflective, leadership journey | "Three months in, the numbers say..." | |
| 35 | | Sales email | Warm, direct, concise | "Saw your team ships dbt models - we built [your-product] for exactly this" | |
| 36 | | Product docs | Clear, precise, minimal | "Run `[your-cli] init` to connect your warehouse" | |
| 37 | | Slack community | Casual, helpful, brief | "Just shipped this - let us know what you think" | |
| 38 | |
| 39 | ## Visual system |
| 40 | |
| 41 | ### Colors |
| 42 | |
| 43 | | Name | Hex | Usage | |
| 44 | |------|-----|-------| |
| 45 | | Primary Black | `#1A1A1A` | Primary text, headings | |
| 46 | | Primary White | `#FAFAFA` | Backgrounds | |
| 47 | | Accent Blue | `#2563EB` | Primary accent, CTAs, links | |
| 48 | | Secondary Gray | `#6B7280` | Secondary text, borders | |
| 49 | | Light Gray | `#F3F4F6` | Card backgrounds, code blocks | |
| 50 | |
| 51 | ### Typography |
| 52 | |
| 53 | | Element | Font | Weight | |
| 54 | |---------|------|--------| |
| 55 | | Headings | Inter | 600 (Semi-bold) | |
| 56 | | Body | Inter | 400 (Regular) | |
| 57 | | Code | JetBrains Mono | 400 | |
| 58 | |
| 59 | ### Logo |
| 60 | |
| 61 | - Primary: horizontal lockup (icon + wordmark) |
| 62 | - Icon only: for small sizes (favicons, avatars) |
| 63 | - Minimum clear space: 1x icon height on all sides |
| 64 | - Never stretch, rotate, recolor, or add effects |
| 65 | |
| 66 | ## Asset locations |
| 67 | |
| 68 | | Asset | Location | |
| 69 | |-------|----------| |
| 70 | | Logo files | `brand/assets/logo/` | |
| 71 | | Color palette | `brand/assets/colors/` | |
| 72 | | Font files | `brand/assets/fonts/` | |
| 73 | | Templates | `brand/assets/templates/` | |
| 74 | | Slide deck template | Canva template `[your-canva-template-id]` | |
| 75 | | Social media templates | `brand/assets/social/` | |
| 76 | |
| 77 | ## Self-improvement |
| 78 | |
| 79 | After the CAO corrects brand usage in any content: |
| 80 | |
| 81 | 1. Identify which guideline was violated or missing |
| 82 | 2. If the correction reveals a rule not captured here, add it to the appropriate section |
| 83 | 3. If a tone example is outdated, replace it with the corrected version |
| 84 | 4. Update `brand/_insights.md` with the pattern (what was wrong, what the CAO wanted) |
| 85 | 5. If the correction applies across channels, update the Writing rules or Tone spectrum tables |