get-shit-pretty 0.6.0 → 0.6.2

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

@@ -2,6 +2,7 @@
 name: start
 description: Start here — picks up where you left off
 user-invocable: true
+model: sonnet
 allowed-tools:
   - Read
   - Write
@@ -25,20 +26,11 @@ Multiple brands and projects can coexist. Projects reference a brand.
 </context>
 
 <objective>
-Through 2-3 rounds of natural conversation, gather a complete brief and create the right project structure (brand, project, or both). Route the user to their first phase skill.
+Through a sequential one-question-at-a-time conversation, gather a complete brief and create the right project structure (brand, project, or both). Route the user to their first phase skill.
 </objective>
 
 <execution_context>
 @${CLAUDE_SKILL_DIR}/../../references/questioning.md
-@${CLAUDE_SKILL_DIR}/../../templates/branding/brief.md
-@${CLAUDE_SKILL_DIR}/../../templates/branding/state.md
-@${CLAUDE_SKILL_DIR}/../../templates/branding/config.json
-@${CLAUDE_SKILL_DIR}/../../templates/branding/roadmap.md
-@${CLAUDE_SKILL_DIR}/../../templates/projects/brief.md
-@${CLAUDE_SKILL_DIR}/../../templates/projects/state.md
-@${CLAUDE_SKILL_DIR}/../../templates/projects/config.json
-@${CLAUDE_SKILL_DIR}/../../templates/projects/roadmap.md
-@${CLAUDE_SKILL_DIR}/../../templates/exports-index.md
 </execution_context>
 
 <rules>
@@ -49,11 +41,12 @@ Through 2-3 rounds of natural conversation, gather a complete brief and create t
 <questioning_principles>
 Follow these principles throughout all conversations:
 
-1. **Inference over interrogation** — state assumptions, let them correct. "SaaS dashboard for enterprise" → you already know: professional, data-dense, web-first.
-2. **Progressive disclosure** — don't dump all questions at once. Flow in natural rounds.
-3. **Concrete options over open-ended** — "More like Stripe's clean approach or Duolingo's playful style?" beats "What style do you want?"
-4. **Know when you have enough** — fill gaps with smart defaults. Don't over-ask.
-5. **One message per round** — ask a cohesive set of related questions, not one at a time.
+1. **One decision per question** — every question must be its own `AskUserQuestion` call with exactly one decision. Never group multiple questions into a single message. Ask, wait for the answer, then ask the next thing.
+2. **Never re-ask** — if the user already answered something (in this phase or a prior one), don't ask again. If you need to validate, confirm: "I see X from earlier — still accurate?" The user should never feel like they're repeating themselves.
+3. **Inference over interrogation** — state assumptions, let them correct. "SaaS dashboard for enterprise" → you already know: professional, data-dense, web-first.
+4. **Adapt and skip** — use each answer to inform the next question. If an answer reveals enough to skip a later question, skip it. Don't follow a rigid checklist.
+5. **Concrete options over open-ended** — "More like Stripe's clean approach or Duolingo's playful style?" beats "What style do you want?"
+6. **Know when you have enough** — fill gaps with smart defaults. Don't over-ask.
 </questioning_principles>
 
 <process>
@@ -71,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 Step 3 Round 2 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
 
@@ -121,8 +114,7 @@ Weave in what you found naturally: framework, styling, component count.
 
 From the greeting exchange, determine which flow to run:
 
-- **Brand identity (new)** → Brand flow (Step 3) with `brand_mode: "new"`
-- **Brand identity (evolve)** → Brand flow (Step 3) with `brand_mode: "evolve"`. Detect evolve signals: user mentions existing brand, assets, guidelines, rebrand, refresh, modernize, evolve, update, redesign.
+- **Brand identity** → Brand flow (Step 3)
 - **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)
@@ -130,55 +122,75 @@ From the greeting exchange, determine which flow to run:
 
 ## Step 3: Brand flow
 
+Each question is its own `AskUserQuestion` call. Ask one, wait, adapt, ask the next. Skip anything you can already infer.
+
+**Step 3a — Brand name and path selection:**
+
 1. Ask for brand name (kebab-case, e.g., "acme-corp")
-2. Create directory structure:
+2. "Do you already have brand materials to work with?" — use `AskUserQuestion`:
+   - **Yes, I have an existing brand** — "I have a logo, colors, guidelines, or other assets"
+   - **No, starting fresh** — "Building a brand from scratch"
+
+If **yes** → set `brand_mode: "evolve"`. Continue with evolve sequence (Step 3b-evolve).
+If **no** → set `brand_mode: "new"`. Continue with new sequence (Step 3b-new).
+
+3. Create directory structure:
 ```bash
 mkdir -p .design/branding/{name}/{audit,discover,strategy,identity,patterns}
 ```
 
