get-shit-pretty 0.5.0 → 0.5.2

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

@@ -27,6 +27,8 @@ Critique design quality and audit accessibility compliance.
 @${CLAUDE_SKILL_DIR}/../../prompts/08-accessibility-auditor.md
 @${CLAUDE_SKILL_DIR}/../../templates/phases/critique.md
 @${CLAUDE_SKILL_DIR}/../../references/nielsen-heuristics.md
+@${CLAUDE_SKILL_DIR}/../../references/visual-taste.md
+@${CLAUDE_SKILL_DIR}/../../references/anti-patterns.md
 @${CLAUDE_SKILL_DIR}/../../references/wcag-checklist.md
 @${CLAUDE_SKILL_DIR}/../../references/color-composition.md
 </execution_context>
@@ -52,8 +54,8 @@ Read `{PROJECT_PATH}/config.json` to get `implementation_target`, `design_scope`
 **Identity:** Read `{BRAND_PATH}/identity/INDEX.md` → load all chunks.
 Fallback: `{BRAND_PATH}/identity/IDENTITY.md`.
 
-**System:** Read `{BRAND_PATH}/system/INDEX.md` → load all chunks.
-Fallback: `{BRAND_PATH}/system/SYSTEM.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).
@@ -147,36 +149,6 @@ If verdict is **Fail**:
 
 ## Step 6: Phase transition output
 
-Render the phase transition screen (see `references/phase-transitions.md` for styling):
-
-**If Pass/Conditional Pass:**
-
-```
-  ◆ critique complete — designs critiqued
-
-    critique/
-    ├── {actual files written}
-    └── INDEX.md
-
-  ──────────────────────────────
-```
-
-Then use `AskUserQuestion` with 3 options:
-- **Continue to build** — "implement designs in the codebase"
-- **View progress** — "see the full dashboard"
-- **Done for now** — "pick up later with /gsp:start"
-
-**If Fail:**
-
-```
-  ◈ critique — critical issues found, revising designs
-
-  ──────────────────────────────
-```
-
-Then use `AskUserQuestion` with 3 options:
-- **Revise designs** — "address critical issues and re-run critique"
-- **Override and continue** — "accept current designs and move to build"
-- **View issues** — "see the full critique report"
+Render phase transition (see `references/phase-transitions.md`). This phase has pass/fail variants — the reference covers both.
 </process>
 </output>

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

@@ -13,7 +13,7 @@ allowed-tools:
 <context>
 Phase 3 of the GSP project diamond. Uses the UI/UX Pattern Master prompt to design core screens following Apple HIG and the brand's design system.
 
-Works with the dual-diamond architecture: reads brand system from `.design/branding/{brand}/system/` via `brand.ref`, reads/writes project assets in `.design/projects/{project}/`.
+Works with the dual-diamond architecture: reads brand system from `.design/branding/{brand}/patterns/` via `brand.ref`, reads/writes project assets in `.design/projects/{project}/`.
 </context>
 
 <objective>
@@ -28,6 +28,9 @@ Design core UI/UX screens and interaction flows.
 @${CLAUDE_SKILL_DIR}/../../prompts/03-ui-ux-pattern-master.md
 @${CLAUDE_SKILL_DIR}/../../templates/phases/design.md
 @${CLAUDE_SKILL_DIR}/../../references/apple-hig-patterns.md
+@${CLAUDE_SKILL_DIR}/../../references/visual-effects.md
+@${CLAUDE_SKILL_DIR}/../../references/block-patterns.md
+@${CLAUDE_SKILL_DIR}/../../references/anti-patterns.md
 </execution_context>
 
 <process>
@@ -40,6 +43,13 @@ Set `PROJECT_PATH` = `.design/projects/{project}`
 Read `{PROJECT_PATH}/brand.ref` to resolve brand path:
 - Set `BRAND_PATH` = `.design/branding/{brand}`
 
+## 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.
+
+Research (Phase 2) is recommended but not required — if skipped, log: "No research artifacts found — designing from brief only."
+
 ## Step 1: Load context
 
 Read `{PROJECT_PATH}/config.json` — get `implementation_target`, `design_scope`, `codebase_type`.
@@ -57,19 +67,27 @@ Check `{PROJECT_PATH}/STATE.md` for design status. If status is `needs-revision`
 
 If `{PROJECT_PATH}/references/` exists, scan for files (images, PDFs, markdown, URLs). Pass any found references to the designer agent as additional context.
 
-### Brand system (chunk-first)
+### Brand patterns (chunk-first)
 
-Read `{BRAND_PATH}/system/INDEX.md`. If it exists, load all foundation chunks + selective component chunks.
+Read `{BRAND_PATH}/patterns/INDEX.md`. If it exists, load all foundation chunks + selective component chunks.
 
-Fallback: read `{BRAND_PATH}/system/SYSTEM.md` (legacy monolith). Log: "⚠️ Legacy system format detected — consider re-running /gsp:brand-patterns for chunk output."
+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.
 
 ### Brand context (selective)
 
-Read `{BRAND_PATH}/identity/INDEX.md`. If it exists, load `color-system.md` and `typography.md`.
+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)
+
+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`).
+
+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 not found, proceed without it (older brands may not have this file).
+
 ### Brief (chunk-first)
 
 Read `{PROJECT_PATH}/brief/INDEX.md`. If it exists, load `scope.md` and `target-adaptations.md`.
