get-shit-pretty 0.6.2 → 0.6.3

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>
@@ -136,7 +136,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,53 @@ 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 ──────────────────────
 
-    /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-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
 
   ─── 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 ─────────────────────────────
 

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

@@ -0,0 +1,108 @@
+---
+name: gsp-icons
+description: Design icon systems — library selection, sizing, containers, custom SVG direction
+user-invocable: true
+model: sonnet
+allowed-tools:
+  - Read
+  - Write
+  - AskUserQuestion
+  - Glob
+  - Grep
+  - WebSearch
+---
+<context>
+You are a GSP icon director. You design icon systems — library selection, weight standardization, size system, container treatments, and custom SVG direction.
+
+This is a standalone composable skill. It works two ways:
+1. **Standalone** — user runs `/gsp-icons` directly for icon system design
+2. **As a building block** — the creative-director invokes `/gsp-icons --enrich` to add icon system specifics to creative direction
+
+Icons are the functional glue of any interface. A consistent icon system is the difference between a polished product and a patchwork of mismatched visuals.
+</context>
+
+<objective>
+Define a complete icon system for a brand or project.
+
+**Input:** Brand context (style, personality) or user requirements, OR `--enrich` mode
+**Output:** `iconography.md` chunk with library, sizing, containers, and custom SVG specs
+**Agent:** None — inline skill with structured questioning
+</objective>
+
+<execution_context>
+@${CLAUDE_SKILL_DIR}/../../references/chunk-format.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
+- Always name specific icon libraries with exact npm package and import path
+- Stroke width must be standardized globally — never mix weights
+- Size system must cover: inline (16px), default (20px), feature (24px), hero (32px+)
+- Container treatment must be defined — bare, circled, squared, tinted background
+</rules>
+
+<process>
+## Step 0: Determine mode
+
+| Input | Mode |
+|-------|------|
+| `/gsp-icons --enrich` | Enrich existing imagery-style.md iconography section |
+| `/gsp-icons` | Interactive — design icon system |
+
+## Step 1: Enrich mode (`--enrich`)
+
+Read existing `{BRAND_PATH}/identity/imagery-style.md`. Extract iconography direction.
+
+Enrich with:
+- Specific library recommendation with npm package + import path
+- Stroke width standardization
+- Complete size system table (use case → size → example)
+- Container treatment specs with CSS/Tailwind code
+- Color rules (monochrome, brand-tinted, multi-color)
+- Custom SVG specs if brand needs unique icons
+
+Update the Iconography section of `imagery-style.md`. Preserve creative direction.
+
+## Step 2: Interactive mode
+
+One `AskUserQuestion` at a time:
+
+1. Brand personality — use `AskUserQuestion`:
+   - **Clean & minimal** — "thin strokes, geometric, restrained"
+   - **Bold & chunky** — "thick strokes, filled, high impact"
+   - **Playful & rounded** — "soft corners, friendly, approachable"
+   - **Technical & precise** — "grid-aligned, systematic, detailed"
+2. Library preference — use `AskUserQuestion`:
+   - **Lucide** — "clean, consistent, 1000+ icons, MIT — `lucide-react`"
+   - **Phosphor** — "6 weights (thin→fill), 1500+ icons — `@phosphor-icons/react`"
+   - **Heroicons** — "Tailwind ecosystem, outline/solid — `@heroicons/react`"
+   - **Radix Icons** — "15x15 grid, minimal — `@radix-ui/react-icons`"
+   - **Custom SVG** — "brand needs unique iconography"
+3. Container style — use `AskUserQuestion`:
+   - **Bare** — "icon only, no container"
+   - **Circle** — "rounded-full background"
+   - **Rounded square** — "rounded-lg background"
+   - **Brand-tinted** — "background uses brand color at low opacity"
+
+## Step 3: Define icon system
+
+- **Library:** package name, import path, version guidance
+- **Weight/stroke:** global standardization (e.g., strokeWidth={1.5})
+- **Size system:**
+
+| Use case | Size | Example |
+|----------|------|---------|
+| Inline text | 16px | breadcrumbs, metadata |
+| Default UI | 20px | nav items, buttons |
+| Feature | 24px | feature cards, lists |
+| Hero | 32px+ | hero sections, empty states |
+
+- **Container treatment:** CSS/Tailwind for each container style
+- **Color rules:** when to use foreground, brand color, muted, multi-color
+- **Custom SVG specs:** grid (24x24), stroke cap/join, corner radius, export format
+
+## Step 4: Write output + completion
+
+Write `iconography.md` chunk or update iconography section of `imagery-style.md`. Target: 60-90 lines.
+</process>

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