-3. Gather brand brief in 3 rounds. The brief is the single source of truth for business and persona definition — invest here.
-
-**Round 1 — Business & People:**
-- Company name, industry, stage
-- Problem / audience / differentiation
-- Business model, main competitors (2-3)
-- Primary persona — infer a concrete profile (name, role, frustration, aspiration) from context and present for correction. Personas should feel like real people — dig into the emotional layer.
-- Secondary persona (if relevant)
-- Mission and vision
-
-**Round 2 — Brand Essence & Landscape:**
-
-Before presenting personality options, **internally synthesize** promise (what should someone feel?) and point of view (what does this brand disagree with?) from Round 1. Don't ask these directly — use them to ground personality options.
-
-- Brand personality — use `AskUserQuestion` with 2-3 concrete personality directions. **Each option must explain WHY it fits this brand's audience and problem** — not just a style label:
-  - Each option: **Label** (3 adjectives) / **Description** (why this personality fits their specific audience and competitive position — reference the persona by name, the problem, or the gap) / **Preview** (example sentence in that voice, using their product context)
-  - **Surprise me** — craft an unexpected direction inspired by the user's industry and personas
-- What the brand should NEVER feel like
-- Competitive landscape — use `WebSearch` to enrich the competitors named in Round 1. Present the map for confirmation.
-- Brands admired / styles to avoid
-
-**Round 3 — Constraints & confirmation:**
-- Existing brand assets? (logo, colors, guidelines)
-- Timeline and budget constraints
-- Non-negotiables
-- **Check background scan:** If the codebase scanner has returned results, weave tech findings naturally.
-- State your understanding back: "Here's what I'm hearing: [summary]." Use `AskUserQuestion`:
-  - **Looks good** — "That's accurate, let's go"
-  - **Adjust something** — "I want to change or add something"
-
-**Evolve mode additions (when `brand_mode` is `evolve`):**
-Add to Round 3:
-- Current brand age, existing guidelines
-- Brand equity (what's working) and pain points (what's not)
-- Evolution scope — preserve / evolve / replace
-
-Skip or compress rounds if the user gives enough upfront. Don't over-ask.
-
-4. Write artifacts:
-- `.design/branding/{name}/BRIEF.md` from brand brief template
-- `.design/branding/{name}/STATE.md` from brand state template
-- `.design/branding/{name}/config.json` from brand config template
-- `.design/branding/{name}/ROADMAP.md` from brand roadmap template
+**Step 3b-evolve — Gather existing brand context:**
+
+Ask these before business questions — the existing brand shapes everything:
+
+3. Share your current brand materials — logo, colors, guidelines, URLs, anything you have. (open-ended — gather thoroughly here. Brand-audit will NOT re-ask for assets.)
+4. How old is the current brand? (open-ended)
+5. What's working well with the current brand? (open-ended)
+6. What's not working — what are the pain points? (open-ended)
+7. Evolution scope — use `AskUserQuestion`: **Preserve most, tweak details** / **Evolve significantly, keep core** / **Replace — start fresh**
+
+Then continue to Step 3c (business & people), skipping anything the brand materials already reveal.
+
+**Step 3b-new — Skip to business questions:**
+
+Continue directly to Step 3c.
+
+**Step 3c — Business & People:**
+
+8. What's the company name, and what industry/stage? (open-ended `AskUserQuestion`)
+9. What problem does it solve, and for whom? (open-ended — use the answer to start inferring persona)
+10. What's the business model? (use `AskUserQuestion` with options if you can infer likely models from industry, otherwise open-ended)
+11. Who are the main competitors? (2-3 names — open-ended)
+12. Present an inferred primary persona — a concrete profile (name, role, frustration, aspiration) based on answers so far. Personas should feel like real people — dig into the emotional layer. Use `AskUserQuestion`: **Looks right** / **Adjust** / **Add a secondary persona**
+
+**Step 3d — Brand Essence:**
+
+Before presenting personality options, **internally synthesize** promise (what should someone feel?) and point of view (what does this brand disagree with?) from prior answers. Don't ask these directly — use them to ground personality options.
+
+13. Brand personality direction — use `AskUserQuestion` with 2-3 concrete personality directions. **Each option must explain WHY it fits this brand's audience and problem** — not just a style label:
+    - Each option: **Label** (3 adjectives) / **Description** (why this personality fits their specific audience and competitive position — reference the persona by name, the problem, or the gap) / **Preview** (example sentence in that voice, using their product context)
+    - **Surprise me** — craft an unexpected direction inspired by the user's industry and personas
+    - Note: this is a high-level direction only. Brand strategy phase will deepen this into archetype + voice — don't over-refine here.
+14. What should the brand NEVER feel like? (use `AskUserQuestion` with 2-3 anti-directions inferred from their personality pick, plus open-ended option)
+15. Brands admired or styles to avoid? (open-ended `AskUserQuestion`)
+
+Note: competitive landscape deep-dive happens in the research phase — don't re-confirm it here. The competitor names from Q11 are enough.
+
+**Step 3e — Constraints & confirmation:**
+
+16. Any non-negotiables or constraints? (timeline, budget, must-haves) — open-ended `AskUserQuestion`
+17. **Check background scan:** If the codebase scanner has returned results, weave tech findings naturally into your summary.
+18. State your understanding back: "Here's what I'm hearing: [summary]." Use `AskUserQuestion`:
+    - **Looks good** — "That's accurate, let's go"
+    - **Adjust something** — "I want to change or add something"
+
+Skip any question you can already answer from prior context. Don't over-ask.
+
+4. Read templates from `${CLAUDE_SKILL_DIR}/../../templates/branding/` and write artifacts:
+- `.design/branding/{name}/BRIEF.md` from `brief.md` template
+- `.design/branding/{name}/STATE.md` from `state.md` template
+- `.design/branding/{name}/config.json` from `config.json` template
+- `.design/branding/{name}/ROADMAP.md` from `roadmap.md` template
 
 5. Set `brand_mode` in config.json based on Step 2 routing decision.
 
