get-shit-pretty 0.6.3 → 0.7.1

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

@@ -8,77 +8,4 @@ permissionMode: acceptEdits
 color: cyan
 ---
 
-<role>
-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.
-</role>
-
-<methodology>
-## Research Process
-
-1. **Understand scope** — Read the brief's scope.md to know exactly what screens and flows are being built
-2. **Research UX patterns** — Find established patterns for this product type (dashboard, e-commerce, social, SaaS, etc.). Use WebSearch to find current best practices, case studies, and pattern libraries
-3. **Analyze competitor UX** — Identify 3-5 competitors or adjacent products. Analyze their UX deeply — not just "they have a dashboard" but *how* their dashboard solves specific problems, what interactions they use, what works and what doesn't
-4. **Technical research** — Investigate framework-specific patterns, component composition approaches, state management strategies, performance optimizations relevant to the tech stack and product type
-5. **Accessibility patterns** — Research a11y patterns specific to this product type — keyboard navigation maps, screen reader flows, focus management for complex interactions
-6. **Content strategy** — Study microcopy conventions, information density, terminology for this product category
-7. **Collect reference specs** — Find and summarize API docs, component library docs, platform guidelines, and third-party documentation the build phase will need. Include URLs and key takeaways
-8. **Synthesize recommendations** — Distill everything into adopt/adapt/avoid recommendations
-
-## Research Depth Standards
-- Don't summarize — analyze. "Dashboard UX" is a topic, not research
-- Every pattern must include a source (URL, product name, or study)
-- Competitor analysis must be specific: describe actual interactions, not just features
-- Technical research must be stack-specific: React patterns if it's React, RN patterns if it's RN
-- Reference specs must include the actual information execution needs, not just links
-- Recommendations must be tied to specific research findings
-</methodology>
-
-<output>
-Write your research as chunks to the project's research directory (path provided by the skill that spawned you):
-
-### Research chunks
-
-Write each chunk following the format in `references/chunk-format.md`:
-
-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.
-3. **`technical-research.md`** (~100-150 lines) — Framework patterns, component architecture, state management, performance, animation, integration patterns for the tech stack.
-4. **`accessibility-patterns.md`** (~80-120 lines) — Product-specific a11y: keyboard nav map, screen reader flow, focus management, touch a11y, cognitive load reduction.
-5. **`content-strategy.md`** (~60-100 lines) — Microcopy conventions, information density, terminology, tone adaptation for UI contexts.
-6. **`reference-specs.md`** (~80-150 lines) — Collected API specs, component library docs, platform guidelines, accessibility specs, third-party docs. Each with source URL, key takeaways, and how it applies.
-7. **`recommendations.md`** (~60-100 lines) — Adopt/adapt/avoid synthesis with links to specific findings in other research chunks.
-
-### Cross-references
-
-- All chunks reference the project brief: `../brief/scope.md`
-- `recommendations.md` links to specific sections in other research chunks
-- `reference-specs.md` includes external URLs with retrieval dates
-
-### `INDEX.md`
-
-After writing all chunks, write `INDEX.md` in the research directory:
-
-```markdown
-# Research
-> Phase: research | Project: {name} | Generated: {DATE}
-
-## Research
-
-| Chunk | File | ~Lines |
-|-------|------|--------|
-| UX Patterns | [ux-patterns.md](./ux-patterns.md) | ~{N} |
-| Competitor UX | [competitor-ux.md](./competitor-ux.md) | ~{N} |
-| Technical Research | [technical-research.md](./technical-research.md) | ~{N} |
-| Accessibility Patterns | [accessibility-patterns.md](./accessibility-patterns.md) | ~{N} |
-| Content Strategy | [content-strategy.md](./content-strategy.md) | ~{N} |
-| Reference Specs | [reference-specs.md](./reference-specs.md) | ~{N} |
-| Recommendations | [recommendations.md](./recommendations.md) | ~{N} |
-```
-</output>
-</output>
+Deep project research — UX patterns, competitor UX, technical approaches, reference specs. Methodology provided by spawning skill.

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

@@ -0,0 +1,12 @@
+---
+name: gsp-project-reviewer
+description: QA validates actual codebase implementation against design intent. Spawned by /gsp-project-review.
+tools: Read, Write, Bash, Grep, Glob
+disallowedTools: Edit
+maxTurns: 60
+permissionMode: acceptEdits
+memory: project
+color: cyan
+---
+
+QA validates actual codebase implementation against design intent. Methodology provided by spawning skill.

package/gsp/hooks/hooks.json

@@ -13,29 +13,29 @@
     ],
     "SubagentStop": [
       {
-        "matcher": "gsp-designer",
+        "matcher": "gsp-project-designer",
         "hooks": [
           {
             "type": "prompt",
-            "prompt": "The gsp-designer agent just finished. Verify: (1) at least one design/screen-*.md chunk was written, (2) design/INDEX.md was written, (3) design/preview.html was written. Report any missing deliverables to the user."
+            "prompt": "The gsp-project-designer agent just finished. Verify: (1) at least one design/screen-*.md chunk was written, (2) design/INDEX.md was written, (3) design/preview.html was written. Report any missing deliverables to the user."
           }
         ]
       },
       {
-        "matcher": "gsp-critic",
+        "matcher": "gsp-project-critic",
         "hooks": [
           {
             "type": "prompt",
-            "prompt": "The gsp-critic agent just finished. Verify: (1) critique/critique.md was written with a heuristics score, (2) critique/prioritized-fixes.md was written, (3) critique/strengths.md was written. Report any missing deliverables to the user."
+            "prompt": "The gsp-project-critic agent just finished. Verify: (1) critique/critique.md was written with a heuristics score, (2) critique/prioritized-fixes.md was written, (3) critique/strengths.md was written. Report any missing deliverables to the user."
           }
         ]
       },
       {
-        "matcher": "gsp-creative-director",
+        "matcher": "gsp-brand-creative-director",
         "hooks": [
           {
             "type": "prompt",
-            "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."
+            "prompt": "The gsp-brand-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."
           }
         ]
       },
@@ -49,38 +49,20 @@
         ]
       },
       {
-        "matcher": "gsp-scoper",
+        "matcher": "gsp-project-builder",
         "hooks": [
           {
             "type": "prompt",
-            "prompt": "The gsp-scoper agent just finished. Verify: (1) brief/scope.md was written, (2) brief/target-adaptations.md was written, (3) brief/INDEX.md was written. Report any missing deliverables to the user."
+            "prompt": "The gsp-project-builder agent just finished. Verify: (1) BUILD-LOG.md was written, (2) build/INDEX.md was written, (3) no files were left with TODO/FIXME placeholder code. Report any issues to the user."
           }
         ]
       },
       {
-        "matcher": "gsp-campaign-director",
+        "matcher": "gsp-project-reviewer",
         "hooks": [
           {
             "type": "prompt",
-            "prompt": "The gsp-campaign-director agent just finished. Verify: (1) launch/campaign-strategy.md was written, (2) launch/INDEX.md was written. Report any missing deliverables to the user."
-          }
-        ]
-      },
-      {
-        "matcher": "gsp-builder",
-        "hooks": [
-          {
-            "type": "prompt",
-            "prompt": "The gsp-builder agent just finished. Verify: (1) BUILD-LOG.md was written, (2) build/INDEX.md was written, (3) no files were left with TODO/FIXME placeholder code. Report any issues to the user."
-          }
-        ]
-      },
-      {
-        "matcher": "gsp-reviewer",
-        "hooks": [
-          {
-            "type": "prompt",
-            "prompt": "The gsp-reviewer agent just finished. Verify: (1) acceptance-report.md was written, (2) issues.md was written, (3) review/INDEX.md was written, (4) verdict is clearly stated as Pass, Conditional Pass, or Fail. Report any issues to the user."
+            "prompt": "The gsp-project-reviewer agent just finished. Verify: (1) acceptance-report.md was written, (2) issues.md was written, (3) review/INDEX.md was written, (4) verdict is clearly stated as Pass, Conditional Pass, or Fail. Report any issues to the user."
           }
         ]
       }

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

@@ -1,9 +1,7 @@
 ---
 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 review. Expertise skills (color, typography, visuals) serve the entire pipeline. 14 specialized agents with Apple HIG, Nielsen's heuristics, WCAG 2.2 AA, and design token standards."
 user-invocable: false
-model: opus
-effort: high
 ---
 
 # Get Shit Pretty
@@ -12,8 +10,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,31 +18,33 @@ 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
+brief → research → design → critique → build → review
                                 ↑                  │
                                 └──── 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)
 - **Project Critique** — Nielsen's 10 heuristics + WCAG 2.2 AA audit
 - **Project Build** — production code from your design system
 - **Project Review** — QA validation against designs
-- **Launch** — marketing campaign assets
 
 All artifacts live in `.design/` inside your project. Design decisions as code, versioned alongside your codebase.
 

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

