get-shit-pretty 0.6.2 → 0.7.0

package/gsp/skills/{gsp-palette/SKILL.md → gsp-color/domains/palette.md}

@@ -1,85 +1,37 @@
----
-name: palette
-description: Generate OKLCH color palettes — standalone or as a building block for identity
-user-invocable: true
-model: sonnet
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - AskUserQuestion
-  - WebFetch
----
-<context>
-You are a GSP palette generator. You produce OKLCH 11-stop color scales from input hex colors using the tints.dev API. Downstream agents (identity-designer, system-architect, builder) consume the output files.
-
-This is a standalone composable skill. It works two ways:
-1. **Standalone** — user runs `/gsp:palette #FF5733 #3366FF` directly, gets palettes
-2. **As a building block** — identity phase detects existing palette files and reuses them
-</context>
-
-<objective>
-Generate production-ready OKLCH color palettes from hex colors.
-
-**Input:** Hex color(s), optional flags (`--preview`)
-**Output:** `palettes.json` + `color-system.md` foundation chunk in the target directory
-**Agent:** None — deterministic API calls, handled inline
-</objective>
+# Palette Generation
 
-<execution_context>
-@${CLAUDE_SKILL_DIR}/../../references/chunk-format.md
-</execution_context>
+Domain expertise for OKLCH palette generation from hex colors.
 
-<rules>
-- Always use `AskUserQuestion` for user interaction — never prompt via plain text
-- One decision per question — never batch multiple questions in a single message
-- Palettes are deterministic — same hex input always produces the same OKLCH scales
-- Foundation chunks follow `references/chunk-format.md` format exactly
-- Every palette gets the full 11-stop scale: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, 950
-- Minimum colors: primary. Secondary and accent are recommended but optional
-- Color names must be semantic (primary, secondary, accent, neutral) not literal (red, blue)
-</rules>
-
-<process>
-## Step 0: Parse invocation
+---
 
-Read the user's input to determine the mode:
+## Modes
 
 | Input | Mode |
 |-------|------|
-| `/gsp:palette #FF5733 #3366FF` | Direct — hex colors from args |
-| `/gsp:palette #FF5733 #3366FF --preview` | Preview — show scales without writing files |
-| `/gsp:palette` | Interactive — ask for colors |
+| `#hex [#hex...]` | Direct — parse hex values, assign roles in order |
+| `#hex [#hex...] --preview` | Preview — show scales without writing files |
 
-## Step 1: Collect colors
+## Color role assignment
 
-### Direct mode (hex args provided)
-
-Parse hex values from the invocation. Assign semantic roles in order:
+Parse hex values from invocation and assign semantic roles in order:
 1. First color → **primary**
 2. Second color → **secondary**
 3. Third color → **accent**
 4. Additional colors → **custom-{n}**
 
-### Interactive mode (no args)
-
-Use `AskUserQuestion` to collect colors:
+Minimum colors: primary. Secondary and accent are recommended but optional.
 
-1. **Primary color** — "What's your primary brand color? (hex code, e.g. #FF5733)"
+Color names must be semantic (primary, secondary, accent, neutral) — not literal (red, blue).
 
-2. **More colors?** — after getting primary:
-   - **Add secondary** — "I have a secondary color"
-   - **Add accent** — "I have an accent color"
-   - **Generate complements** — "suggest secondary/accent from my primary"
-   - **Just primary** — "that's enough, generate from one color"
+## Complement generation
 
-If "generate complements": calculate harmonious colors from the primary:
-- Secondary: rotate hue by 180° (complement)
-- Accent: rotate hue by 30° (analogous)
+When the user has only a primary and wants suggestions:
+- **Secondary:** rotate hue by 180 degrees (complement)
+- **Accent:** rotate hue by 30 degrees (analogous)
 
-Present the generated suggestions and let the user confirm or adjust.
+Present the generated suggestions and let the user confirm or adjust via `AskUserQuestion`.
 
-## Step 2: Generate OKLCH scales via tints.dev API
+## OKLCH scale generation via tints.dev API
 
 For each color, call the tints.dev API:
 