@@ -186,8 +198,8 @@ Skip or compress rounds if the user gives enough upfront. Don't over-ask.
 
 - **Brand-only, new →** continue to `/gsp:brand-research`
 - **Brand-only, evolve →** continue to `/gsp:brand-audit`
-- **E2E, new →** auto-continue to Step 4
-- **E2E, evolve →** continue to `/gsp:brand-audit` (then Step 4 after 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
 
@@ -212,40 +224,38 @@ Use the background `git branch --show-current` result. If detected, confirm bran
 
 6. Consume `.design/system/STACK.md` — note classification for config.json, auto-infer `implementation_target` from STACK.md + COMPONENTS.md.
 
-7. Gather project brief in 2 rounds:
-
-**Round 1 — What we're building:**
-- What are we building? (app, website, dashboard, etc.)
-- Present background scan findings: "I found a {classification} {framework} project with {details}. Want to build on that?"
-- Platforms (web, iOS, Android)?
-- Tech stack preferences? (confirm inferred or ask)
-- Implementation target — use `AskUserQuestion` with options based on codebase analysis (e.g., shadcn, rn-reusables, custom, css-only)
-- Design scope — use `AskUserQuestion`:
-  - **Full** — "Complete design: screens, components, tokens"
-  - **Partial** — "Specific screens or flows only"
-  - **Tokens only** — "Just design tokens, no screens"
-- Key screens/flows needed?
-
-Use inference from the codebase scan — don't re-ask what you can already see.
-
-**Round 2 — Success & gaps:**
-- Success criteria
-- Timeline, constraints
-- Any remaining gaps
-- State your understanding back: "Here's what I'm hearing: [summary]." Use `AskUserQuestion`:
-  - **Looks good** — "That's accurate, let's go"
-  - **Adjust something** — "I want to change or add something"
-  - **Explain this** — "Walk me through what you captured and why" → explain each section of the brief and how it'll be used in the next phases
-  - **Surprise me** — "Suggest something I haven't thought of" → propose an unexpected screen, flow, or feature angle that would elevate the project based on what you know about the brand, audience, and codebase. Present it as a suggestion the user can adopt, tweak, or skip.
-
-Skip or compress rounds if the user gives enough upfront. Don't over-ask.
-
-8. Write artifacts:
-- `.design/projects/{name}/BRIEF.md` from project brief template
-- `.design/projects/{name}/STATE.md` from project state template — populate `## Git` table with detected/confirmed branch (or "—")
-- `.design/projects/{name}/config.json` from project config template — populate `git.branch` with detected/confirmed branch (or empty string)
-- `.design/projects/{name}/ROADMAP.md` from project roadmap template
-- `.design/projects/{name}/exports/INDEX.md` from exports-index template
+7. Gather project brief as a sequential conversation. Each question is its own `AskUserQuestion` call. Ask one, wait, adapt, ask the next. Skip anything you can already infer from the codebase scan.
+
+**Sequence — What we're building:**
+
+1. What are we building? (app, website, dashboard, etc.) — open-ended `AskUserQuestion`
+2. Present background scan findings: "I found a {classification} {framework} project with {details}." Use `AskUserQuestion`: **Build on this** / **Different stack** / **Tell me more**
+3. Platforms? — use `AskUserQuestion`: **Web** / **iOS** / **Android** / **Cross-platform** (skip if obvious from codebase)
+4. Implementation target — use `AskUserQuestion` with options based on codebase analysis (e.g., shadcn, rn-reusables, custom, css-only)
+5. Design scope — use `AskUserQuestion`:
+   - **Full** — "Complete design: screens, components, tokens"
+   - **Partial** — "Specific screens or flows only"
+   - **Tokens only** — "Just design tokens, no screens"
+6. Key screens/flows needed? — open-ended `AskUserQuestion`
+
+**Sequence — Success & confirmation:**
+
+7. What does success look like? — open-ended `AskUserQuestion`
+8. Any constraints? (timeline, budget, must-haves) — open-ended `AskUserQuestion`
+9. State your understanding back: "Here's what I'm hearing: [summary]." Use `AskUserQuestion`:
+   - **Looks good** — "That's accurate, let's go"
+   - **Adjust something** — "I want to change or add something"
+   - **Explain this** — "Walk me through what you captured and why" → explain each section of the brief and how it'll be used in the next phases
+   - **Surprise me** — "Suggest something I haven't thought of" → propose an unexpected screen, flow, or feature angle that would elevate the project based on what you know about the brand, audience, and codebase. Present it as a suggestion the user can adopt, tweak, or skip.
+
+Skip any question you can already answer from the codebase scan. Don't over-ask.
+
+8. Read templates from `${CLAUDE_SKILL_DIR}/../../templates/projects/` and write artifacts:
+- `.design/projects/{name}/BRIEF.md` from `brief.md` template
+- `.design/projects/{name}/STATE.md` from `state.md` template — populate `## Git` table with detected/confirmed branch (or "—")
+- `.design/projects/{name}/config.json` from `config.json` template — populate `git.branch` with detected/confirmed branch (or empty string)
+- `.design/projects/{name}/ROADMAP.md` from `roadmap.md` template
+- `.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
@@ -309,7 +319,7 @@ Continue directly to Step 4 (project flow) with these modifications:
 - Go straight to asking for project name
 - Set `style_preset: "{preset}"` in the project's `config.json`
 - Set `identity_hash: "style-only"` in `brand.ref`
-- Proceed with the normal 2-round project brief gathering
+- Proceed with the normal sequential project brief gathering
 
 ### Upgrade path
 

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

@@ -2,6 +2,7 @@
 name: style
 description: Apply a design style — get tokens and foundations without the branding diamond
 user-invocable: true
+model: sonnet
 allowed-tools:
   - Read
   - Write
@@ -35,6 +36,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`
 - When mixing styles, later style values override earlier ones (last-wins precedence)
 - Never mix clashing styles — check the compatibility matrix first

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

@@ -2,6 +2,7 @@
 name: typescale
 description: Generate a mathematical type scale — standalone or as a building block for identity
 user-invocable: true
+model: sonnet
 allowed-tools:
   - Read
   - Write
@@ -34,6 +35,7 @@ Generate a production-ready typography system with fluid responsive sizing, vert
 
 <rules>
 - Always use `AskUserQuestion` for user interaction — never prompt via plain text
+- One decision per question — never batch multiple questions in a single message
 - Foundation chunks follow `references/chunk-format.md` format exactly
 - All sizes include px, rem, AND fluid clamp() values for headings
 - Line heights snap to a 4px grid for vertical rhythm (body 24px = 6 × 4px)

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

@@ -2,36 +2,52 @@
 name: update
 description: Update GSP to the latest version
 user-invocable: true
+model: sonnet
+allowed-tools:
+  - Read
+  - Bash
+  - AskUserQuestion
+  - Glob
+  - WebFetch
 ---
 <objective>
 Check for GSP updates, show what's new, and run the update if the user confirms.
 </objective>
 
+<rules>
+- Always use `AskUserQuestion` for user-facing questions — never raw text prompts
+- One decision per question — never batch multiple questions in a single message
+</rules>
+
 <process>
 
 ## Step 1 — Detect installation
 
-Check for a `VERSION` file to determine install type. The runtime directory varies by tool:
-- Claude Code: `.claude/` (local) or `~/.claude/` (global)
-- OpenCode: `.opencode/` (local) or `~/.config/opencode/` (global)
-- Gemini: `.gemini/` (local) or `~/.gemini/` (global)
-- Codex: `.codex/` (local) or `~/.codex/` (global)
+Determine the runtime by checking which config directory exists. Check local first, then global:
+
+| Runtime | Local dir | Global dir |
+|---------|-----------|------------|
+| Claude Code | `.claude/` | `~/.claude/` |
+| OpenCode | `.opencode/` | `~/.config/opencode/` |
+| Gemini | `.gemini/` | `~/.gemini/` |
+| Codex | `.codex/` | `~/.codex/` |
 
-Look for the VERSION file in both local and global locations. Check two paths per location (current layout first, legacy fallback):
+For each runtime, look for the VERSION file in two paths (current layout first, legacy fallback):
 1. `{runtime-dir}/VERSION` (v0.5.0+)
 2. `{runtime-dir}/get-shit-pretty/VERSION` (legacy v0.4.x)
 
-If neither exists in either location, tell the user GSP doesn't appear to be installed and suggest running:
+Record which runtime(s) and install type (local/global) were found.
+
+If no VERSION file exists anywhere, tell the user GSP doesn't appear to be installed and suggest:
 ```
 npx get-shit-pretty
 ```
 Then stop.
 
-Read the VERSION file to get the installed version. Store which type was detected (local or global).
+Read the VERSION file to get the installed version.
 
 ## Step 2 — Check latest version
 
-Run:
 ```bash
 npm view get-shit-pretty version
 ```
@@ -40,7 +56,7 @@ If the command fails, tell the user the version check failed (they may be offlin
 
 ## Step 3 — Compare versions
 
-If installed version >= latest version, tell the user:
+If installed version >= latest version:
 ```
 GSP v{installed} is already up to date.
 ```
@@ -48,40 +64,55 @@ Then stop.
 
 ## Step 4 — Show what's new
 
-Tell the user:
 ```
 Update available: v{installed} → v{latest}
 ```
 
-Fetch the changelog to show what changed:
+Fetch the changelog:
 ```bash
 curl -sf https://raw.githubusercontent.com/jubscodes/get-shit-pretty/main/CHANGELOG.md
 ```
 
-If the fetch succeeds, extract and display the section for the latest version. If it fails, skip — changelog display is optional.
+If the fetch succeeds, extract and display the section(s) between the installed and latest versions. If it fails, skip — changelog display is optional.
 
 ## Step 5 — Warn about clean install
 
-Tell the user:
 ```
 The update replaces:
-  • skills/gsp-*       (all GSP skills)
-  • get-shit-pretty/*  (runtime files)
-  • gsp-* agents       (all GSP agents)
+  • skills/gsp-*          (all GSP skills + sibling files)
+  • prompts/              (agent system prompts)
+  • templates/            (config, state, brief templates)
+  • references/           (shared reference material)
+  • agents/gsp-*          (all GSP agents)
 
 Custom files outside these prefixes are preserved.
 ```
 
 ## Step 6 — Confirm with user
 
-Ask the user to confirm before proceeding. If they decline, stop.
+Use `AskUserQuestion`:
+- **Update now** — "Install v{latest}"
+- **Skip** — "I'll update later"
+
+If skip → stop.
 
 ## Step 7 — Execute update
 
-Based on the detected install type from Step 1:
+Build the installer command based on what was detected in Step 1:
+
+**Runtime flag:** use the detected runtime (`--claude`, `--opencode`, `--gemini`, `--codex`). If multiple runtimes were found, use `--all`.
+
+**Scope flag:** `--local` if local install was detected, `--global` if global.
+
+```bash
+npx get-shit-pretty@latest {runtime-flag} {scope-flag}
+```
 
-- **Local install**: run `npx get-shit-pretty@latest --claude --local`
-- **Global install**: run `npx get-shit-pretty@latest --claude`
+Examples:
+- Local Claude: `npx get-shit-pretty@latest --claude --local`
+- Global Claude: `npx get-shit-pretty@latest --claude --global`
+- Global OpenCode: `npx get-shit-pretty@latest --opencode --global`
+- Multiple runtimes: `npx get-shit-pretty@latest --all --global`
 
 Show the output to the user.
 
@@ -102,10 +133,9 @@ rm -f {runtime-dir}/get-shit-pretty/.update-cache.json
 
 ## Step 9 — Remind to restart
 
-Tell the user:
 ```
 GSP updated to v{latest}.
-Restart your Claude Code session to load the new commands and agents.
+Restart your session to load the new skills and agents.
 ```
 
 </process>

package/gsp/templates/branding/config.json

@@ -1,11 +1,12 @@
 {
-  "version": "0.5.0",
+  "version": "0.6.2",
   "project_type": "brand",
   "brand": {
     "name": "",
     "created": ""
   },
   "brand_mode": "new",
+  "e2e": false,
   "evolution_scope": {
     "preserve": [],
     "evolve": [],

package/gsp/templates/phases/identity.md

@@ -5,7 +5,7 @@
 
 ---
 
-> This phase produces 6 chunks + palettes.json + INDEX.md in the `identity/` directory.
+> This phase produces 5 chunks + palettes.json + INDEX.md in the `identity/` directory.
 
 ## Inputs
 - BRIEF.md — personas, constraints
@@ -26,7 +26,6 @@
 | `typography.md` | Primary + secondary typefaces, full type scale, responsive behavior |
 | `imagery-style.md` | Photography, illustration, iconography guidelines |
 | `brand-applications.md` | Key touchpoints showing the brand in use |
-| `brand-book.md` | 20-page brand book outline with section descriptions |
 
 Also produces `palettes.json` — machine-readable OKLCH color scales.
 
@@ -43,7 +42,7 @@ Each chunk follows the format in `references/chunk-format.md`.
   - **Usage rules**
 
 ### color-system.md
-- Full palette table: Role, Hex, RGB, Pantone, CMYK, Usage, Rationale
+- Full palette table: Role, Hex, RGB, Usage, Rationale
 - Semantic colors (error, success, warning)
 - Color rationale — connects to archetype and brand essence
 - Dark mode mapping table
@@ -65,6 +64,3 @@ Each chunk follows the format in `references/chunk-format.md`.
 - Key touchpoints showing the brand in use (digital, print, social)
 - Each application with visual direction and design notes
 
-### brand-book.md
-- 20-page outline covering: Brand Story, Strategy, Voice, Logo System,
-  Color, Typography, Imagery, Layout, Applications, Do's and Don'ts

package/gsp/templates/projects/config.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.5.0",
+  "version": "0.6.2",
   "project_type": "design",
   "project": {
     "name": "",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-pretty",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "Design engineering system for AI coding agents. Brand identity + design projects, from strategy to code.",
   "bin": {
     "get-shit-pretty": "bin/install.js"
@@ -39,32 +39,30 @@
     "url": "git+https://github.com/jubscodes/get-shit-pretty.git"
   },
   "devDependencies": {
-    "@tailwindcss/postcss": "^4.2.2",
-    "@types/node": "^25.5.0",
-    "@types/react": "^19.2.14",
-    "@types/react-dom": "^19.2.3",
-    "next": "^16.2.0",
-    "postcss": "^8.5.8",
-    "react": "^19.2.4",
-    "react-dom": "^19.2.4",
-    "tailwindcss": "^4.2.2",
-    "typescript": "^5.9.3"
-  },
-  "dependencies": {
     "@base-ui/react": "^1.3.0",
     "@mdx-js/loader": "^3.1.1",
     "@mdx-js/mdx": "^3.1.1",
     "@mdx-js/react": "^3.1.1",
     "@next/mdx": "^16.2.1",
+    "@tailwindcss/postcss": "^4.2.2",
+    "@types/node": "^25.5.0",
+    "@types/react": "^19.2.14",
+    "@types/react-dom": "^19.2.3",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "gray-matter": "^4.0.3",
     "lucide-react": "^0.577.0",
+    "next": "^16.2.0",
     "next-themes": "^0.4.6",
+    "postcss": "^8.5.8",
+    "react": "^19.2.4",
+    "react-dom": "^19.2.4",
     "shadcn": "^4.1.0",
     "shiki": "^4.0.2",
     "sonner": "^2.0.7",
     "tailwind-merge": "^3.5.0",
-    "tw-animate-css": "^1.4.0"
+    "tailwindcss": "^4.2.2",
+    "tw-animate-css": "^1.4.0",
+    "typescript": "^5.9.3"
   }
 }