get-shit-pretty 0.6.2 → 0.6.3

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

@@ -1,5 +1,5 @@
 ---
-name: project-design
+name: gsp-project-design
 description: Design screens and interaction flows
 user-invocable: true
 model: opus
@@ -28,7 +28,6 @@ Design core UI/UX screens and interaction flows.
 </objective>
 
 <execution_context>
-@${CLAUDE_SKILL_DIR}/../../prompts/03-ui-ux-pattern-master.md
 @${CLAUDE_SKILL_DIR}/../../templates/phases/design.md
 </execution_context>
 
@@ -42,7 +41,7 @@ Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 ## Step 0.5: Validate prerequisites
 
 Read `{PROJECT_PATH}/STATE.md`. Check that Brief (Phase 1) is `complete`.
-If not: "Brief hasn't been completed yet. Run `/gsp:project-brief` first." Then stop.
+If not: "Brief hasn't been completed yet. Run `/gsp-project-brief` first." Then stop.
 
 Research (Phase 2) is recommended but not required — if skipped, log: "No research artifacts found — designing from brief only."
 
@@ -67,19 +66,21 @@ If `{PROJECT_PATH}/references/` exists, scan for files (images, PDFs, markdown,
 
 Read `{BRAND_PATH}/patterns/INDEX.md`. If it exists, load all foundation chunks + selective component chunks.
 
-If it doesn't exist, tell the user to run `/gsp:brand-patterns` first.
+If it doesn't exist, tell the user to run `/gsp-brand-guidelines` first.
 
 ### Brand context (selective)
 
 Read `{BRAND_PATH}/identity/INDEX.md`. If it exists, load `color-system.md`, `typography.md`, and `imagery-style.md`.
 
-### Brand style prompt (visual DNA)
+### STYLE.md (visual DNA)
 
-Scan `{BRAND_PATH}/patterns/` for a `.md` file that is NOT `INDEX.md`, `principles.md`, or inside `foundations/` or `components/`. This is the brand's custom style prompt (`{brand-name}.md`).
+Check for `{BRAND_PATH}/patterns/STYLE.md`. This is the single document that governs all visual decisions.
 
-If found, read it. Pass to the designer agent in Step 3 as the **primary visual direction** — it contains design philosophy, bold visual bets, effects vocabulary, and component stylings with CSS/Tailwind hints.
+If found, read it. Pass to the designer agent in Step 3 as the **primary visual direction** — it contains intensity dials, component patterns, constraints (never/always), effects vocabulary, and bold bets.
 
-If not found, proceed without it (older brands may not have this file).
+If not found, fall back to scanning `{BRAND_PATH}/patterns/` for a `.md` file that is NOT `INDEX.md` or inside `components/` (legacy `{brand-name}.md` format).
+
+If neither found, proceed without it (older brands may not have this file).
 
 ### Brief (chunk-first)
 
@@ -98,7 +99,7 @@ If research doesn't exist, proceed without it (research is informative, not bloc
 **If `design_scope` is `tokens`:**
 1. Update `{PROJECT_PATH}/STATE.md` — set Phase 3 (Design) status to `skipped`
 2. Display: "Design phase skipped — design scope is `tokens`."
-3. Route: "Run `/gsp:project-build`."
+3. Route: "Run `/gsp-project-build`."
 4. Stop here.
 
 **If `design_scope` is `partial`:**
@@ -113,29 +114,28 @@ When `implementation_target` is not `figma`:
 ## Step 2.5: Load design references
 
 Read these reference files (relative to skill dir `${CLAUDE_SKILL_DIR}/../../references/`):
-- `apple-hig-patterns.md`
-- `visual-effects.md`
 - `block-patterns.md`
-- `anti-patterns.md`
 
 Hold their content for inlining into the agent prompt in Step 3.
 
+> **Note:** Apple HIG patterns and anti-patterns are distilled into the `gsp-designer` agent prompt. Visual effects are covered by STYLE.md's patterns/constraints/effects blocks (from #69). Full refs remain on disk for edge-case agent lookup.
+
 ## Step 3: Spawn designer
 
 Spawn the `gsp-designer` agent. **Inline all content** — the agent should not need to read any input files.
 
 Pass in the agent prompt:
-- **Content of** all brand patterns foundation chunks + selective component chunks (loaded in Step 1)
-- **Content of** brand identity chunks: color-system.md, typography.md, imagery-style.md (loaded in Step 1)
-- **Content of** brand style prompt ({brand-name}.md) when available
+- **Content of** STYLE.md when available — this is the primary visual direction. When STYLE.md exists, skip foundation chunks (color-system, typography, spacing, elevation, border-radius) — STYLE.md already contains this data. Only load selective component chunks.
+- **Content of** all brand patterns foundation chunks (only when STYLE.md does NOT exist — fallback for older brands)
+- **Content of** brand identity chunks: imagery-style.md (always — not covered by STYLE.md). Skip identity color-system.md and typography.md when STYLE.md exists (redundant).
 - **Content of** brief chunks: scope.md, target-adaptations.md (loaded in Step 1)
 - **Content of** research chunks: ux-patterns.md, recommendations.md, reference-specs.md (loaded in Step 1)
 - **Content of** BRIEF.md
 - **Content of** `.design/system/COMPONENTS.md`, `TOKENS.md` (when loaded in Step 2)
 - **Content of** custom references (when loaded in Step 1)
 - **Content of** critique fixes: prioritized-fixes.md, accessibility-fixes.md (when in revision mode)
-- The UI/UX Pattern Master prompt (03), design output template (from execution_context)
-- **Content of** Apple HIG patterns, visual effects, block patterns, anti-patterns references (loaded in Step 2.5)
+- Design output template (from execution_context)
+- **Content of** block patterns reference (loaded in Step 2.5)
 - `implementation_target`, `design_scope`, `codebase_type`
 - Target screens (when partial)
 - **Output path:** `{PROJECT_PATH}/design/`

package/gsp/skills/gsp-project-research/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: project-research
+name: gsp-project-research
 description: Research UX patterns and technical approaches
 user-invocable: true
 model: sonnet
@@ -17,7 +17,7 @@ allowed-tools:
 <context>
 Phase 2 of the GSP project diamond. Deep research phase that investigates UX patterns, competitor experiences, technical approaches, accessibility strategies, and content patterns specific to what this project is building.
 
-This is NOT brand-level discovery (that's `/gsp:brand-research`). This is project-level research — focused on the product type, user flows, and implementation challenges.
+This is NOT brand-level discovery (that's `/gsp-brand-research`). This is project-level research — focused on the product type, user flows, and implementation challenges.
 
 Works with the dual-diamond architecture: reads brand context from `.design/branding/{brand}/` via `brand.ref`, reads/writes project assets in `.design/projects/{project}/`.
 </context>
@@ -31,7 +31,6 @@ Deep research into UX patterns, competitor experiences, and technical approaches
 </objective>
 
 <execution_context>
-@${CLAUDE_SKILL_DIR}/../../prompts/12-project-researcher.md
 @${CLAUDE_SKILL_DIR}/../../templates/phases/research.md
 </execution_context>
 
@@ -48,7 +47,7 @@ Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 Read `{PROJECT_PATH}/brief/INDEX.md`. If it exists, load `scope.md` and `target-adaptations.md`.
 
-If brief doesn't exist, tell the user to run `/gsp:project-brief` first.
+If brief doesn't exist, tell the user to run `/gsp-project-brief` first.
 
 ### Brand system (selective)
 
@@ -73,7 +72,7 @@ Read:
 **If `design_scope` is `tokens`:**
 1. Update `{PROJECT_PATH}/STATE.md` — set Phase 2 (Research) status to `skipped`
 2. Display: "Research phase skipped — design scope is `tokens`."
-3. Route: "Run `/gsp:project-build`."
+3. Route: "Run `/gsp-project-build`."
 4. Stop here.
 
 ## Step 1.75: Pre-fetch references (background)
@@ -91,7 +90,7 @@ Pass in the agent prompt:
 - **Content of** custom references (loaded in Step 1)
 - **Content of** BRIEF.md (loaded in Step 1)
 - Any pre-fetched reference content (from Step 1.75)
-- The Project Researcher prompt (12), research output template (from execution_context)
+- Research output template (from execution_context)
 - `implementation_target`, `platform`, `tech_stack`
 - **Output path:** `{PROJECT_PATH}/research/`
 

package/gsp/skills/gsp-project-review/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: project-review
+name: gsp-project-review
 description: QA review — validate implementation against designs
 user-invocable: true
 model: opus
@@ -28,7 +28,6 @@ QA validate the codebase implementation against design intent.
 </objective>
 
 <execution_context>
-@${CLAUDE_SKILL_DIR}/../../prompts/11-deliverable-reviewer.md
 @${CLAUDE_SKILL_DIR}/../../templates/phases/review.md
 </execution_context>
 
@@ -43,7 +42,7 @@ Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 Read `{PROJECT_PATH}/config.json` to get `implementation_target`, `design_scope`, `codebase_type`.
 
-**Prior code accessibility audit:** Check if `{PROJECT_PATH}/review/accessibility-audit.md` exists from a prior `/gsp:accessibility --code` run. If yes, load it — the reviewer will reference these findings instead of performing inline a11y checks.
+**Prior code accessibility audit:** Check if `{PROJECT_PATH}/review/accessibility-audit.md` exists from a prior `/gsp-accessibility --code` run. If yes, load it — the reviewer will reference these findings instead of performing inline a11y checks.
 
 ### Load all artifacts
 
@@ -56,7 +55,7 @@ Read `{PROJECT_PATH}/config.json` to get `implementation_target`, `design_scope`
 **Design:** Read `{PROJECT_PATH}/design/INDEX.md` → load all screen chunks.
 
 **Brand patterns:** Read `{BRAND_PATH}/patterns/INDEX.md` → load foundation + component chunks.
-Also read `{BRAND_PATH}/patterns/tokens.json`.
+Also read `{BRAND_PATH}/patterns/{brand-name}.yml` (the brand's token/style source of truth).
 
 **Brand identity (selective):** Read `{BRAND_PATH}/identity/imagery-style.md` (if exists) — needed for imagery audit.
 
@@ -76,7 +75,7 @@ Also read `{BRAND_PATH}/patterns/tokens.json`.
 3. Write `{PROJECT_PATH}/review/INDEX.md`
 4. Update `{PROJECT_PATH}/exports/INDEX.md` between `<!-- BEGIN:review -->` and `<!-- END:review -->` with populated table
 5. Update `{PROJECT_PATH}/STATE.md` — set Phase 6 (Review) to `complete` or `needs-revision`
-6. Route: display verdict and suggest `/gsp:launch` or re-run `/gsp:project-review`
+6. Route: display verdict and suggest `/gsp-launch` or re-run `/gsp-project-review`
 7. **Stop here**
 
 ## Step 2: Spawn reviewer
@@ -86,14 +85,13 @@ Spawn the `gsp-reviewer` agent with:
 - Actual codebase file paths (from BUILD-LOG.md)
 - `git diff` output
 - Design chunks
-- Brand system chunks + tokens.json
+- Brand system chunks + `{brand-name}.yml`
 - Brief chunks
 - Critique fixes (to verify resolution)
 - `.design/system/COMPONENTS.md` (when exists — to verify existing components weren't broken)
 - MANIFEST.md (when exists — to verify build claims match reality)
 - `codebase_type` from config.json
-- The Deliverable Reviewer prompt (11)
-- The review output template
+- Review output template (from execution_context)
 - **Output path:** `{PROJECT_PATH}/review/`
 - Prior code accessibility findings (if `{PROJECT_PATH}/review/accessibility-audit.md` exists — tell reviewer to reference these instead of performing inline a11y checks; reviewer keeps inline checks as fallback if no prior audit exists)
 - **Clear instruction:** "Review actual codebase files, not `.design/build/` specs. Use Grep to search for hardcoded values. Use `git diff` to verify changes. Reference actual file paths in issues."
@@ -175,5 +173,5 @@ If verdict is **Fail**:
 
 Render phase transition (see `references/phase-transitions.md`). This phase has pass/fail variants — the reference covers both.
 
-If review identified brand-level issues (token values that don't work in context), note: "Some issues are brand-level — run `/gsp:brand-refine` to adjust tokens without re-running identity."
+If review identified brand-level issues (token values that don't work in context), note: "Some issues are brand-level — run `/gsp-brand-refine` to adjust tokens without re-running identity."
 </process>

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

@@ -1,5 +1,5 @@
 ---
-name: scaffold
+name: gsp-scaffold
 description: Deterministic stack setup — install deps, create configs, verify build compiles
 user-invocable: true
 model: sonnet
@@ -16,8 +16,8 @@ Composable stack setup skill. No agent — all inline Bash commands. Determinist
 Reads project config and stack state, installs dependencies, creates config files, installs component library primitives, and verifies the build compiles. Produces `SCAFFOLD-LOG.md`.
 
 Works two ways:
-1. **Standalone** — user runs `/gsp:scaffold` directly to set up a project's stack
-2. **As a building block** — `/gsp:project-build` invokes this as Phase 1 before spawning builder agents
+1. **Standalone** — user runs `/gsp-scaffold` directly to set up a project's stack
+2. **As a building block** — `/gsp-project-build` invokes this as Phase 1 before spawning builder agents
 </context>
 
 <objective>

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

@@ -1,5 +1,5 @@
 ---
-name: start
+name: gsp-start
 description: Start here — picks up where you left off
 user-invocable: true
 model: sonnet
@@ -64,7 +64,7 @@ Scan `.design/` for existing brands and projects:
 
 ### Step 1b: Run design system scan (background)
 
-Spawn `/gsp:design-system` as a background agent (`run_in_background: true`, `subagent_type: "general-purpose"`). It writes to `.design/system/` — don't wait for it. Store the task reference for the brand essence questions or Step 4.
+Spawn `/gsp-design-system` as a background agent (`run_in_background: true`, `subagent_type: "general-purpose"`). It writes to `.design/system/` — don't wait for it. Store the task reference for the brand essence questions or Step 4.
 
 ### Step 1c: Greet
 
@@ -80,7 +80,7 @@ Adapt the greeting based on what the scan revealed. Use plain text with Unicode
 - **Summary box:** `┌──┐│└──┘` border with key-value pairs inside
 
 **Fresh start (no `.design/`):**
-Show `  /gsp: ◇◇\n  looks like a fresh start.` (append codebase scanning note if `package.json` exists). Use `AskUserQuestion` with: Brand identity, Design project, Both (brand + project), Quick project.
+Show `  /gsp- ◇◇\n  looks like a fresh start.` (append codebase scanning note if `package.json` exists). Use `AskUserQuestion` with: Brand identity, Design project, Both (brand + project), Quick project.
 
 **Legacy `.design/` detected (flat structure, pre-0.4.0):**
 Acknowledge the legacy project. Use `AskUserQuestion`: Start fresh brand, Start design project, Keep working.
@@ -98,7 +98,7 @@ Show compact brand (single-line if complete) + full project pipeline flow. Then
 When codebase has been scanned (`.design/system/STACK.md` exists), show a Summary Box using data from STACK.md and COMPONENTS.md:
 ```
   ┌──────────────────────────────────────────┐
-  │  /gsp: ◆◈                               │
+  │  /gsp- ◆◈                               │
   │                                          │
   │  framework     Next.js 14               │
   │  styling       Tailwind + shadcn/ui     │
@@ -118,7 +118,7 @@ From the greeting exchange, determine which flow to run:
 - **Design project** → Check for brands first. If none exist, explain they need a brand first. Offer to create one, then auto-transition to project flow.
 - **Full design (brand + project)** → Brand flow (Step 3), with E2E flag so brand completion auto-transitions to project flow (Step 4)
 - **Quick project** → Quick flow (Step 5)
-- **Continue existing work** → route to `/gsp:progress`
+- **Continue existing work** → route to `/gsp-progress`
 
 ## Step 3: Brand flow
 
@@ -196,10 +196,10 @@ Skip any question you can already answer from prior context. Don't over-ask.
 
 6. Route using `AskUserQuestion` — always offer Continue / Stop here / What happens next:
 
-- **Brand-only, new →** continue to `/gsp:brand-research`
-- **Brand-only, evolve →** continue to `/gsp:brand-audit`
-- **E2E, new →** continue to `/gsp:brand-research` (complete the entire brand pipeline first — research → strategy → identity → patterns — then auto-transition to Step 4 for project setup). Set `"e2e": true` in config.json so brand-patterns knows to route to project flow after completion.
-- **E2E, evolve →** continue to `/gsp:brand-audit` (complete full brand pipeline, then auto-transition to Step 4). Set `"e2e": true` in config.json.
+- **Brand-only, new →** continue to `/gsp-brand-research`
+- **Brand-only, evolve →** continue to `/gsp-brand-audit`
+- **E2E, new →** continue to `/gsp-brand-research` (complete the entire brand pipeline first — research → strategy → identity → patterns — then auto-transition to Step 4 for project setup). Set `"e2e": true` in config.json so brand-patterns knows to route to project flow after completion.
+- **E2E, evolve →** continue to `/gsp-brand-audit` (complete full brand pipeline, then auto-transition to Step 4). Set `"e2e": true` in config.json.
 
 ## Step 4: Project flow
 
@@ -258,8 +258,8 @@ Skip any question you can already answer from the codebase scan. Don't over-ask.
 - `.design/projects/{name}/exports/INDEX.md` from `${CLAUDE_SKILL_DIR}/../../templates/exports-index.md`
 
 9. Route using `AskUserQuestion`: "Project set up! Ready to scope what you're building?"
-  - **Continue to scoping** — "Scope the project now" → invoke `/gsp:project-brief` via Skill tool
-  - **Stop here** — "I'll come back later" → confirm files are saved, show how to resume with `/gsp:start`
+  - **Continue to scoping** — "Scope the project now" → invoke `/gsp-project-brief` via Skill tool
+  - **Stop here** — "I'll come back later" → confirm files are saved, show how to resume with `/gsp-start`
   - **What happens next?** — "Explain the scoping phase" → explain what project-brief does (screen list, component adaptations, gap analysis) and how it uses the brief
 
 ## Step 5: Quick project flow
@@ -279,8 +279,8 @@ Read `${CLAUDE_SKILL_DIR}/../../skills/gsp-style/styles/INDEX.yml` and present s
 mkdir -p .design/branding/_style-{preset}/patterns/
 ```
 
-2. Invoke `/gsp:style {preset}` via Skill tool — this writes:
-   - `tokens.json` (W3C design tokens)
+2. Invoke `/gsp-style {preset}` via Skill tool — this writes:
+   - `{preset}.yml` (brand style preset)
    - Foundation chunks (color, typography, spacing, elevation, radius)
    - `INDEX.md`
 
@@ -324,7 +324,7 @@ Continue directly to Step 4 (project flow) with these modifications:
 ### Upgrade path
 
 If a user later wants full branding, they can:
-1. Run `/gsp:start` → "Brand identity" to create a real brand
+1. Run `/gsp-start` → "Brand identity" to create a real brand
 2. Full diamond produces identity + patterns with real tokens
 3. Update the project's `brand.ref` to point to the new brand
 4. Re-run build phases — they pick up the new tokens automatically

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

@@ -1,5 +1,5 @@
 ---
-name: style
+name: gsp-style
 description: Apply a design style — get tokens and foundations without the branding diamond
 user-invocable: true
 model: sonnet
@@ -12,10 +12,10 @@ allowed-tools:
   - Grep
 ---
 <context>
-You are a GSP style applicator. You produce W3C Design Tokens (`tokens.json`) and foundation chunks from style presets — bypassing the full branding diamond (discover → strategy → identity → system). Downstream agents (designer, builder) consume `tokens.json` regardless of how it was produced.
+You are a GSP style applicator. You produce a brand `.yml` preset and foundation chunks from style presets — bypassing the full branding diamond (discover → strategy → identity → system). Downstream agents (designer, builder) consume the `.yml` preset regardless of how it was produced.
 
 This is a standalone composable skill. It works two ways:
-1. **Standalone** — user runs `/gsp:style cyberpunk` directly, gets visual preview + tokens
+1. **Standalone** — user runs `/gsp-style cyberpunk` directly, gets visual preview + tokens
 2. **As a building block** — agents invoke this skill during workflows, getting tokens only
 </context>
 
@@ -23,7 +23,7 @@ This is a standalone composable skill. It works two ways:
 Apply a named style preset to produce production-ready design tokens and foundation chunks.
 
 **Input:** Style name(s), optional flags (`--list`, `--preview`)
-**Output:** `tokens.json` + 5 foundation chunks + `INDEX.md` in the target system directory
+**Output:** `{preset-name}.yml` + `STYLE.md` + `INDEX.md` in the target system directory
 **Agent:** None — token expansion from YAML presets is handled inline
 </objective>
 
@@ -37,7 +37,7 @@ Apply a named style preset to produce production-ready design tokens and foundat
 <rules>
 - Always use `AskUserQuestion` for user interaction — never prompt via plain text
 - One decision per question — never batch multiple questions in a single message
-- `tokens.json` follows W3C Design Tokens format from `references/design-tokens.md`
+- Token values in `.yml` presets follow W3C Design Tokens format from `references/design-tokens.md`
 - When mixing styles, later style values override earlier ones (last-wins precedence)
 - Never mix clashing styles — check the compatibility matrix first
 </rules>
@@ -49,11 +49,11 @@ Read the user's input to determine the mode:
 
 | Input | Mode |
 |-------|------|
-| `/gsp:style --list` | List all available presets |
-| `/gsp:style --preview cyberpunk` | Show tokens without writing files |
-| `/gsp:style cyberpunk` | Apply single style |
-| `/gsp:style cyberpunk + neubrutalism` | Mix styles (check compatibility) |
-| `/gsp:style` (no args) | Interactive — browse and pick |
+| `/gsp-style --list` | List all available presets |
+| `/gsp-style --preview cyberpunk` | Show tokens without writing files |
+| `/gsp-style cyberpunk` | Apply single style |
+| `/gsp-style cyberpunk + neubrutalism` | Mix styles (check compatibility) |
+| `/gsp-style` (no args) | Interactive — browse and pick |
 
 ## Step 1: List mode (`--list`)
 
@@ -120,51 +120,49 @@ If invoked from a project context (`.design/projects/{project}/`):
 
 If `--preview`, display expanded tokens grouped by section (Color, Typography, Shape, Elevation, Motion) as key-value pairs. Footer: usage hint to apply. Stop here — do not write any files.
 
-## Step 6: Expand tokens to W3C format
+## Step 6: Copy preset as brand style
 
-Transform the YAML preset tokens into the full W3C Design Tokens JSON structure.
+Copy the preset `.yml` to the output path as the brand's style source:
+- If within a brand: `{OUTPUT_PATH}/{preset-name}.yml`
+- If standalone: `{OUTPUT_PATH}/_style-{preset-name}.yml`
 
-### Token expansion mapping
+If a `.yml` already exists at the output path, use `AskUserQuestion`: "A style preset already exists — overwrite?" with options **Overwrite** and **Cancel**. If cancelled, skip and proceed.
 
-Transform each YAML preset section into W3C Design Tokens JSON with `$value` and `$type` fields:
+The `.yml` IS the token source of truth — no separate `tokens.json` needed. The builder generates CSS variables from it at build time using `references/token-mapping.md`.
 
-| Preset section | Token path | $type | Notes |
-|---------------|------------|-------|-------|
-| `color.*` | `color.brand.{key}`, `color.semantic.{key}` | `color` | Split into brand (primary, secondary, accent) and semantic (background, surface, on-primary, on-background, error, success, warning, info) |
-| `typography.*` | `font.family.{primary,mono}` | `fontFamily` | — |
-| `typography.*` | `typography.{level}` | `typography` | Composite: fontFamily, fontSize, fontWeight, lineHeight, letterSpacing. 9 levels: display, heading-1 through heading-3, body-large, body, body-small, caption, overline |
-| `spacing.*` | `spacing.{xs,sm,md,lg,xl,2xl,3xl,4xl}` | `dimension` | — |
-| `elevation.*` | `shadow.{sm,md,lg,xl}` | `shadow` | Parse CSS shadow shorthand into structured format |
-| `shape.*` | `radius.{none,sm,md,lg,full}` | `dimension` | `full` = 9999px |
-| `motion.*` | `motion.duration.{fast,normal}`, `motion.easing.default` | `duration`, `cubicBezier` | — |
+## Step 7: Write STYLE.md
 
-**Style-specific tokens:** If preset has extra groups (e.g., `glass`, `glow`, `gradient`, `syntax`), include under `$extensions.gsp-style-specific`.
+Read the style template from `${CLAUDE_SKILL_DIR}/../../templates/phases/style.md`.
 
-**Dark mode:** If preset has `dark_mode` section, include under `$extensions.dark` with semantic color overrides.
+Read BOTH source files:
+- `styles/{name}.yml` — structured data (tokens, intensity, patterns, constraints, effects)
+- `styles/{name}.md` — prose companion (design philosophy, CSS code hints, component styling, textures). Skip the `<role>` block — start from `<design-system>`.
 
-**Extensions metadata:** Always include `$extensions.gsp-style` with the preset name.
+If the `.md` companion doesn't exist, render STYLE.md from `.yml` data only (thinner but functional).
 
-## Step 7: Write tokens.json
+Render into the template sections:
 
-If `{OUTPUT_PATH}/tokens.json` already exists, use `AskUserQuestion`: "tokens.json already exists — overwrite with style preset? Existing component-level tokens will be replaced." with options **Overwrite** and **Cancel**. If cancelled, skip writing tokens.json and proceed to the next step.
+- **Intensity** — from `.yml` `intensity:` block
+- **Philosophy** — extract from `.md` companion's Design Philosophy section. Condense to 2-4 sentences capturing the emotional DNA and cultural references.
+- **Patterns** — from `.yml` `patterns:` block, rendered as tables per component
+- **Constraints** — from `.yml` `constraints:` block, rendered as never/always bullet lists
+- **Effects** — from `.yml` `effects:` block, rendered as interaction vocabulary + state tables
+- **Bold Bets** — extract from `.md` companion's "Non-Genericness" or "Bold Factor" section. Pick 3-5 most distinctive techniques with implementation specifics.
+- **Implementation** — extract from `.md` companion's component stylings and CSS code:
+  - **Component Code Hints** — Tailwind/CSS patterns beyond the Patterns tables
+  - **Textures & Surfaces** — CSS for noise, halftone, grain (skip if style has none)
+  - **Typography Treatments** — text-stroke, tracking overrides (skip if standard)
+  - **Animation Recipes** — keyframes, transitions (skip if effects vocabulary is sufficient)
 
-Write the complete W3C Design Tokens JSON to `{OUTPUT_PATH}/tokens.json`.
+Write to `{OUTPUT_PATH}/STYLE.md`.
 
-## Step 8: Write foundation chunks
+## Step 8: Write INDEX.md
 
-Write 5 foundation chunks to `{OUTPUT_PATH}/foundations/`, each following `references/chunk-format.md`:
+Write `{OUTPUT_PATH}/INDEX.md` — header with phase/style/date, applied style name + description, file table ({preset-name}.yml, STYLE.md).
 
-- **color-system.md** — brand colors, semantic colors, dark mode mapping, WCAG contrast notes
-- **typography.md** — 9-level type scale, font family details + Google Fonts link, weight rationale
-- **spacing.md** — spacing scale with base unit and usage guidelines
-- **elevation.md** — shadow scale with use cases per level + style-specific notes
-- **border-radius.md** — radius token scale + style-specific shape notes
+Foundation chunks (color-system.md, typography.md, etc.) are NOT written in the quick path — the `.yml` has the token values, STYLE.md has the composition rules. Foundation chunks are only produced by the full branding diamond where the brand-engineer adds deeper analysis (WCAG ratios, font loading, semantic rationale).
 
-## Step 9: Write INDEX.md
-
-Write `{OUTPUT_PATH}/INDEX.md` — header with phase/style/date, applied style name + description, foundations table (chunk name, file link, ~lines), tokens table (tokens.json link).
-
-## Step 10: Update state
+## Step 9: Update state
 
 If a brand STATE.md exists at the brand path:
 - Set patterns phase status to `complete`
@@ -174,7 +172,7 @@ If a brand STATE.md exists at the brand path:
 If a project config.json exists:
 - Add `"style_preset": "{name}"` to preferences
 
-## Step 11: Completion output
+## Step 10: Completion output
 
-Show: header (`/gsp:style — {name} applied`), file tree (foundations/ + tokens.json + INDEX.md). Then `AskUserQuestion`: Start a project → `/gsp:project-brief`, Build components → `/gsp:brand-patterns`, Preview tokens, Try a different style → restart Step 2.
+Show: header (`/gsp-style — {name} applied`), file tree ({name}.yml + STYLE.md + INDEX.md). Then `AskUserQuestion`: Start a project → `/gsp-project-brief`, Build components → `/gsp-brand-guidelines`, Preview tokens, Try a different style → restart Step 2.
 </process>

package/gsp/skills/gsp-style/styles/INDEX.yml

@@ -1,6 +1,6 @@
 # Style Preset Index
 # 34 styles — sourced from designprompts.dev, GSP trend references, and original presets
-# Tags enable fuzzy matching: /gsp:style "something dark and techy" → cyberpunk, terminal, modern-dark
+# Tags enable fuzzy matching: /gsp-style "something dark and techy" → cyberpunk, terminal, modern-dark
 
 styles:
   # ── Minimal ─────────────────────────

package/gsp/skills/gsp-style/styles/academia.yml

@@ -62,5 +62,85 @@ dark_mode:
     surface: "#251E19"
     on-background: "#E8DFD4"
 
+intensity:
+  variance: 3     # classical symmetry with occasional 60/40 splits, mostly balanced
+  motion: 3       # dignified and deliberate — sepia reveals, brass shimmer, no playfulness
+  density: 4      # ornamental but restrained — flourishes, dividers, textures fill space with purpose
+
+patterns:
+  card:
+    border: "{shape.border-width} solid {shape.border-color}"
+    shadow: "none resting, {elevation.shadow-lg} on hover — warm depth"
+    radius: "{shape.border-radius-md}"
+    background: "one layer above page — aged oak surface"
+    decoration: "brass corner flourishes (24px L-brackets) at opposing corners, opacity 0.6→1.0 on hover"
+  button-primary:
+    background: "{brass.gradient}"
+    border: "none"
+    shadow: "inset highlights + depth shadow, brass glow on hover"
+    text: "uppercase, tracking-[0.15em], {typography.font-family-display}, engraved text-shadow"
+    radius: "{shape.border-radius-md}"
+  button-secondary:
+    background: "transparent"
+    border: "2px solid {color.accent}"
+    text: "uppercase, tracking-[0.15em], {color.accent}"
+    radius: "{shape.border-radius-md}"
+    hover: "fills crimson — border + bg shift to accentSecondary, text inverts"
+  input:
+    border: "{shape.border-width} solid {shape.border-color}"
+    radius: "{shape.border-radius-md}"
+    background: "aged oak surface"
+    focus: "border-{color.accent}, ring-2 ring-{color.accent}/30 ring-offset-2"
+    placeholder: "italic serif, faded ink color"
+  badge:
+    shape: "circular — crimson wax seal with radial gradient and inset shadows"
+    text: "centered icon (star), no text — visual accent"
+  nav:
+    style: "classical horizontal with brass accent links"
+    links: "serif, hover shifts to brass with tracking increase (0.2em→0.25em)"
+  layout:
+    archetype: "classical-symmetric"
+    max-width: "max-w-6xl"
+    section-spacing: "py-24 to py-32 — contemplative breathing room"
+    grid-gap: "gap-8 to gap-12"
+    surfaces: "paper texture (3% opacity noise, overlay blend) + vignette darkening edges"
+    decoration: "ornate dividers with centered glyphs, arch-topped images (40% 40% 0 0 / 20% 20% 0 0), Roman numeral volume labels"
+
+constraints:
+  never:
+    - "sans-serif fonts in headings — serif typography only (Cormorant, Crimson, Cinzel)"
+    - "bright saturated colors — everything aged and warm-toned"
+    - "pure black (#000000) or pure white (#FFFFFF) — warm mahogany and parchment"
+    - "bouncy or elastic animations — dignified motion only, like turning heavy pages"
+    - "sharp geometric decorations — favor architectural curves (arch-tops, flourishes)"
+    - "cold tones mixing with warm palette — exclusively warm throughout"
+    - "flat backgrounds without texture — paper grain and vignette are essential"
+    - "playful or whimsical elements — scholarly gravitas at all times"
+  always:
+    - "sepia filter (0.6) on all images by default, full color reveals on hover (700ms)"
+    - "brass (#C9A962) for ALL interactive elements — buttons, links, focus rings, hover states"
+    - "Roman numerals (Volume I, II, III) for section numbering"
+    - "arch-topped images (40% 40% 0 0 / 20% 20% 0 0 border-radius)"
+    - "paper texture overlay (3% opacity) + vignette radial gradient"
+    - "corner flourishes on major containers (brass L-brackets)"
+    - "ornate dividers with decorative glyphs between sections"
+    - "drop caps on introductory paragraphs (Cinzel, text-7xl, brass)"
+
+effects:
+  interaction-vocabulary: [brass-shimmer, sepia-reveal, dignified-lift, flourish-brighten]
+  hover:
+    card: "dignified-lift — shadow appears (0→lg), border shifts brass, flourish-brighten on corners"
+    button-primary: "brass-shimmer — brightness increases to 110%, glow shadow appears"
+    button-secondary: "crimson transform — border + bg shift to crimson, text inverts to parchment"
+    image: "sepia-reveal — sepia(0.6)→sepia(0), scale-105 over 700ms"
+    link: "brass-shimmer — color shifts to brass, tracking widens slightly"
+  active:
+    button: "deeper inset shadow — pressed-into-metal feel"
+  focus:
+    general: "ring-2 ring-{color.accent} ring-offset-2 ring-offset-background"
+  transition: "duration-300 to duration-700, ease-out"
+  ambient:
+    - "brass-breathe — subtle brightness oscillation on brass buttons (100%→110%, 2s cycle)"
+
 compatibility: [swiss-minimalist, monochrome]
 clashes: [cyberpunk, vaporwave, retro]