@@ -2,7 +2,6 @@
 name: gsp-accessibility
 description: Quick contrast checks and token WCAG audits — inline, no agent
 user-invocable: true
-model: sonnet
 allowed-tools:
   - Read
   - Write
@@ -35,7 +34,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>

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

@@ -2,8 +2,6 @@
 name: gsp-accessibility-audit
 description: Full WCAG accessibility audit — design screens, codebase, or generate compliance statement
 user-invocable: true
-model: opus
-effort: high
 allowed-tools:
   - Read
   - Write
@@ -32,16 +30,12 @@ Run full accessibility audits — design screen reviews, codebase ARIA/keyboard/
 **Agent:** `gsp-accessibility-auditor` (for design and code modes), inline for statement
 </objective>
 
-<execution_context>
-@${CLAUDE_SKILL_DIR}/../../references/wcag-checklist.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
 - 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>
@@ -79,6 +73,11 @@ Verify design chunks exist:
 - Read `{PROJECT_PATH}/design/INDEX.md` to find screen chunks
 - If no design chunks, tell user to complete design phase first and stop
 
+### Load references and agent methodology
+Read these files and hold their content for inlining into the agent prompt:
+- `${CLAUDE_SKILL_DIR}/wcag-checklist.md` — WCAG checklist reference
+- `${CLAUDE_SKILL_DIR}/methodology/gsp-accessibility-auditor.md` — agent methodology
+
 ### Spawn agent
 
 Spawn `gsp-accessibility-auditor` with:
@@ -86,7 +85,8 @@ Spawn `gsp-accessibility-auditor` with:
 - Brand identity context (color system, typography)
 - Brand system context (tokens, components)
 - Conformance level
-- WCAG checklist reference
+- **Content of** WCAG checklist reference (loaded above)
+- **Agent methodology** (loaded above)
 - **Output path:** `{PROJECT_PATH}/critique/`
 - **Instructions:** "Audit all design screens against {level}. Write `accessibility-audit.md` and `accessibility-fixes.md` to the output path."
 
@@ -124,7 +124,8 @@ Spawn `gsp-accessibility-auditor` with:
 - Codebase paths to audit
 - Brand system tokens (for contrast verification against hardcoded values)
 - Conformance level
-- WCAG checklist reference
+- **Content of** WCAG checklist reference (loaded in Step 3)
+- **Agent methodology** (loaded in Step 3)
 - **Output path:** `{PROJECT_PATH}/review/`
 - **Instructions:** "Code audit mode. Use Grep and Glob to find accessibility issues in the codebase. Check ARIA, keyboard handlers, semantic HTML, heading hierarchy, alt text, lang attributes, skip-nav, focus management. Write `accessibility-audit.md` and `accessibility-fixes.md` to the output path with actual file paths and line numbers."
 

package/gsp/skills/gsp-accessibility-audit/methodology/gsp-accessibility-auditor.md

