get-shit-pretty 0.5.2 → 0.6.1

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

@@ -72,7 +72,7 @@ If all 4 phases complete, check:
 
 **Check B4: Legacy Monolith Detection**
 For each brand phase directory (discover, strategy, identity, patterns):
-- If monolith exists but no INDEX.md → WARN: "Legacy format in {phase}/ — re-run /gsp:brand-{phase} for 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)
 
@@ -239,6 +239,22 @@ Glob for all SKILL.md files in the skills directory (`{runtime-dir}/skills/*/SKI
 - 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."
 
+**Check I2: Skill directories are complete (not just SKILL.md)**
+For each gsp-* skill directory, check if `SKILL.md` references sibling files via `${CLAUDE_SKILL_DIR}/` paths (e.g. `styles/INDEX.yml`). If it does, verify those files/dirs exist in the installed skill directory.
+- All referenced siblings present → PASS
+- 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}/../../`.
+- All present → PASS
+- Missing → FAIL: "Bundle directory {dir} missing. Re-run the installer: `npx get-shit-pretty`"
+
+**Check I4: VERSION file present**
+Check `{runtime-dir}/VERSION` exists and contains a valid semver string.
+- Present and valid → PASS (show version)
+- Missing → WARN: "VERSION file missing. Re-run the installer."
+- Mismatched with source → INFO: "Installed version {installed} differs from source {source}."
+
 ### Cross-Instance Checks
 
 **Check X1: Multiple projects, same brand**
@@ -287,6 +303,9 @@ Overall Health: {SCORE}/100 {emoji}
 
 ─── Installation Health ───────────────
   ✅ I1. Skills invocable ........ PASS
+  ✅ I2. Skill completeness ...... PASS
+  ✅ I3. Bundle directories ...... PASS
+  ✅ I4. VERSION file ............ PASS
 
 ─── Cross-Instance ────────────────────
   ✅ X1. Brand Consistency ...... PASS

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

@@ -42,6 +42,7 @@ Skill names are left-padded with 4 spaces. Descriptions start at column 27 (4 in
     /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)
 
   ─── Project ──────────────────────────

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

@@ -31,12 +31,9 @@ Create marketing campaign assets for product launch.
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Set `BRAND_PATH` = `.design/branding/{brand}`
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 ## Step 1: Load context
 
@@ -49,9 +46,8 @@ Read `{PROJECT_PATH}/config.json` to get `design_scope`.
 ### Identity (selective, chunk-first)
 
 Read `{BRAND_PATH}/identity/INDEX.md`. If it exists, load all identity chunks.
-Fallback: read `{BRAND_PATH}/identity/IDENTITY.md`. Log: "⚠️ Legacy identity format detected."
 
-If neither exists, tell the user to complete the brand identity first.
+If it doesn't exist, tell the user to complete the brand identity first.
 
 ### Voice and Messaging (from strategy)
 
@@ -60,7 +56,6 @@ Read `{BRAND_PATH}/strategy/voice-and-tone.md` and `{BRAND_PATH}/strategy/messag
 ### Design (chunk-first)
 
 Read `{PROJECT_PATH}/design/INDEX.md`. If it exists, load all screen chunks.
-Fallback: read `{PROJECT_PATH}/screens/INDEX.md` (legacy path).
 
 ### Other
 

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

@@ -31,6 +31,7 @@ Generate production-ready OKLCH color palettes from hex colors.
 
 <rules>
 - Always use `AskUserQuestion` for user interaction — never prompt via plain text
+- One decision per question — never batch multiple questions in a single message
 - Palettes are deterministic — same hex input always produces the same OKLCH scales
 - Foundation chunks follow `references/chunk-format.md` format exactly
 - Every palette gets the full 11-stop scale: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, 950
@@ -138,6 +139,8 @@ If a brand context exists (`.design/branding/{brand}/`):
 
 ## Step 5: Write palettes.json
 
+If `{OUTPUT_PATH}/palettes.json` already exists, use `AskUserQuestion`: "palettes.json already exists — overwrite with new palette?" with options **Overwrite** and **Cancel**. If cancelled, skip writing palettes.json and proceed to the next step.
+
 Write `{OUTPUT_PATH}/palettes.json` with the full OKLCH scales:
 
 ```json

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

@@ -34,15 +34,9 @@ Scope the project and plan adaptations from the brand system.
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Extract `brand` name and `path` from brand.ref
-- Set `BRAND_PATH` = `.design/branding/{brand}`
-
-If brand.ref doesn't exist, tell the user to run `/gsp:start` to set up the project with a brand reference.
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`. If brand.ref doesn't exist, tell the user to run `/gsp:start`.
 
 ## Step 1: Load context
 
@@ -50,9 +44,7 @@ If brand.ref doesn't exist, tell the user to run `/gsp:start` to set up the proj
 
 Read `{BRAND_PATH}/patterns/INDEX.md`. If it exists, load all foundation chunks + selective component chunks.
 
-Fallback: read `{BRAND_PATH}/patterns/SYSTEM.md` (legacy monolith). Log: "⚠️ Legacy format detected."
-
-If neither exists, tell the user to run `/gsp:brand-patterns` first to create the brand's design patterns.
+If it doesn't exist, tell the user to run `/gsp:brand-patterns` first to create the brand's design patterns.
 
 Also read `{BRAND_PATH}/patterns/tokens.json`.
 

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

@@ -57,12 +57,9 @@ Implement designs as production-ready code in the codebase via phased pipeline w
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Set `BRAND_PATH` = `.design/branding/{brand}`
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 ## Step 0.5: Validate prerequisites
 

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

@@ -36,12 +36,9 @@ Critique design quality and audit accessibility compliance.
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Set `BRAND_PATH` = `.design/branding/{brand}`
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 ## Step 1: Load context
 
@@ -52,13 +49,10 @@ Read `{PROJECT_PATH}/config.json` to get `implementation_target`, `design_scope`
 **BRIEF:** `{PROJECT_PATH}/BRIEF.md`
 
 **Identity:** Read `{BRAND_PATH}/identity/INDEX.md` → load all chunks.
-Fallback: `{BRAND_PATH}/identity/IDENTITY.md`.
 
 **Patterns:** Read `{BRAND_PATH}/patterns/INDEX.md` → load all chunks.
-Fallback: `{BRAND_PATH}/patterns/SYSTEM.md`.
 
 **Design:** Read `{PROJECT_PATH}/design/INDEX.md` → load all chunks.
-Fallback: `{PROJECT_PATH}/design/SCREENS.md` or `{PROJECT_PATH}/screens/INDEX.md` (legacy).
 
 **Brief:** Read `{PROJECT_PATH}/brief/INDEX.md` → load all chunks (if exists).
 
@@ -150,5 +144,7 @@ If verdict is **Fail**:
 ## Step 6: Phase transition output
 
 Render phase transition (see `references/phase-transitions.md`). This phase has pass/fail variants — the reference covers both.
+
+If critique identified brand-level issues (palette contrast, typography weight, spacing scale), note: "Some issues are brand-level — run `/gsp:brand-refine` to adjust tokens without re-running identity."
 </process>
 </output>

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

@@ -36,12 +36,9 @@ Design core UI/UX screens and interaction flows.
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Set `BRAND_PATH` = `.design/branding/{brand}`
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 ## Step 0.5: Validate prerequisites
 
@@ -71,14 +68,11 @@ 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.
 
-Fallback: read `{BRAND_PATH}/patterns/SYSTEM.md` (legacy monolith). Log: "⚠️ Legacy format detected — consider re-running /gsp:brand-patterns for chunk output."
-
-If neither exists, tell the user to run `/gsp:brand-patterns` first.
+If it doesn't exist, tell the user to run `/gsp:brand-patterns` first.
 
 ### Brand context (selective)
 
 Read `{BRAND_PATH}/identity/INDEX.md`. If it exists, load `color-system.md`, `typography.md`, and `imagery-style.md`.
-Fallback: read `{BRAND_PATH}/identity/IDENTITY.md`.
 
 ### Brand style prompt (visual DNA)
 

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

@@ -36,12 +36,9 @@ Deep research into UX patterns, competitor experiences, and technical approaches
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Set `BRAND_PATH` = `.design/branding/{brand}`
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 ## Step 1: Load context
 

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

@@ -32,12 +32,9 @@ QA validate the codebase implementation against design intent.
 <process>
 ## Step 0: Resolve project and brand
 
-Scan `.design/projects/` for project directories. If only one project exists, use it. If multiple, ask the user which project to work on.
+Resolve project from `.design/projects/` (one → use it, multiple → ask). Set `PROJECT_PATH`.
 
-Set `PROJECT_PATH` = `.design/projects/{project}`
-
-Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
-- Set `BRAND_PATH` = `.design/branding/{brand}`
+Read `{PROJECT_PATH}/brand.ref` → set `BRAND_PATH`.
 
 ## Step 1: Load context
 
@@ -54,7 +51,6 @@ Read `{PROJECT_PATH}/config.json` to get `implementation_target`, `design_scope`
 **Git diff:** Run `git diff` (and `git diff --cached`) to see what actually changed in the codebase. Cross-reference against BUILD-LOG.md.
 
 **Design:** Read `{PROJECT_PATH}/design/INDEX.md` → load all screen chunks.
-Fallback: `{PROJECT_PATH}/screens/INDEX.md` (legacy).
 
 **Brand patterns:** Read `{BRAND_PATH}/patterns/INDEX.md` → load foundation + component chunks.
 Also read `{BRAND_PATH}/patterns/tokens.json`.
@@ -175,4 +171,6 @@ If verdict is **Fail**:
 ## Step 6: Phase transition output
 
 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."
 </process>