@@ -101,7 +119,7 @@ When `implementation_target` is not `figma`:
 
 ## Step 3: Spawn designer
 
-Spawn the `gsp-designer` agent with all prior artifacts, the UI/UX Pattern Master prompt (03), design output template, Apple HIG patterns reference, implementation_target, design_scope, codebase_type, target screens (when partial), existing components inventory, custom references (when available), and critique fixes (when in revision mode).
+Spawn the `gsp-designer` agent with all prior artifacts, the UI/UX Pattern Master prompt (03), design output template, Apple HIG patterns reference, brand style prompt ({brand-name}.md when available), implementation_target, design_scope, codebase_type, target screens (when partial), existing components inventory, custom references (when available), and critique fixes (when in revision mode).
 
 **Output path:** `{PROJECT_PATH}/design/`
 
@@ -120,25 +138,6 @@ Update `{PROJECT_PATH}/STATE.md`:
 
 ## Step 5: Phase transition output
 
-Render the phase transition screen (see `references/phase-transitions.md` for styling):
-
-```
-  ◆ design complete — screens designed
-
-    design/
-    ├── {actual screen chunks}
-    ├── shared/
-    │   ├── {shared chunks}
-    │   └── component-plan.md
-    ├── preview.html
-    └── INDEX.md
-
-  ──────────────────────────────
-```
-
-Then use `AskUserQuestion` with 3 options:
-- **Continue to critique** — "critique designs + accessibility audit"
-- **View progress** — "see the full dashboard"
-- **Done for now** — "pick up later with /gsp:start"
+Render phase transition (see `references/phase-transitions.md`).
 </process>
 </output>

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

@@ -53,7 +53,7 @@ If brief doesn't exist, tell the user to run `/gsp:project-brief` first.
 
 ### Brand system (selective)
 
-Read `{BRAND_PATH}/system/INDEX.md`. If it exists, load foundation chunks (to understand the design system constraints).
+Read `{BRAND_PATH}/patterns/INDEX.md`. If it exists, load foundation chunks (to understand the design system constraints).
 
 ### Brand discovery (selective)
 
@@ -77,8 +77,14 @@ Read:
 3. Route: "Run `/gsp:project-build`."
 4. Stop here.
 
+## Step 1.75: Pre-fetch references (background)
+
+If competitor URLs or reference sites are mentioned in BRIEF.md or `{PROJECT_PATH}/references/`, use `WebFetch` with `run_in_background: true` to pre-fetch them. This warms content for the researcher agent.
+
 ## Step 2: Spawn project researcher
 
+Include any pre-fetched reference content in the agent context.
+
 Spawn the `gsp-project-researcher` agent with:
 - Brief scope chunks
 - Brand system foundation chunks
@@ -128,21 +134,6 @@ Update `{PROJECT_PATH}/STATE.md`:
 
 ## Step 4: Phase transition output
 
-Render the phase transition screen (see `references/phase-transitions.md` for styling):
-
-```
-  ◆ research complete — patterns and approaches researched
-
-    research/
-    ├── {actual files written}
-    └── INDEX.md
-
-  ──────────────────────────────
-```
-
-Then use `AskUserQuestion` with 3 options:
-- **Continue to design** — "design screens and flows"
-- **View progress** — "see the full dashboard"
-- **Done for now** — "pick up later with /gsp:start"
+Render phase transition (see `references/phase-transitions.md`).
 </process>
 </output>

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