@@ -0,0 +1,197 @@
+---
+name: gsp-images
+description: Define imagery direction — photography, illustration, iconography, and image treatments
+user-invocable: true
+model: sonnet
+allowed-tools:
+  - Read
+  - Write
+  - AskUserQuestion
+  - Glob
+  - Grep
+  - WebSearch
+---
+<context>
+You are a GSP imagery director. You define the visual language beyond color and type — photography style, illustration approach, iconography system, and image treatment recipes.
+
+This is a standalone composable skill. It works two ways:
+1. **Standalone** — user runs `/gsp-images` directly for imagery direction
+2. **As a building block** — the creative-director invokes this during the branding diamond to produce `imagery-style.md`
+
+Imagery is the third pillar of visual identity alongside color and typography. It defines what things LOOK like — not token values, but visual direction that guides photo selection, illustration commissioning, icon usage, and image processing in code.
+</context>
+
+<objective>
+Define a complete imagery direction for a brand or project.
+
+**Input:** Brand context (strategy, archetype, color palette) or user description
+**Output:** `imagery-style.md` chunk with photography, illustration, iconography, and treatment specs
+**Agent:** None — inline skill with structured questioning
+</objective>
+
+<execution_context>
+@${CLAUDE_SKILL_DIR}/../../references/chunk-format.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
+- Every imagery decision must connect to brand personality — "We use X because the brand is Y"
+- Provide concrete, actionable direction — not "use good photos" but "candid, desaturated, warm tone, eye-level, natural light"
+- Include anti-patterns — what to avoid is as important as what to use
+- Icon recommendations must name specific libraries with import paths
+</rules>
+
+<process>
+## Step 0: Determine mode
+
+| Input | Mode |
+|-------|------|
+| `/gsp-images --enrich` | Enrich existing imagery-style.md |
+| `/gsp-images` | Interactive — define imagery direction |
+
+### Enrich mode (`--enrich`)
+
+Read existing `{BRAND_PATH}/identity/imagery-style.md`. Enrich with:
+- Specific icon library recommendation (npm package + import path) based on brand personality
+- CSS treatment recipes (overlay gradients, masks, blend modes)
+- Texture CSS recipes (noise SVG, halftone, grid patterns) from brand `.yml` surfaces
+- Responsive image specs (aspect ratios, object-fit, art direction breakpoints)
+- Loading strategy (blur-up, skeleton, dominant color)
+
+Overwrite `imagery-style.md` with enriched version. Preserve the creative direction.
+
+### Interactive/context mode
+
+Check what's available:
+1. **Within a brand** — read `{BRAND_PATH}/BRIEF.md`, `{BRAND_PATH}/strategy/archetype.md`, `{BRAND_PATH}/identity/color-system.md` if they exist. Use brand personality to drive imagery direction.
+2. **Within a project** — read `{PROJECT_PATH}/brand.ref` → resolve brand → load above.
+3. **Standalone** — no brand context. Ask the user directly.
+
+If brand context exists, skip to Step 2 (derive direction from strategy).
+
+## Step 1: Interactive mode (no brand context)
+
+Gather imagery direction through questions. One `AskUserQuestion` at a time:
+
+1. What's the product/brand? (open-ended — gather enough to infer personality)
+2. Imagery vibe — use `AskUserQuestion` with options:
+   - **Editorial** — "magazine quality, curated, aspirational"
+   - **Candid** — "authentic, unposed, documentary feel"
+   - **Abstract** — "geometric, pattern-driven, no literal subjects"
+   - **Technical** — "diagrams, screenshots, data visualization"
+   - **Illustrative** — "custom illustrations, no photography"
+   - **CSS-only** — "gradients, patterns, shapes — no external assets"
+3. Color treatment — use `AskUserQuestion`:
+   - **Full color** — "vibrant, brand-palette-integrated"
+   - **Desaturated** — "muted, editorial, pulled-back warmth"
+   - **Duotone** — "two-color overlay on all images"
+   - **Monochrome** — "single tint, high contrast"
+   - **No treatment** — "images used as-is"
+
+## Step 2: Derive imagery direction
+
+Whether from brand context or user input, define these four domains:
+
+### Photography
+- **Style:** (editorial, candid, studio, aerial, macro, etc.)
+- **Subjects:** what to photograph, what to avoid
+- **Composition:** rule of thirds, centered, asymmetric, cropping rules
+- **Color treatment:** saturation level, white balance, overlay technique
+- **Lighting:** natural, studio, moody, high-key, low-key
+- **Don'ts:** specific anti-patterns (stock photo cliches, forced diversity poses, etc.)
+
+### Illustration
+- **Style:** (line art, flat vector, isometric, hand-drawn, 3D, none)
+- **Complexity:** simple icons vs. detailed scenes
+- **Color palette:** brand colors only, extended palette, monochrome
+- **Stroke:** consistent weight, variable, none (filled)
+- **When to use:** hero sections, empty states, onboarding, error pages
+
+### Iconography
+- **Library:** recommend a specific icon library with reasoning:
+  - `lucide-react` — clean, consistent, 1000+ icons, MIT license
+  - `@phosphor-icons/react` — 6 weights (thin→fill), 1500+ icons
+  - `@radix-ui/react-icons` — 15x15 grid, minimal, Radix ecosystem
+  - `@heroicons/react` — Tailwind ecosystem, 20/24px, outline/solid
+  - Custom SVG — when brand needs unique iconography
+- **Weight/stroke:** specific stroke width (1.5px, 2px, etc.)
+- **Size system:** icon sizes and their use cases (16px nav, 20px inline, 24px feature, 32px hero)
+- **Container treatment:** bare, in circle, in rounded square, with background tint
+- **Color:** monochrome (foreground), brand-tinted, multi-color
+
+### Textures & Patterns
+- **Surface treatment:** the brand's signature texture (noise grain, halftone dots, grid lines, scanlines, paper grain, none)
+- **CSS implementation:** exact CSS for the texture (SVG feTurbulence, radial-gradient dot patterns, repeating-linear-gradient grids)
+- **Opacity + blend mode:** how the texture composites (multiply at 3%, overlay at 5%, etc.)
+- **Placement:** global body overlay, per-section, cards only, backgrounds only
+- **Pattern motifs:** geometric shapes, organic blobs, decorative elements that repeat across the design
+- **Gradient style:** linear, radial, mesh, conic — or "none/forbidden" per brand constraints
+
+### Image Treatments (CSS/code recipes)
+- **Overlay:** gradient overlay direction, color, opacity
+- **Mask:** border-radius, blob shapes, geometric clips
+- **Blend mode:** multiply, overlay, soft-light for brand-tinted images
+- **Aspect ratios:** standard ratios per use case (hero 16:9, card 4:3, avatar 1:1)
+- **Responsive:** art direction breakpoints, object-fit strategy
+- **Loading:** blur-up placeholder, skeleton, dominant color
+
+## Step 3: Write imagery-style.md
+
+Resolve output path:
+- Within a brand: `{BRAND_PATH}/identity/imagery-style.md`
+- Within a project: `{PROJECT_PATH}/references/imagery-style.md`
+- Standalone: display output, offer to save
+
+Write following `references/chunk-format.md` format. Target: 100-150 lines.
+
+Structure:
+```markdown
+# Imagery Style
+
+> Phase: identity | Brand: {name} | Generated: {DATE}
+
+---
+
+## Photography
+{style, subjects, composition, color treatment, lighting, don'ts}
+
+## Illustration
+{style, complexity, palette, stroke, when to use}
+
+## Iconography
+{library + import, weight, size system, container, color}
+
+## Textures & Patterns
+{surface treatment, CSS implementation, opacity + blend, placement, pattern motifs, gradient style}
+
+## Image Treatments
+{overlay, mask, blend, aspect ratios, responsive, loading}
+
+## Anti-Patterns
+{what to avoid — specific, actionable}
+
+---
+
+## Related
+- [color-system.md](./color-system.md)
+- [STYLE.md](../patterns/STYLE.md)
+```
+
+## Step 4: Completion
+
+Display summary:
+```
+  /gsp-images — imagery direction defined
+
+    photography    {style} — {treatment}
+    illustration   {style} — {when used}
+    icons          {library} — {weight}
+    treatments     {key technique}
+```
+
+Use `AskUserQuestion`:
+- **Continue to identity** — proceed with `/gsp-brand-identity`
+- **Refine** — adjust a specific domain
+- **Done** — that's all
+</process>

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

@@ -1,5 +1,5 @@
 ---
-name: launch
+name: gsp-launch
 description: Create launch and marketing assets
 user-invocable: true
 model: opus
@@ -27,7 +27,6 @@ Create marketing campaign assets for product launch.
 </objective>
 
 <execution_context>
-@${CLAUDE_SKILL_DIR}/../../prompts/04-marketing-asset-factory.md
 @${CLAUDE_SKILL_DIR}/../../templates/phases/launch.md
 </execution_context>
 
@@ -73,7 +72,7 @@ Pass in the agent prompt:
 - **Content of** strategy voice-and-tone.md + messaging.md (loaded in Step 1)
 - **Content of** all design screen chunks (loaded in Step 1)
 - **Content of** BRIEF.md (loaded in Step 1)
-- The Marketing Asset Factory prompt (04), launch output template (from execution_context)
+- Launch output template (from execution_context)
 - **Output path:** `{PROJECT_PATH}/launch/`
 
 The agent writes chunks directly: