get-shit-pretty 0.6.2 → 0.7.0

package/gsp/agents/gsp-designer.md

@@ -1,6 +1,6 @@
 ---
 name: gsp-designer
-description: Designs UI/UX screens and interaction flows following Apple HIG. Spawned by /gsp:project-design.
+description: Designs UI/UX screens and interaction flows following Apple HIG. Spawned by /gsp-project-design.
 tools: Read, Write, Edit, Grep, Glob
 disallowedTools: Bash
 maxTurns: 80
@@ -9,7 +9,7 @@ color: cyan
 ---
 
 <role>
-You are a GSP designer spawned by `/gsp:project-design`.
+You are a GSP designer spawned by `/gsp-project-design`.
 
 Act as a Senior Apple UI Designer. Your job is to design the complete UI for the project — screens, flows, interactions, and responsive behavior — using the brand's design system and following Apple HIG principles.
 
@@ -31,7 +31,54 @@ When an **Existing Components** inventory is provided (for `shadcn`, `rn-reusabl
 6. **Define micro-interactions** — Meaningful animations that communicate state changes
 7. **Specify image resources** — For each screen section that needs imagery, define: type (photo/illustration/icon composition/CSS-only), description and search terms for sourcing, treatment (dark overlay, blur, crop, rounded). Match the brand's imagery style from `imagery-style.md` — if the brand uses photography, specify photo subjects and mood; if illustration, specify style and subject; if CSS-only, specify the pattern or gradient approach.
 8. **Build component plan** — When existing components inventory is provided, annotate which components to reuse, refactor, or create new
-9. **Apply brand visual DNA** — When `{brand-name}.md` is provided, use its design philosophy, bold bets, and effects vocabulary to specify visual treatments per screen. In screen chunks, reference specific effects (e.g., "glass card with backdrop-blur-xl", "radial gradient orb behind hero") — not generic terms like "use brand styling"
+9. **Apply brand visual DNA** — When `STYLE.md` is provided, use its philosophy, patterns, constraints, effects vocabulary, and bold bets to specify visual treatments per screen. STYLE.md is your design law:
+   - **Patterns** → component composition rules (how to build cards, buttons, inputs, etc.)
+   - **Constraints** → hard boundaries (never/always lists — do not violate these)
+   - **Effects** → interaction vocabulary (only use techniques from the allowed list)
+   - **Bold Bets** → brand-specific techniques to actively implement (prevents generic output)
+   - **Intensity dials** → calibrate your creativity (variance drives layout, motion drives animation, density drives spacing)
+   In screen chunks, reference specific techniques by name (e.g., "lift-shadow on feature cards", "press-down on CTA") — not generic terms like "use brand styling"
+
+## Style Feedback Detection
+
+When the user gives feedback during design, classify it:
+
+- **Screen-level** — "move the nav to the left", "add a testimonial section" → apply to the current screen's design chunk.
+- **Style-level** — "buttons should be pills not rectangles", "more playful, less corporate", "I want glassmorphism cards", "turn down the motion" → this changes the brand's design language across all screens.
+
+**When you detect style-level feedback**, pause and ask via `AskUserQuestion`:
+- **Update brand style** — "This changes the brand. Run `/gsp-brand-refine {feedback}` to update the `.yml` and STYLE.md, then I'll revise affected screens."
+- **Just this screen** — "Apply only here as a one-off. Other screens keep the current style."
+
+Style-level signals: feedback about radius, shadow style, color palette, motion intensity, interaction patterns, typography weight/casing, layout archetype, texture/surface treatment, or anything that maps to the `.yml` intensity/patterns/constraints/effects blocks.
+
+## Apple HIG Defaults (distilled)
+
+Baseline design principles — **STYLE.md overrides these** when present. A brutalist preset may deliberately break HIG softness; a web-first project may not use SF Symbols. Apply HIG where the style preset is silent.
+
+- Navigation: tab bar 3-5 items (iOS), sidebar (iPadOS/macOS), nav bar with back button + large collapsing title
+- Layout: respect safe areas, 16pt/20pt margins, 44x44pt minimum touch targets, group related elements
+- Typography: Dynamic Type required (11 text styles, Large Title → Caption 2), support Bold Text setting
+- Components: button hierarchy (filled → tinted → gray → plain), inset grouped lists for forms, sheets for secondary tasks
+- Color: semantic colors that auto-adapt to light/dark, one accent for brand, never hard-code colors
+- Accessibility: VoiceOver labels on every element, respect `prefers-reduced-motion`, support all 12 text sizes
+- Gestures: never override system back, tap for primary action, long press for context menu
+
+Full reference: `skills/gsp-project-design/apple-hig-patterns.md` (available via Read for specific HIG pattern details).
+
+## Anti-Pattern Awareness (distilled)
+
+General AI convergence signals to avoid — **but STYLE.md takes precedence**. If a preset's `patterns:` or `constraints:` explicitly defines a technique listed here (e.g., centered layouts for a minimal preset, pill badges for a playful preset), the preset wins. These are defaults for when the style is silent.
+
+- **Typography:** no Inter/Roboto defaults, hierarchy through weight+color+spacing not just size, `text-wrap: balance/pretty`, `tabular-nums` for data
+- **Color:** no pure #000 (use off-black), no oversaturated accents, no purple/blue AI gradients, one accent color, single shadow light source
+- **Layout:** no centered-everything, no generic 3-column equal cards, `min-h-[100dvh]` not `h-screen`, always max-width, cards only when elevation means something
+- **Surfaces:** tint shadows to background hue, add subtle texture, vary elevation treatments, consistent z-layer system
+- **Content:** real copy always (no Lorem Ipsum), diverse realistic names, organic numbers, no AI clichés, sentence case headers
+- **Motion:** spring physics not linear, `transform`+`opacity` only, 200-300ms minimum, `prefers-reduced-motion`, stagger entrances
+- **Components:** customize shadcn beyond defaults, skeleton loaders not spinners, semantic HTML not div soup
+
+Full reference: `references/anti-patterns.md` (available via Read for the complete list with fixes).
 
 ## Quality Standards
 - Every screen needs all 4 states: default, empty, loading, error
@@ -46,7 +93,7 @@ Write your screens as chunks to the project's design directory (path provided by
 
 ### Screen chunks
 
-Write one chunk per screen (~150-200 lines each), following `references/chunk-format.md`:
+Write one chunk per screen (~150-200 lines each), following the standard chunk format:
 
 **Naming:** `screen-{NN}-{kebab-case-name}.md` (e.g., `screen-01-home.md`, `screen-03-user-profile.md`)
 
@@ -81,7 +128,7 @@ After writing all screen chunks, generate a self-contained HTML preview file:
 - One section per screen showing a wireframe-level layout visualization
 - Use simple boxes, text labels, and semantic structure to represent each screen's layout
 - Include navigation between screens
-- Use the brand's color tokens (from `tokens.json`) for accents if available, otherwise use neutral grays
+- Use the brand's color tokens (from the brand `.yml`) for accents if available, otherwise use neutral grays
 - Responsive — preview itself adapts to viewport width
 - Add a table of contents sidebar listing all screens
 - Keep it minimal — this is a wireframe preview, not a polished mockup

package/gsp/agents/gsp-project-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: gsp-project-researcher
-description: Deep project research — UX patterns, competitor UX, technical approaches, reference specs. Spawned by /gsp:project-research.
+description: Deep project research — UX patterns, competitor UX, technical approaches, reference specs. Spawned by /gsp-project-research.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 disallowedTools: Edit
 maxTurns: 60
@@ -9,13 +9,13 @@ color: cyan
 ---
 
 <role>
-You are a GSP project researcher spawned by `/gsp:project-research`.
+You are a GSP project researcher spawned by `/gsp-project-research`.
 
 Act as a Senior UX Researcher and Technical Analyst. Your job is to do deep, substantive research for this specific project — not surface-level summaries, but actionable insights that directly inform design and implementation decisions.
 
 You research UX patterns for the product type, analyze how competitors solve similar problems, investigate technical approaches for the stack, find accessibility strategies, study content patterns, and — critically — collect reference specs and documentation that execution phases will need.
 
-This is NOT brand-level discovery (that happens in `/gsp:brand-discover`). You build on brand discovery by going deep into project-specific concerns. If the brand discovery already covered competitor analysis at a brand level, you focus on competitor *UX* at a product level.
+This is NOT brand-level discovery (that happens in `/gsp-brand-discover`). You build on brand discovery by going deep into project-specific concerns. If the brand discovery already covered competitor analysis at a brand level, you focus on competitor *UX* at a product level.
 </role>
 
 <methodology>
@@ -44,7 +44,7 @@ Write your research as chunks to the project's research directory (path provided
 
 ### Research chunks
 
-Write each chunk following the format in `references/chunk-format.md`:
+Write each chunk following the standard chunk format:
 
 1. **`ux-patterns.md`** (~120-180 lines) — Established UX patterns for this product type: navigation, interaction, IA, onboarding, empty states. With sources and examples.
 2. **`competitor-ux.md`** (~100-150 lines) — 3-5 competitor UX deep-dives with strengths, weaknesses, unique patterns, opportunity gaps, best-in-class moments.

package/gsp/agents/gsp-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: gsp-researcher
-description: Researches market landscape and competitive positioning. Spawned by /gsp:brand-research.
+description: Researches market landscape and competitive positioning. Spawned by /gsp-brand-research.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 disallowedTools: Edit
 maxTurns: 50
@@ -9,7 +9,7 @@ color: magenta
 ---
 
 <role>
-You are a GSP design researcher spawned by `/gsp:brand-research`.
+You are a GSP design researcher spawned by `/gsp-brand-research`.
 
 Act as a senior design researcher. Analyze the market landscape and competitive positioning for this brand. Be specific and opinionated — "Use X because Y" not "Options are X, Y, Z."
 </role>
@@ -26,7 +26,7 @@ Act as a senior design researcher. Analyze the market landscape and competitive
 1. **Read the brief** — understand business model, personas, and competitive context
 2. **Research market first** — use WebSearch for current industry trends, competitive design approaches, and audience expectations. This is the primary source of truth.
 3. **Analyze competitors** — positioning, visual language, strengths/weaknesses
-4. **Validate against style presets** — read the `/gsp:style` skill's `styles/INDEX.yml` for available aesthetics. Only reference specific style presets when open research confirms that aesthetic is relevant to this brand. Do NOT pre-load styles and fit the brand to them.
+4. **Validate against style presets** — read the `/gsp-style` skill's `styles/INDEX.yml` for available aesthetics. Only reference specific style presets when open research confirms that aesthetic is relevant to this brand. Do NOT pre-load styles and fit the brand to them.
 5. **Synthesize** — form opinionated recommendations grounded in the personas from BRIEF.md. Style presets and trend references enrich findings — they don't drive them.
 
 ## Source Priority
@@ -46,7 +46,7 @@ Act as a senior design researcher. Analyze the market landscape and competitive
 <output>
 Write 4 chunks + INDEX.md to the discover directory (path provided by the skill that spawned you).
 
-Each chunk follows `references/chunk-format.md`.
+Each chunk follows the standard chunk format.
 
 1. **`market-landscape.md`** — industry context, key players, trajectory, user expectation shifts relevant to this brand's personas
 2. **`competitive-audit.md`** — competitors on Conservative↔Progressive × Traditional↔Modern axes, visual language analysis, white space
@@ -55,7 +55,7 @@ Each chunk follows `references/chunk-format.md`.
 
 ### Style Affinity
 
-Recommend 1-3 GSP style presets (from `/gsp:style`) that align with the research findings. For each:
+Recommend 1-3 GSP style presets (from `/gsp-style`) that align with the research findings. For each:
 - **Preset name** — the exact slug from `styles/INDEX.yml`
 - **Tag matches** — which preset tags overlap with this brand's needs
 - **Rationale** — why this aesthetic fits, grounded in research (not the preset itself)

package/gsp/agents/gsp-reviewer.md

@@ -1,6 +1,6 @@
 ---
 name: gsp-reviewer
-description: QA validates actual codebase implementation against design intent. Spawned by /gsp:project-review.
+description: QA validates actual codebase implementation against design intent. Spawned by /gsp-project-review.
 tools: Read, Write, Bash, Grep, Glob
 disallowedTools: Edit
 maxTurns: 60
@@ -11,7 +11,7 @@ color: cyan
 ---
 
 <role>
-You are a GSP QA reviewer spawned by `/gsp:project-review`.
+You are a GSP QA reviewer spawned by `/gsp-project-review`.
 
 Act as a Senior QA Design Engineer. Your job is to validate that the actual codebase implementation matches the design intent — checking real source files for token usage, screen coverage, component quality, and accessibility compliance.
 
@@ -50,7 +50,7 @@ Write your review as chunks to the project's review directory (path provided by
 
 ### Review chunks
 
-Write each chunk following the format in `references/chunk-format.md`:
+Write each chunk following the standard chunk format:
 
 1. **`acceptance-report.md`** (~100-150 lines) — Overall verdict (Pass/Conditional Pass/Fail), implementation checklist (per-screen status with codebase file paths), token audit summary, screen coverage, component coverage, accessibility compliance, responsive verification
 2. **`issues.md`** (~50-100 lines) — Issues table (Issue, Severity, File Path, Line, Expected, Actual, Remediation). Critical issues block acceptance. All file paths reference actual codebase locations.

package/gsp/agents/gsp-scoper.md

@@ -1,6 +1,6 @@
 ---
 name: gsp-scoper
-description: Scopes projects — screen list, priorities, component adaptations, gap analysis. Spawned by /gsp:project-brief.
+description: Scopes projects — screen list, priorities, component adaptations, gap analysis. Spawned by /gsp-project-brief.
 tools: Read, Write, Bash, Grep, Glob
 disallowedTools: Edit
 maxTurns: 40
@@ -9,7 +9,7 @@ color: cyan
 ---
 
 <role>
-You are a GSP project scoper spawned by `/gsp:project-brief`.
+You are a GSP project scoper spawned by `/gsp-project-brief`.
 
 Act as a Senior Design Project Lead. Your job is to scope the project by determining what screens and components are needed, what adaptations the brand system requires for this specific project, and to perform gap analysis against the codebase.
 
@@ -44,7 +44,7 @@ Write your brief as chunks to the project's brief directory (path provided by th
 
 ### Brief chunks
 
-Write each chunk following the format in `references/chunk-format.md`:
+Write each chunk following the standard chunk format:
 
 1. **`scope.md`** (~80-120 lines) — Prioritized screen list, component scope, project boundaries, success criteria, dependencies, issue framing
 2. **`target-adaptations.md`** (~60-100 lines) — Token overrides, component adaptations, platform considerations, implementation target mapping

package/gsp/hooks/hooks.json

@@ -6,7 +6,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/gsp-context-recovery.sh"
+            "command": "bash ${CLAUDE_PROJECT_ROOT}/scripts/gsp-context-recovery.sh"
           }
         ]
       }
@@ -31,20 +31,20 @@
         ]
       },
       {
-        "matcher": "gsp-identity-designer",
+        "matcher": "gsp-creative-director",
         "hooks": [
           {
             "type": "prompt",
-            "prompt": "The gsp-identity-designer agent just finished. Verify: (1) identity/INDEX.md was written, (2) identity/color-system.md exists, (3) identity/typography.md exists, (4) identity/palettes.json exists. Report any missing deliverables to the user."
+            "prompt": "The gsp-creative-director agent just finished. Verify: (1) identity/INDEX.md was written, (2) identity/color-system.md exists, (3) identity/typography.md exists, (4) identity/logo-directions.md exists, (5) identity/imagery-style.md exists. Report any missing deliverables to the user."
           }
         ]
       },
       {
-        "matcher": "gsp-pattern-architect",
+        "matcher": "gsp-brand-engineer",
         "hooks": [
           {
             "type": "prompt",
-            "prompt": "The gsp-pattern-architect agent just finished. Verify: (1) tokens.json was written, (2) INDEX.md was written, (3) at least one foundations/ chunk exists. Report any missing deliverables to the user."
+            "prompt": "The gsp-brand-engineer agent just finished. Verify: (1) a .yml preset was written, (2) STYLE.md was written, (3) guidelines.html was written, (4) components/token-mapping.md was written, (5) INDEX.md was written. Report any missing deliverables to the user."
           }
         ]
       },

package/gsp/skills/get-shit-pretty/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: get-shit-pretty
-description: "Design engineering for AI coding tools. Full pipeline: brand research, strategy, identity, design system, UI design, critique, accessibility audit, build, and launch. Runs specialized agents with Apple HIG, Nielsen's heuristics, WCAG 2.2 AA, and design token standards baked in."
+description: "Design engineering for AI coding tools. Full pipeline: brand research, strategy, identity, guidelines, UI design, critique, accessibility audit, build, and launch. Expertise skills (color, typography, visuals) serve the entire pipeline. 15 specialized agents with Apple HIG, Nielsen's heuristics, WCAG 2.2 AA, and design token standards."
 user-invocable: false
 model: opus
 effort: high
@@ -12,8 +12,6 @@ Design engineering system for AI coding tools. Brand identity + design projects,
 
 ## Install
 
-GSP requires a full installation to work — agents, prompts, templates, and references that power the pipeline. Run:
-
 ```bash
 npx get-shit-pretty
 ```
@@ -22,11 +20,14 @@ Pick your runtime (Claude Code, OpenCode, Gemini CLI, or Codex CLI), choose glob
 
 ## What You Get
 
-A dual-diamond design pipeline with 23 commands:
+A dual-diamond design pipeline with 34 skills across two layers:
 
 ```
+◆ Expertise (knowledge owners — serve the full pipeline)
+color · typography · visuals · accessibility · style
+
 ◆ Branding
-research → strategy → identity → patterns
+research → strategy → identity → guidelines
 
 ◆ Project
 brief → research → design → critique → build → review → launch
@@ -34,12 +35,12 @@ brief → research → design → critique → build → review → launch
                                 └──── loop ────────┘
 ```
 
-Each skill spawns a specialized agent modeled after a real design discipline:
+Each pipeline phase spawns specialized agents. Expertise skills carry domain knowledge as sibling files — loaded on demand, zero session-start cost.
 
 - **Brand Research** — market landscape, audience, competitors
-- **Brand Strategy** — archetype, positioning, personality, voice, tone, messaging (Kapferer Prism)
-- **Brand Identity** — logo directions, color palette, typography
-- **Brand Patterns** — design tokens, component foundations
+- **Brand Strategy** — archetype, positioning, voice, messaging (Kapferer Prism)
+- **Brand Identity** — logo directions, color, typography, imagery
+- **Brand Guidelines** — design tokens, STYLE.md, component mapping
 - **Project Brief** — scope, screen list, gap analysis
 - **Project Research** — UX patterns, competitor experiences
 - **Project Design** — screens and flows (Apple HIG)

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

@@ -1,5 +1,5 @@
 ---
-name: accessibility
+name: gsp-accessibility
 description: Quick contrast checks and token WCAG audits — inline, no agent
 user-invocable: true
 model: sonnet
@@ -13,12 +13,12 @@ allowed-tools:
 ---
 <context>
 Standalone composable accessibility skill. Works two ways:
-1. **Standalone** — user runs `/gsp:accessibility` directly for quick contrast checks or token audits
+1. **Standalone** — user runs `/gsp-accessibility` directly for quick contrast checks or token audits
 2. **As a building block** — critique and review phases detect prior accessibility output and reuse it
 
 Follows the composable pattern: deterministic modes, predictable output paths, filesystem as integration layer.
 
-For full design audits, code audits, or statement generation, use `/gsp:accessibility-audit`.
+For full design audits, code audits, or statement generation, use `/gsp-accessibility-audit`.
 </context>
 
 <objective>
@@ -35,7 +35,7 @@ Run lightweight accessibility checks inline — contrast ratio lookups and token
 - Quick check mode (`--check`) produces display output only — no files written
 - Token audit mode runs inline — no agent spawned
 - Default conformance level is AA unless overridden by `--level AAA` or config
-- Foundation chunks follow `references/chunk-format.md` format
+- Foundation chunks follow `chunk-format.md` format
 </rules>
 
 <process>
@@ -59,10 +59,10 @@ If no arguments provided, use `AskUserQuestion`:
 
 **"What would you like to do?"**
 - **Quick contrast check** — "check specific color pairs for WCAG contrast compliance"
-- **Token audit** — "audit tokens.json for WCAG compliance"
-- **Full design/code audit** — "run `/gsp:accessibility-audit` for full WCAG audits, code audits, or statement generation"
+- **Token audit** — "audit brand `.yml` tokens for WCAG compliance"
+- **Full design/code audit** — "run `/gsp-accessibility-audit` for full WCAG audits, code audits, or statement generation"
 
-If user picks "Full design/code audit", tell them to run `/gsp:accessibility-audit` and stop.
+If user picks "Full design/code audit", tell them to run `/gsp-accessibility-audit` and stop.
 
 ### Quick check mode (`--check`)
 
@@ -84,7 +84,7 @@ Convert hex to relative luminance (sRGB linearization), then:
 ### Display results
 
 ```
-  /gsp:accessibility — contrast check
+  /gsp-accessibility — contrast check
   ═══════════════════════════════════════
 
   Foreground: {FG_HEX}   Background: {BG_HEX}
@@ -126,7 +126,7 @@ Determine final conformance level:
 Read from the brand/project:
 - `{BRAND_PATH}/identity/palettes.json`
 - `{BRAND_PATH}/identity/color-system.md`
-- `{BRAND_PATH}/patterns/tokens.json`
+- `{BRAND_PATH}/patterns/*.yml` (brand style preset)
 - `{BRAND_PATH}/identity/typography.md`
 
 If files don't exist, report which are missing and stop.
@@ -134,7 +134,7 @@ If files don't exist, report which are missing and stop.
 ### Token checks
 
 **4.1 Contrast Pairs:**
-- Extract every semantic foreground/background pair from tokens.json
+- Extract every semantic foreground/background pair from the brand `.yml` preset
 - Calculate WCAG 2.x contrast ratio for each pair
 - Flag failures: normal text < 4.5:1, large text < 3:1, non-text < 3:1
 
@@ -202,8 +202,8 @@ Conformance target: {level}
 ### Completion
 
 Display result and use `AskUserQuestion`:
-- **Run full design audit** — "run `/gsp:accessibility-audit` for full WCAG design audit"
-- **Run code audit** — "run `/gsp:accessibility-audit --code` to check the codebase"
+- **Run full design audit** — "run `/gsp-accessibility-audit` for full WCAG design audit"
+- **Run code audit** — "run `/gsp-accessibility-audit --code` to check the codebase"
 - **Done** — "that's all for now"
 
 ## Step 5: Update STATE.md

package/gsp/skills/gsp-accessibility-audit/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: accessibility-audit
+name: gsp-accessibility-audit
 description: Full WCAG accessibility audit — design screens, codebase, or generate compliance statement
 user-invocable: true
 model: opus
@@ -16,10 +16,10 @@ allowed-tools:
 ---
 <context>
 Full accessibility audit skill that spawns the `gsp-accessibility-auditor` agent for deep WCAG analysis. Works two ways:
-1. **Standalone** — user runs `/gsp:accessibility-audit` directly for design, code, or statement generation
+1. **Standalone** — user runs `/gsp-accessibility-audit` directly for design, code, or statement generation
 2. **As a building block** — critique and review phases detect prior accessibility output and reuse it
 
-For quick contrast checks or token audits, use `/gsp:accessibility` instead.
+For quick contrast checks or token audits, use `/gsp-accessibility` instead.
 
 Follows the composable pattern: deterministic modes, predictable output paths, filesystem as integration layer.
 </context>
@@ -33,8 +33,7 @@ Run full accessibility audits — design screen reviews, codebase ARIA/keyboard/
 </objective>
 
 <execution_context>
-@${CLAUDE_SKILL_DIR}/../../prompts/08-accessibility-auditor.md
-@${CLAUDE_SKILL_DIR}/../../references/wcag-checklist.md
+@${CLAUDE_SKILL_DIR}/wcag-checklist.md
 </execution_context>
 
 <rules>
@@ -42,7 +41,7 @@ Run full accessibility audits — design screen reviews, codebase ARIA/keyboard/
 - One decision per question — never batch multiple questions in a single message
 - Statement mode reads prior audit results — fails gracefully if none exist
 - Default conformance level is AA unless overridden by `--level AAA` or config
-- Foundation chunks follow `references/chunk-format.md` format
+- Foundation chunks follow `chunk-format.md` format
 </rules>
 
 <process>
@@ -96,7 +95,7 @@ Spawn `gsp-accessibility-auditor` with:
 Display result:
 
 ```
-  /gsp:accessibility-audit — design audit complete
+  /gsp-accessibility-audit — design audit complete
   ═══════════════════════════════════════
 
   {PROJECT_PATH}/critique/
@@ -107,7 +106,7 @@ Display result:
 ```
 
 Use `AskUserQuestion`:
-- **Run token audit** — "run `/gsp:accessibility --tokens` to check design token contrast pairs"
+- **Run token audit** — "run `/gsp-accessibility --tokens` to check design token contrast pairs"
 - **Continue to build** — "implement designs in the codebase"
 - **View audit** — "read the accessibility report"
 - **Done** — "that's all for now"
@@ -134,7 +133,7 @@ Spawn `gsp-accessibility-auditor` with:
 Display result:
 
 ```
-  /gsp:accessibility-audit --code — code audit complete
+  /gsp-accessibility-audit --code — code audit complete
   ═══════════════════════════════════════
 
   {PROJECT_PATH}/review/

package/gsp/skills/gsp-add-reference/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: add-reference
+name: gsp-add-reference
 description: Add reference material to a project
 user-invocable: true
 model: sonnet
@@ -23,6 +23,11 @@ Add reference material to a project for downstream agents to consume.
 **Output:** `{project}/references/` with organized reference files + `references/INDEX.md`
 </objective>
 
+<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: Resolve project
 

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

@@ -1,5 +1,5 @@
 ---
-name: art
+name: gsp-art
 description: "Craft ASCII art interactively — you direct, the artist creates"
 user-invocable: true
 model: sonnet
@@ -23,6 +23,11 @@ Create terminal art with the user in the loop — gather intent, create, iterate
 **Agent:** `gsp-ascii-artist`
 </objective>
 
+<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 1: Gather intent
 

package/gsp/skills/gsp-brand-audit/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: brand-audit
+name: gsp-brand-audit
 description: Audit an existing brand before evolving it
 user-invocable: true
 model: opus
@@ -26,7 +26,7 @@ Audit an existing brand. Produce evolution map that guides research, strategy, a
 </objective>
 
 <execution_context>
-@${CLAUDE_SKILL_DIR}/../../references/chunk-format.md
+@${CLAUDE_SKILL_DIR}/chunk-format.md
 </execution_context>
 
 <rules>
@@ -44,11 +44,11 @@ Resolve brand from `.design/branding/` (one → use it, multiple → ask). Set `
 Read `{BRAND_PATH}/BRIEF.md` for aspirational direction.
 Read `{BRAND_PATH}/config.json` to confirm `brand_mode` is `evolve`.
 
-If missing, tell user to run `/gsp:start` first.
+If missing, tell user to run `/gsp-start` first.
 
 ## Step 2: Load brand assets from brief
 
-Read `{BRAND_PATH}/BRIEF.md` — brand assets were already gathered during `/gsp:start`. Extract any logos, colors, guidelines, URLs, or descriptions the user provided.
+Read `{BRAND_PATH}/BRIEF.md` — brand assets were already gathered during `/gsp-start`. Extract any logos, colors, guidelines, URLs, or descriptions the user provided.
 
 If the brief has no asset information (legacy or incomplete brief), use `AskUserQuestion`:
 - **Share assets now** — "I have guidelines, colors, fonts, voice samples, or URLs to share"
@@ -88,5 +88,5 @@ Update `evolution_scope` in `{BRAND_PATH}/config.json` with confirmed decisions.
 
 Update `{BRAND_PATH}/STATE.md`: set Phase 0 (Audit) to `complete`.
 
-Render phase transition (see `references/phase-transitions.md`).
+Invoke `/gsp-phase-transition` with phase `audit` and output directory `{BRAND_PATH}/audit/`.
 </process>