@@ -93,14 +45,16 @@ Where:
 
 The API returns an 11-stop OKLCH scale (50-950) with L, C, H values for each stop.
 
-Parse the response and extract the scale values.
+Every palette gets the full 11-stop scale: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, 950.
 
-## Step 3: Preview mode (`--preview`)
+Palettes are deterministic — same hex input always produces the same OKLCH scales.
 
-If `--preview`, display the scales without writing files:
+## Preview mode (`--preview`)
+
+Display scales without writing files:
 
 ```
-  /gsp:palette preview
+  /gsp-color preview
   ═══════════════════════════════════════
 
   primary (#FF5733)
@@ -120,14 +74,12 @@ If `--preview`, display the scales without writing files:
     ...
 
   ─────────────────────────────────────
-  Run /gsp:palette #FF5733 #3366FF to write files.
+  Run /gsp-color #FF5733 #3366FF to write files.
 ```
 
 Stop here. Do not write any files.
 
-## Step 4: Resolve output path
-
-Determine where to write the palette output:
+## Output path resolution
 
 ### Within a brand identity
 If a brand context exists (`.design/branding/{brand}/`):
@@ -138,15 +90,13 @@ If a brand context exists (`.design/branding/{brand}/`):
 - Write to `.design/branding/_palette/`
 - Create minimal directory structure
 
-## Step 5: Write palettes.json
+## palettes.json format
 
-If `{OUTPUT_PATH}/palettes.json` already exists, use `AskUserQuestion`: "palettes.json already exists — overwrite with new palette?" with options **Overwrite** and **Cancel**. If cancelled, skip writing palettes.json and proceed to the next step.
-
-Write `{OUTPUT_PATH}/palettes.json` with the full OKLCH scales:
+If `{OUTPUT_PATH}/palettes.json` already exists, use `AskUserQuestion`: "palettes.json already exists — overwrite with new palette?" with options **Overwrite** and **Cancel**. If cancelled, skip writing.
 
 ```json
 {
-  "$description": "OKLCH 11-stop color palettes generated by /gsp:palette",
+  "$description": "OKLCH 11-stop color palettes generated by /gsp-color",
   "$source": "tints.dev",
   "primary": {
     "source": "#FF5733",
@@ -167,9 +117,9 @@ Write `{OUTPUT_PATH}/palettes.json` with the full OKLCH scales:
 }
 ```
 
-## Step 6: Write color-system.md
+## color-system.md format (palette-only)
 
-Write `{OUTPUT_PATH}/color-system.md` as a foundation chunk per `references/chunk-format.md`:
+Write `{OUTPUT_PATH}/color-system.md` as a foundation chunk per chunk-format.md:
 
 ```markdown
 # Color System
@@ -222,16 +172,6 @@ Write `{OUTPUT_PATH}/color-system.md` as a foundation chunk per `references/chun
 | primary-900 (text) | primary-100 | Invert for readability |
 | secondary-500 | secondary-400 | Same shift as primary |
 
-## Semantic Assignments
-
-| Token | Light value | Dark value |
-|-------|-------------|------------|
-| --color-brand | primary-500 | primary-400 |
-| --color-brand-hover | primary-600 | primary-300 |
-| --color-surface | primary-50 | primary-950 |
-| --color-text | primary-900 | primary-50 |
-| --color-accent | accent-500 | accent-400 |
-
 ---
 
 ## Related
@@ -240,12 +180,10 @@ Write `{OUTPUT_PATH}/color-system.md` as a foundation chunk per `references/chun
 - [typography.md](./typography.md)
 ```
 
-## Step 7: Completion output
-
-Display the result:
+## Completion output
 
 ```
-  /gsp:palette — {n} colors scaled
+  /gsp-color — {n} colors scaled
   ═══════════════════════════════════════
 
   {OUTPUT_PATH}/
@@ -257,11 +195,3 @@ Display the result:
 
   ─────────────────────────────────────
 ```
-
-Then use `AskUserQuestion` with routing options:
-
-- **Generate type scale** — "pair these palettes with typography" → route to `/gsp:typescale`
-- **Apply a full style** — "use a style preset for the complete system" → route to `/gsp:style`
-- **Continue to identity** — "use these palettes in the branding diamond" → route to `/gsp:brand-identity`
-- **Done** — "that's all for now"
-</process>