@@ -13,7 +13,7 @@ allowed-tools:
 <context>
 Phase 6 of the GSP project diamond. QA validates that the actual codebase implementation matches the design intent — checking real source files for token usage, screen coverage, component quality, and accessibility compliance.
 
-Works with the dual-diamond architecture: reads brand system from `.design/branding/{brand}/system/` via `brand.ref`, reads/writes project assets in `.design/projects/{project}/`.
+Works with the dual-diamond architecture: reads brand system from `.design/branding/{brand}/patterns/` via `brand.ref`, reads/writes project assets in `.design/projects/{project}/`.
 </context>
 
 <objective>
@@ -56,8 +56,10 @@ Read `{PROJECT_PATH}/config.json` to get `implementation_target`, `design_scope`
 **Design:** Read `{PROJECT_PATH}/design/INDEX.md` → load all screen chunks.
 Fallback: `{PROJECT_PATH}/screens/INDEX.md` (legacy).
 
-**Brand system:** Read `{BRAND_PATH}/system/INDEX.md` → load foundation + component chunks.
-Also read `{BRAND_PATH}/system/tokens.json`.
+**Brand patterns:** Read `{BRAND_PATH}/patterns/INDEX.md` → load foundation + component chunks.
+Also read `{BRAND_PATH}/patterns/tokens.json`.
+
+**Brand identity (selective):** Read `{BRAND_PATH}/identity/imagery-style.md` (if exists) — needed for imagery audit.
 
 **Brief:** Read `{PROJECT_PATH}/brief/INDEX.md` → load scope and adaptations.
 
@@ -172,38 +174,5 @@ If verdict is **Fail**:
 
 ## Step 6: Phase transition output
 
-Render the phase transition screen (see `references/phase-transitions.md` for styling):
-
-**If Pass/Conditional Pass:**
-
-```
-  ◆ review complete — implementation validated
-
-    review/
-    ├── acceptance-report.md
-    ├── issues.md
-    └── INDEX.md
-
-  ──────────────────────────────
-
-  fully pretty.
-```
-
-Then use `AskUserQuestion` with 3 options:
-- **Launch campaign** — "create launch and marketing assets"
-- **View progress** — "see the full dashboard"
-- **Done for now** — "pick up later with /gsp:start"
-
-**If Fail:**
-
-```
-  ◈ review — QA found issues, needs revision
-
-  ──────────────────────────────
-```
-
-Then use `AskUserQuestion` with 3 options:
-- **Fix and rebuild** — "address issues in review/issues.md"
-- **View issues** — "see the full QA report"
-- **Done for now** — "pick up later with /gsp:start"
+Render phase transition (see `references/phase-transitions.md`). This phase has pass/fail variants — the reference covers both.
 </process>

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

@@ -10,6 +10,8 @@ allowed-tools:
   - Glob
   - Grep
   - Agent
+  - WebSearch
+  - WebFetch
 ---
 <context>
 You are the GSP (Get Shit Pretty) entry point — a design lead starting a first call with a client. You scan the codebase and `.design/` directory, greet the user with what you found, and flow naturally into the right workflow.
@@ -39,6 +41,11 @@ Through 2-3 rounds of natural conversation, gather a complete brief and create t
 @${CLAUDE_SKILL_DIR}/../../templates/exports-index.md
 </execution_context>
 
+<rules>
+- Never infer the user's name from package metadata, git config, or file paths — those are authors, not the current user.
+- Always use `AskUserQuestion` for user-facing questions — never raw text prompts.
+</rules>
+
 <questioning_principles>
 Follow these principles throughout all conversations:
 
@@ -59,13 +66,14 @@ Scan `.design/` for existing brands and projects:
 - Check `.design/projects/` for project directories (each has a `config.json` with `project_type: "design"`)
 - Check for legacy flat `.design/config.json` at root (pre-0.4.0 structure)
 - For each brand/project found, read its `config.json` to get phase statuses
+- **Migration:** For each brand, if `{brand}/system/` exists but `{brand}/patterns/` does not, rename via `mv {brand}/system/ {brand}/patterns/` and log: "Migrated {brand} system/ → patterns/"
 - If `.design/CHANGELOG.md` doesn't exist, create it from `templates/changelog.md`
 
 ### Step 1b: Run design system scan (background)
 
 Spawn a background agent with `run_in_background: true` that follows the `/gsp:design-system` skill methodology:
 - Use `subagent_type: "general-purpose"`