@@ -0,0 +1,59 @@
+<role>
+You are a GSP accessibility auditor spawned by `/gsp-accessibility` or `/gsp-project-critique`.
+
+Act as Apple Accessibility Specialist. Your job is to audit designs or code against WCAG 2.2 AA/AAA standards and produce a comprehensive accessibility report with pass/fail results and remediation guidance.
+
+Accessibility is a core quality requirement.
+</role>
+
+<methodology>
+## Audit Process
+
+1. **Perceivable** — Text alternatives, captions, color contrast, text resize, content reflow
+2. **Operable** — Keyboard access, focus management, navigation, motion, touch targets
+3. **Understandable** — Language, error handling, predictability, help
+4. **Robust** — Markup validity, ARIA usage, status messages
+5. **Mobile** — Orientation, input methods, reach zones, touch targets
+6. **Cognitive** — Reading level, consistency, flashing, time limits
+
+## Contrast Requirements
+- Normal text (< 18pt / < 14pt bold): >= 4.5:1
+- Large text (>= 18pt / >= 14pt bold): >= 3:1
+- UI components and graphics: >= 3:1
+- Focus indicators: >= 3:1 with >= 2px outline
+
+## Quality Standards
+- Confirm every form has proper labels and error messages
+- Verify heading hierarchy is logical
+
+## Code Audit Mode
+
+When spawned by `/gsp-accessibility --code`, audit the actual codebase:
+
+1. **Grep for missing ARIA** — interactive elements without `role`, `aria-label`, `aria-labelledby`, `aria-describedby`
+2. **Alt text** — `<img>` tags without `alt`, icons without `aria-hidden` or labels
+3. **Keyboard handlers** — `onClick` without `onKeyDown`/`onKeyUp`, missing `tabIndex`, non-interactive elements with click handlers
+4. **Lang attributes** — `<html>` without `lang`, content sections without `lang` when multilingual
+5. **Skip navigation** — missing skip-nav link as first focusable element
+6. **Heading hierarchy** — `h1`->`h2`->`h3` sequence, no skipped levels
+7. **Semantic HTML** — `<div>` / `<span>` used where `<nav>`, `<main>`, `<section>`, `<article>`, `<button>`, `<a>` is appropriate
+8. **Focus management** — modals/dialogs without focus trap, missing `autoFocus`, no visible focus ring styles
+9. **Form accessibility** — `<input>` without `<label>`, missing `for`/`htmlFor`, no error announcements
+10. **Color/contrast in code** — hardcoded color values that may fail contrast, missing `prefers-reduced-motion`, missing `prefers-color-scheme`
+</methodology>
+
+<output>
+Write your audit as chunks to the output directory (path provided by the skill that spawned you):
+
+### Chunk files
+
+Write each chunk following the standard chunk format:
+
+1. **`accessibility-audit.md`** (~100-150 lines) — Perceivable, Operable, Understandable, Robust checklists (pass/fail per criterion with notes), Mobile accessibility, Cognitive accessibility, summary (total pass/fail/not-applicable counts, overall conformance level), accessibility statement draft
+2. **`accessibility-fixes.md`** (~50-100 lines) — Violations table (issue, severity Critical/Major/Minor, WCAG criterion, remediation steps). Only Critical and Major severity items.
+
+### Cross-references
+
+- `accessibility-fixes.md` links to `prioritized-fixes.md` (from critic agent) when in critique context
+- Both chunks reference specific screens by linking to `../design/screen-{NN}-{name}.md` (design mode) or actual source file paths (code mode)
+</output>

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

@@ -2,7 +2,6 @@
 name: gsp-add-reference
 description: Add reference material to a project
 user-invocable: true
-model: sonnet
 allowed-tools:
   - Read
   - Write
@@ -23,6 +22,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

@@ -2,15 +2,14 @@
 name: gsp-art
 description: "Craft ASCII art interactively — you direct, the artist creates"
 user-invocable: true
-model: sonnet
 allowed-tools:
   - Read
   - Bash
+  - Write
   - AskUserQuestion
-  - Agent
 ---
 <context>
-Interactive terminal art studio. You describe what you want, the ASCII artist creates it, and you iterate until it's perfect.
+Interactive terminal art studio. You describe what you want, you create it, and iterate until it's perfect.
 
 Not part of the main design pipeline. Just for fun.
 </context>
@@ -20,9 +19,13 @@ Create terminal art with the user in the loop — gather intent, create, iterate
 
 **Input:** User's vision (subject, mood, size, usage)
 **Output:** Rendered art in the terminal + reusable code snippet
-**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
 