package/gsp/skills/gsp-color/domains/system.md

@@ -0,0 +1,123 @@
+# Color System
+
+Domain expertise for full color system design — creative rationale, contrast validation, semantic mapping, dark mode.
+
+---
+
+## Modes
+
+| Input | Mode |
+|-------|------|
+| `--enrich` | Enrich existing color-system.md with technical precision |
+| *(no args)* | Interactive — explore and build a color system from scratch |
+
+## Enrich mode (`--enrich`)
+
+Read existing `{BRAND_PATH}/identity/color-system.md`. Extract chosen hex values and rationale.
+
+Read `references/color-composition.md` via `${CLAUDE_SKILL_DIR}/references/color-composition.md` for domain expertise on composition strategies.
+
+Enrich the file with:
+- OKLCH 11-stop scales via tints.dev API: `https://www.tints.dev/api/{colorName}/{hexWithoutHash}`
+- WCAG AA contrast ratios for every semantic foreground/background pair
+- Semantic color mapping (error, success, warning, info)
+- Dark mode color mapping with equivalent contrast
+- Write `palettes.json` alongside color-system.md
+
+Overwrite `color-system.md` with enriched version. Preserve the creative rationale — add technical data around it.
+
+## Interactive mode (no args)
+
+One `AskUserQuestion` at a time:
+
+1. **Starting point** — use `AskUserQuestion`:
+   - **I have hex values** — "I know my brand colors"
+   - **From a style preset** — "Start from a GSP preset palette"
+   - **Explore** — "Help me find the right palette"
+2. If exploring: ask about mood (warm/cool/neutral), energy (vibrant/muted/earthy), context (tech/health/luxury/etc.)
+3. Propose a palette with primary + secondary + accent + neutral, show hex swatches
+4. Confirm or iterate
+
+After colors are confirmed, build the full system (contrast, semantics, dark mode).
+
+## WCAG AA contrast validation
+
+Calculate contrast for every text/background pair:
+- Normal text: 4.5:1 minimum
+- Large text (18px+ or 14px+ bold): 3:1 minimum
+- Flag failures with suggested alternatives from the palette scale
+
+Test these combinations:
+- Each semantic color on white (#fff) and black (#000)
+- Primary text on secondary backgrounds and vice versa
+- All foreground/background pairs used in semantic assignments
+
+## Semantic color mapping
+
+Map brand colors to semantic roles:
+- **Primary** → CTAs, primary buttons, links
+- **Secondary** → supporting UI, secondary surfaces
+- **Accent** → highlights, badges, decorative
+
+Define standard semantic colors:
+- **Error** — red-family, distinct from brand palette
+- **Success** — green-family
+- **Warning** — amber/yellow-family
+- **Info** — blue-family (or brand secondary if blue-adjacent)
+
+Each semantic color needs its own 11-stop scale or at minimum light/default/dark stops.
+
+## Dark mode mapping
+
+Maintain equivalent contrast relationships:
+
+| Light mode | Dark mode | Rationale |
+|------------|-----------|-----------|
+| primary-500 (buttons) | primary-400 | Lighter for dark bg contrast |
+| primary-50 (bg tint) | primary-950 | Invert the tint |
+| primary-900 (text) | primary-100 | Invert for readability |
+| secondary-500 | secondary-400 | Same shift as primary |
+| neutral-50 (page bg) | neutral-950 | Full inversion |
+| neutral-900 (body text) | neutral-100 | Full inversion |
+
+## Output structure
+
+Write to the resolved output path:
+
+### color-system.md
+
+Full color system chunk (~100-150 lines) per chunk-format.md including:
+- Source colors table
+- Palette scales (all 11 stops per color)
+- Contrast audit results (pass/fail per pair)
+- Semantic color assignments (light + dark values)
+- Dark mode mapping table
+- Composition strategy recommendation (referencing color-composition.md strategies)
+
+### palettes.json
+
+Full OKLCH scales in structured JSON (same format as palette domain).
+
+### Semantic assignments template
+
+```
+| Token | Light value | Dark value |
+|-------|-------------|------------|
+| --color-brand | primary-500 | primary-400 |
+| --color-brand-hover | primary-600 | primary-300 |
+| --color-surface | primary-50 | primary-950 |
+| --color-text | primary-900 | primary-50 |
+| --color-accent | accent-500 | accent-400 |
+| --color-error | error-500 | error-400 |
+| --color-success | success-500 | success-400 |
+| --color-warning | warning-500 | warning-400 |
+| --color-info | info-500 | info-400 |
+```
+
+## Completion
+
+Display palette summary with contrast status. Offer next steps via `AskUserQuestion`:
+- **Generate type scale** — route to `/gsp-typography`
+- **Apply a full style** — route to `/gsp-style`
+- **Continue to identity** — route to `/gsp-brand-identity`
+- **Done** — "that's all for now"

package/gsp/skills/gsp-design-system/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: design-system
+name: gsp-design-system
 description: Scan and document the existing design system state
 user-invocable: true
 model: sonnet
@@ -15,8 +15,8 @@ allowed-tools:
 Composable skill that scans the workspace codebase and documents the existing design system state. Produces focused documents that downstream skills and agents consume selectively.
 
 Works two ways:
-1. **Standalone** — user runs `/gsp:design-system` for a quick workspace audit
-2. **Building block** — `/gsp:start` invokes this in the background during project setup
+1. **Standalone** — user runs `/gsp-design-system` for a quick workspace audit
+2. **Building block** — `/gsp-start` invokes this in the background during project setup
 
 Output is workspace-level (not project-scoped), so it's shared across all projects and only needs to run once per codebase state change. Re-runnable — overwrites previous output.
 </context>
@@ -35,6 +35,11 @@ Scan the codebase and produce five focused design system documents.
 @${CLAUDE_SKILL_DIR}/../../templates/system/CONCERNS.md
 </execution_context>
 
+<rules>
+- Always use `AskUserQuestion` for user interaction — never prompt via plain text
+- One decision per question — never batch multiple questions in a single message
+</rules>
+
 <process>
 ## Step 0: Prepare output directory
 
@@ -136,7 +141,7 @@ Each concern includes: file paths, severity (high/medium/low), and fix approach.
 Display a summary box:
 
 ```
-  /gsp: design-system scan complete
+  /gsp- design-system scan complete
 
   ┌──────────────────────────────────────────┐
   │  type           {classification}         │

package/gsp/skills/gsp-doctor/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: doctor
+name: gsp-doctor
 description: Check project health
 user-invocable: true
 model: sonnet
@@ -27,7 +27,7 @@ Check for `.design/` in the current directory.
 If not found:
 ```
 🩺 GSP Doctor — No project found
-   No .design/ directory detected. Run /gsp:start to start.
+   No .design/ directory detected. Run /gsp-start to start.
 ```
 Stop here.
 
@@ -68,12 +68,12 @@ If all 4 phases complete, check:
 - `identity/INDEX.md` exists (chunk format)
 - `identity/palettes.json` exists (WARN if missing)
 - `patterns/INDEX.md` exists (chunk format)
-- `patterns/tokens.json` exists (WARN if missing)
+- `patterns/*.yml` preset exists (WARN if missing)
 - If monolith exists without INDEX.md → WARN: "Legacy monolith format"
 
 **Check B4: Legacy Monolith Detection**
 For each brand phase directory (discover, strategy, identity, patterns):
-- If monolith exists but no INDEX.md → WARN: "Monolith files are no longer supported in GSP v0.6.0+. Re-run `/gsp:brand-{phase}` to generate chunk output."
+- If monolith exists but no INDEX.md → WARN: "Monolith files are no longer supported in GSP v0.6.0+. Re-run `/gsp-brand-{phase}` to generate chunk output."
 
 ### Per-Project Checks (6-phase)
 
@@ -86,12 +86,12 @@ Required dirs: brief/, research/, design/, critique/, build/, review/
 
 Check each exists:
 - All present → PASS
-- Core files missing → FAIL: list which are missing, suggest `/gsp:start`
+- Core files missing → FAIL: list which are missing, suggest `/gsp-start`
 
 **Design system check:**
 - If `.design/system/` directory exists, verify at least `STACK.md` is present → PASS
-- If `.design/system/` is missing and codebase is not greenfield → WARN: "Design system scan missing. Run `/gsp:design-system` to scan."
-- If old project-scoped `codebase/INVENTORY.md` exists → WARN: "Legacy INVENTORY.md found. Run `/gsp:design-system` to migrate to workspace-level design system docs."
+- If `.design/system/` is missing and codebase is not greenfield → WARN: "Design system scan missing. Run `/gsp-design-system` to scan."
+- If old project-scoped `codebase/INVENTORY.md` exists → WARN: "Legacy INVENTORY.md found. Run `/gsp-design-system` to migrate to workspace-level design system docs."
 
 Legacy detection: if system/, screens/, specs/, plan/ dirs exist → WARN: "Legacy structure detected — project uses old phase layout"
 
@@ -103,7 +103,7 @@ WARN if brand referenced but system not complete
 **Check P3: Brand Drift**
 Read `identity_hash` from brand.ref
 If brand identity/IDENTITY.md exists, compute current hash (first 8 chars of md5)
-If hashes differ → WARN: "Brand identity has changed since project consumed it. Consider re-running `/gsp:project-brief`."
+If hashes differ → WARN: "Brand identity has changed since project consumed it. Consider re-running `/gsp-project-brief`."
 If identity_hash is "pending" → INFO: "Brand identity wasn't complete when project was created."
 
 **Check P4: Phase Ordering**
@@ -117,7 +117,7 @@ brief < research < design < critique < build < review
 2. Valid skip scenarios (not violations):
    - design skipped when `design_scope` is `tokens`
    - research can proceed without brief
-3. build complete but critique pending → WARN: "Build completed without critique. Run `/gsp:project-critique` to audit."
+3. build complete but critique pending → WARN: "Build completed without critique. Run `/gsp-project-critique` to audit."
 4. Any other out-of-order completion → FAIL with specifics
 
 All phases in order (or validly skipped) → PASS
@@ -130,7 +130,7 @@ Only check phases that are `complete`. All paths relative to the project instanc
 
 **When `system_strategy` is `extend`:**
 - Check if brand's `patterns/` output contains "Component Audit" or "KEEP" or "RESTYLE" or "REFACTOR" or "REPLACE"
-- If none found → WARN: "Strategy is `extend` but system output lacks component audit table. Re-run `/gsp:brand-patterns`."
+- If none found → WARN: "Strategy is `extend` but system output lacks component audit table. Re-run `/gsp-brand-guidelines`."
 
 **When `implementation_target` is `shadcn`:**
 - If brief phase is complete, check brief/ output for "shadcn" or "npx shadcn"
@@ -169,7 +169,7 @@ No drift detected → PASS
 **What it catches:** Chunk directories missing, INDEX.md references broken.
 
 For each completed project phase (brief, research, design, critique, build, review):
-- Check for `{phase}/INDEX.md` — if missing → WARN: "Phase {phase} is complete but has no INDEX.md. Re-run `/gsp:{command}` to generate chunks."
+- Check for `{phase}/INDEX.md` — if missing → WARN: "Phase {phase} is complete but has no INDEX.md. Re-run `/gsp-{command}` to generate chunks."
 
 **If exports/INDEX.md exists, check for broken references:**
 - Read INDEX.md, extract all file paths from markdown links
@@ -190,7 +190,7 @@ Legacy path detection: if `screens/` exists instead of `design/` → WARN
 **design/ → brand system:**
 If both exist, extract component names referenced in design chunks (look for patterns like "Uses: {ComponentName}" or component references). Check each exists in the brand's system output.
 
-Components referenced in designs but not in system → WARN: "Design references components not defined in brand system: {list}. Re-run `/gsp:brand-patterns` to add them, or update designs."
+Components referenced in designs but not in system → WARN: "Design references components not defined in brand system: {list}. Re-run `/gsp-brand-guidelines` to add them, or update designs."
 
 **critique/ → design/:**
 If both exist, extract screen references from critique chunks. Check each referenced screen exists in design/.
@@ -229,14 +229,14 @@ No review issues → PASS
 
 **palettes.json check:**
 - If brand's identity phase is complete, check for `identity/palettes.json`
-- If missing → INFO: "No tints.dev palettes found. Re-run `/gsp:brand-identity` to generate OKLCH color palettes."
+- If missing → INFO: "No tints.dev palettes found. Re-run `/gsp-brand-identity` to generate OKLCH color palettes."
 
 No upgrade concerns → PASS
 
 ### Installation Health Checks
 
 **Check I1: Skills have `user-invocable: true`**
-Glob for all SKILL.md files in the skills directory (`{runtime-dir}/skills/*/SKILL.md` — e.g. `.claude/skills/` for Claude Code, `.opencode/skills/` for OpenCode, `.gemini/skills/` for Gemini). For each skill (except the plugin entry point `get-shit-pretty`), check frontmatter for `user-invocable: true`.
+Glob for all SKILL.md files in the skills directory (`{runtime-dir}/skills/*/SKILL.md` — e.g. `.claude/skills/` for Claude Code, `.opencode/skills/` for OpenCode, `.gemini/skills/` for Gemini). For each skill (except the entry point `get-shit-pretty`), check frontmatter for `user-invocable: true`.
 - All present → PASS
 - Missing → WARN: "Skills missing `user-invocable: true`: {list}. They won't appear in the slash-command menu. Re-run the installer or add the field manually."
 
@@ -246,7 +246,7 @@ For each gsp-* skill directory, check if `SKILL.md` references sibling files via
 - Missing siblings → FAIL: "Skill {name} references {path} but it's missing. Re-run the installer: `npx get-shit-pretty`"
 
 **Check I3: Bundle directories accessible**
-Check that the runtime bundle directories exist (`{runtime-dir}/prompts/`, `{runtime-dir}/templates/`, `{runtime-dir}/references/`). Skills reference these via `${CLAUDE_SKILL_DIR}/../../`.
+Check that the runtime bundle directories exist (`{runtime-dir}/templates/`, `{runtime-dir}/references/`). Skills reference these via `${CLAUDE_SKILL_DIR}/../../`.
 - All present → PASS
 - Missing → FAIL: "Bundle directory {dir} missing. Re-run the installer: `npx get-shit-pretty`"
 
@@ -256,6 +256,12 @@ Check `{runtime-dir}/VERSION` exists and contains a valid semver string.
 - Missing → WARN: "VERSION file missing. Re-run the installer."
 - Mismatched with source → INFO: "Installed version {installed} differs from source {source}."
 
+**Check I5: No duplicate skills (stale global install)**
+Check if `~/.claude/skills/` contains `gsp-*` directories when running from a local install. These cause duplicates between global and local.
+- Run: `ls ~/.claude/skills/ | grep '^gsp-'`
+- No matches → PASS
+- Matches found → FAIL: "Found {N} stale GSP skills in ~/.claude/skills/. Fix: run `npx get-shit-pretty --claude --local` to reinstall (the installer cleans stale globals automatically), or manually remove: `rm -rf ~/.claude/skills/gsp-*`"
+
 ### Cross-Instance Checks
 
 **Check X1: Multiple projects, same brand**
@@ -307,6 +313,7 @@ Overall Health: {SCORE}/100 {emoji}
   ✅ I2. Skill completeness ...... PASS
   ✅ I3. Bundle directories ...... PASS
   ✅ I4. VERSION file ............ PASS
+  ✅ I5. No duplicate skills ..... PASS
 
 ─── Cross-Instance ────────────────────
   ✅ X1. Brand Consistency ...... PASS
@@ -315,15 +322,15 @@ Overall Health: {SCORE}/100 {emoji}
 
 FAIL:
   • [acme-website/P1] Missing brand.ref
-    → Fix: Re-run /gsp:start to set up project with brand reference
+    → Fix: Re-run /gsp-start to set up project with brand reference
 
 WARN:
   • [acme-corp/B3] No palettes.json found
-    → Fix: Re-run /gsp:brand-identity to generate OKLCH palettes
+    → Fix: Re-run /gsp-brand-identity to generate OKLCH palettes
 
 INFO:
   • [acme-corp/P10] Config version is 0.3.0, current GSP is 0.5.0
-    → Fix: Re-run /gsp:start to upgrade config
+    → Fix: Re-run /gsp-start to upgrade config
 
 ─── Summary ───────────────────────────
 

package/gsp/skills/gsp-help/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: help
+name: gsp-help
 description: Show all skills
 user-invocable: true
 model: sonnet
@@ -26,53 +26,54 @@ Output the following as plain text. Use Unicode characters (`───`, `◇`,
 Skill names are left-padded with 4 spaces. Descriptions start at column 27 (4 indent + 23 max skill name width).
 
 ```
-  /gsp: ◇◇  v{VERSION}
+  /gsp- ◇◇  v{VERSION}
   skill reference
 
 
   ─── Getting Started ──────────────────
 
-    /gsp:start             start here — picks up where you left off
-    /gsp:help              this skill reference
-    /gsp:progress          how pretty are we?
+    /gsp-start             start here — picks up where you left off
+    /gsp-help              this skill reference
+    /gsp-progress          how pretty are we?
 
   ─── Branding ─────────────────────────
 
-    /gsp:brand-research    research your market and audience
-    /gsp:brand-strategy    define positioning, personality, voice and messaging
-    /gsp:brand-identity    create visual identity
-    /gsp:brand-patterns    build design system tokens and components
-    /gsp:brand-sync        sync brand to match a project's shipped state
-    /gsp:brand-refine      tweak brand tokens mid-project without re-running identity
-    /gsp:brand-audit       audit existing brand before evolving (optional)
+    /gsp-brand-research    research your market and audience
+    /gsp-brand-strategy    define positioning, personality, voice and messaging
+    /gsp-brand-identity    create visual identity
+    /gsp-brand-guidelines    build design system tokens and components
+    /gsp-brand-sync        sync brand to match a project's shipped state
+    /gsp-brand-refine      tweak brand tokens mid-project without re-running identity
+    /gsp-brand-audit       audit existing brand before evolving (optional)
 
   ─── Project ──────────────────────────
 
-    /gsp:project-brief     scope what you're building
-    /gsp:project-research  research UX patterns and approaches
-    /gsp:project-design    design screens and flows
-    /gsp:project-critique  critique designs + accessibility audit
-    /gsp:project-build     implement designs in the codebase
-    /gsp:project-review    QA validate implementation against designs
-    /gsp:add-reference     add reference material to a project
+    /gsp-project-brief     scope what you're building
+    /gsp-project-research  research UX patterns and approaches
+    /gsp-project-design    design screens and flows
+    /gsp-project-critique  critique designs + accessibility audit
+    /gsp-project-build     implement designs in the codebase
+    /gsp-project-review    QA validate implementation against designs
+    /gsp-add-reference     add reference material to a project
 
-  ─── Composable ──────────────────────
+  ─── Expertise ───────────────────────
 
-    /gsp:accessibility     accessibility audit — contrast, WCAG, code checks
-    /gsp:palette           generate OKLCH color palettes
-    /gsp:typescale         generate mathematical type scales
-    /gsp:style             apply a design style preset
+    /gsp-color             color systems — palettes, contrast, semantic mapping, dark mode
+    /gsp-typography        type systems — scale, pairing, fluid type, vertical rhythm
+    /gsp-visuals           visual direction — imagery, 3D, video, textures
+    /gsp-accessibility     accessibility audit — contrast, WCAG, code checks
+    /gsp-style             apply a design style preset
 
   ─── Utilities ────────────────────────
 
-    /gsp:doctor            check project health
-    /gsp:update            update GSP to latest version
-    /gsp:launch            create launch and marketing assets (optional)
+    /gsp-doctor            check project health
+    /gsp-update            update GSP to latest version
+    /gsp-launch            create launch and marketing assets (optional)
 
   ─── Easter Eggs ────────────────────
 
-    /gsp:art               ASCII art studio
-    /gsp:pretty            surprise terminal art
+    /gsp-art               ASCII art studio
+    /gsp-pretty            surprise terminal art
 
   ─── Flow ─────────────────────────────