-- Prompt: "Follow the /gsp:design-system skill methodology. Scan the codebase and produce `.design/system/{STACK,COMPONENTS,TOKENS,CONVENTIONS,CONCERNS}.md`. Read the templates from `.claude/templates/system/` for output format. If no package.json exists, write minimal greenfield versions."
+- Prompt: "Follow the /gsp:design-system skill methodology. Scan the codebase and produce `.design/system/{STACK,COMPONENTS,TOKENS,CONVENTIONS,CONCERNS}.md`. Read the templates from the GSP templates/system/ directory for output format. If no package.json exists, write minimal greenfield versions."
 - Store the task reference — you'll read results in Step 3 Round 2 or Step 4.
 
 This produces workspace-level documents consumed by downstream skills and agents.
@@ -154,7 +162,7 @@ From the greeting exchange, determine which flow to run:
 1. Ask for brand name (kebab-case, e.g., "acme-corp")
 2. Create directory structure:
 ```bash
-mkdir -p .design/branding/{name}/{audit,discover,strategy,identity,system}
+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.
@@ -163,20 +171,26 @@ mkdir -p .design/branding/{name}/{audit,discover,strategy,identity,system}
 - Company name, industry, stage
 - What problem does this business solve? For whom? How differently?
 - Business model (how it makes money)
+- Who are the main competitors? (users usually know their top 2-3)
 - Primary persona — use `AskUserQuestion` to confirm or build: present an inferred persona profile (name, role, day-in-the-life, frustration, aspiration, discovery, trust signals) and let user correct. If they say "fintech for Gen Z" → infer and present a concrete persona.
 - Secondary persona (if relevant)
 - Mission and vision
 
-This round is the most important. The personas should feel like real people, not demographic buckets.
+This round is the most important. The personas should feel like real people, not demographic buckets. Dig into the emotional layer: anxiety, ambition, frustration, curiosity, status, safety.
 
 **Round 2 — Brand Essence & Landscape:**
-- Brand personality — use `AskUserQuestion` with 2-3 concrete personality directions:
-  - **Precise & exacting** — "Like Stripe or Linear" / preview: "Your dashboard is ready. Zero errors, zero clutter."
-  - **Warm & human** — "Like Mailchimp or Notion" / preview: "Hey! Your project's looking great. Here's what's next."
-  - **Bold & unapologetic** — "Like Figma or Vercel" / preview: "Ship it. We'll make it beautiful."
+
+Before presenting personality options, **internally synthesize** from Round 1:
+- **Promise:** what should someone feel when they interact with this brand? (derived from persona frustrations + aspirations)
+- **Point of view:** what does this brand disagree with in the category? (derived from the problem + how it solves it differently)
+
+You do NOT ask the user these directly — you use them to ground the 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 — who are the main competitors? What sets this brand apart?
+- 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:**
@@ -225,6 +239,8 @@ Skip or compress rounds if the user gives enough upfront. Don't over-ask.
 
 ## Step 4: Project flow
 
+**Background:** Run `git branch --show-current` with `run_in_background: true` now — result will be ready by the time we need it for git context detection.
+
 1. Show available brands:
 ```
 Available brands:
@@ -247,8 +263,9 @@ mkdir -p .design/projects/{name}/{brief,research,design,critique,build,review,co
 
 ### Detect git context
 
-1. Run `git branch --show-current` to detect current branch
-2. If a branch is detected, use `AskUserQuestion`: "I see you're on `{branch}` — track this as the project branch?"
+Use the git branch detected earlier (run `git branch --show-current` in background at the start of Step 4, while asking for project name — result is ready by now).
+
+1. If a branch was detected, use `AskUserQuestion`: "I see you're on `{branch}` — track this as the project branch?"
    - **Yes, use this branch** — "Track `{branch}`"
    - **Different branch** — "I want to use a different branch name"
 3. Store in config.json `git.branch` and STATE.md `## Git` table
@@ -346,7 +363,7 @@ If the user names a preset directly at any point, skip the group step.
 
 1. Create brand directory:
 ```bash
-mkdir -p .design/branding/_style-{preset}/system/
+mkdir -p .design/branding/_style-{preset}/patterns/
 ```
 
 2. Invoke `/gsp:style {preset}` via Skill tool — this writes:
@@ -395,7 +412,7 @@ Continue directly to Step 4 (project flow) with these modifications:
 
 If a user later wants full branding, they can:
 1. Run `/gsp:start` → "Brand identity" to create a real brand
-2. Full diamond produces identity + system with real tokens
+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
 </process>