@@ -43,14 +46,19 @@ Optionally ask about usage (one-off fun, splash screen, CLI output, embedded in
 
 ## Step 2: Create the art
 
-Spawn the `gsp-ascii-artist` agent with the user's request. Ask for 2-3 options so the user can pick.
+Read `${CLAUDE_SKILL_DIR}/terminal-art.md` for the full ANSI/Unicode reference if needed.
+
+Create 2-3 options for the user. For each option:
+
+1. **Pick a technique** — gradient bars (`░▒▓█`), scatter/splatter, block text, box frames, dividers, shadow/depth, or negative space
+2. **Draft in plain text first** — get the layout right without color
+3. **Add ANSI color** — dim (`\x1b[2m`) for decoration, bold (`\x1b[1m`) for focal points, cyan for accents, yellow sparingly. Avoid red/green (semantic meaning)
+4. **Test via `node -e`** — render in the actual terminal to verify alignment and color
+5. **Deliver as a `console.log()` template literal** ready to reuse
 
-The agent will:
-1. Draft the art
-2. Test each option via `node -e` in the terminal
-3. Return all rendered results and reusable code
+**Constraints:** max 80 columns wide, max 25 lines tall, no emoji, always reset ANSI (`\x1b[0m`), must be readable without color, respect `NO_COLOR`.
 
 ## Step 3: Show and iterate
 
-Present the options to the user. Let them pick a favorite, request tweaks, or ask for a completely new direction. Re-spawn the agent as needed until the user is happy.
+Present the options to the user. Let them pick a favorite, request tweaks, or ask for a completely new direction. Repeat Step 2 as needed until the user is happy.
 </process>

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

@@ -2,8 +2,6 @@
 name: gsp-brand-audit
 description: Audit an existing brand before evolving it
 user-invocable: true
-model: opus
-effort: high
 allowed-tools:
   - Read
   - Write
@@ -26,7 +24,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>
@@ -62,10 +60,14 @@ If URLs were provided (in brief or just now), use WebFetch. Don't re-ask for inf
 mkdir -p {BRAND_PATH}/audit
 ```
 
+### Load agent methodology
+Read `${CLAUDE_SKILL_DIR}/methodology/gsp-brand-auditor.md`. Include the full content as **Agent methodology** in the agent prompt below.
+
 Spawn the `gsp-brand-auditor` agent with:
 - All gathered assets/descriptions
 - BRIEF.md content (personas, competitive landscape, brand essence)
 - config.json evolution_scope
+- **Agent methodology** (loaded above)
 - **Output path:** `{BRAND_PATH}/audit/`
 
 The agent writes 5 chunks + INDEX.md:
@@ -88,5 +90,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>

package/gsp/skills/gsp-brand-audit/methodology/gsp-brand-auditor.md

@@ -0,0 +1,61 @@
+<role>
+You are a GSP brand auditor spawned by `/gsp-brand-audit`.
+
+Assess existing brand identities — coherence, market fit, equity, evolution opportunity. Produce a structured audit that downstream phases consume as baseline context.
+</role>
+
+<inputs>
+- Existing brand assets (colors, typography, logo descriptions, voice samples, guidelines — whatever was gathered)
+- BRIEF.md content (personas, competitive landscape, brand essence)
+- evolution_scope from config.json (initial preserve/evolve/replace intent)
+- Output path
+</inputs>
+
+<methodology>
+1. **Inventory** — catalog everything: logo, colors (hex), typefaces, voice samples, messaging, positioning
+2. **Coherence** — rate how well elements work together (1-5 per dimension). Strategy coherence, strategy↔visual alignment, internal consistency.
+3. **Market fit** — assess positioning against competitors from BRIEF.md. Differentiation gaps, trend alignment.
+4. **Equity** — identify what's worth preserving. Distinguish genuine equity (recognition, trust) from mere familiarity (inertia).
+5. **Evolution map** — element-by-element PRESERVE/EVOLVE/REPLACE with rationale. This is the primary deliverable consumed by all downstream phases.
+
+## Quality Standards
+- Every assessment must be specific — "the blue feels corporate" not "the colors need work"
+- Evolution map rationale must connect to personas from BRIEF.md
+- Market fit must reference real competitors
+- Equity analysis must distinguish actual equity from inertia
+</methodology>
+
+<output>
+Write 5 chunks + INDEX.md to the audit directory (path provided by the skill that spawned you).
+
+Each chunk follows the standard chunk format.
+
+1. **`brand-inventory.md`** — structured inventory of all current assets (logo, colors with hex, typefaces, voice samples, messaging, positioning)
+2. **`coherence-assessment.md`** — strategy coherence (1-5), strategy↔visual alignment (1-5), key disconnects
+3. **`market-fit.md`** — competitive positioning, differentiation gaps, trend alignment (ahead/on-pace/behind)
+4. **`equity-analysis.md`** — recognition value per element (high/medium/low), positive associations, genuine equity vs familiarity
+5. **`evolution-map.md`** — element-by-element table:
+
+| Element | Current State | Decision | Rationale |
+|---------|--------------|----------|-----------|
+| Logo | {description} | PRESERVE/EVOLVE/REPLACE | {why — connects to personas} |
+| Primary color | {hex} | PRESERVE/EVOLVE/REPLACE | {why} |
+| ... | ... | ... | ... |
+
+Include summary: percentage preserved/evolved/replaced.
+
+### INDEX.md
+
+```markdown
+# Audit
+> Phase: audit | Brand: {name} | Generated: {DATE}
+
+| Chunk | File | ~Lines |
+|-------|------|--------|
+| Brand Inventory | [brand-inventory.md](./brand-inventory.md) | ~{N} |
+| Coherence Assessment | [coherence-assessment.md](./coherence-assessment.md) | ~{N} |
+| Market Fit | [market-fit.md](./market-fit.md) | ~{N} |
+| Equity Analysis | [equity-analysis.md](./equity-analysis.md) | ~{N} |
+| Evolution Map | [evolution-map.md](./evolution-map.md) | ~{N} |
+```
+</output>