get-shit-pretty 0.4.2 → 0.5.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,24 @@
+{
+  "name": "gsp",
+  "version": "0.5.0",
+  "description": "Design engineering system for AI coding agents. Brand identity + design projects, from strategy to code.",
+  "author": {
+    "name": "jubscodes",
+    "url": "https://github.com/jubscodes"
+  },
+  "homepage": "https://github.com/jubscodes/get-shit-pretty",
+  "repository": "https://github.com/jubscodes/get-shit-pretty",
+  "license": "MIT",
+  "keywords": [
+    "design",
+    "design-system",
+    "brand",
+    "ui-ux",
+    "design-engineering",
+    "shadcn",
+    "figma",
+    "apple-hig",
+    "wcag",
+    "accessibility"
+  ]
+}

package/.mcp.json

@@ -0,0 +1,16 @@
+{
+  "mcpServers": {
+    "github": {
+      "type": "http",
+      "url": "https://api.githubcopilot.com/mcp/"
+    },
+    "figma": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@anthropic/mcp-figma"],
+      "env": {
+        "FIGMA_ACCESS_TOKEN": "${FIGMA_ACCESS_TOKEN}"
+      }
+    }
+  }
+}

package/README.md

@@ -2,9 +2,7 @@
 
 # GET SHIT PRETTY
 
-**Design engineering for AI coding tools.**
-
-**Research, brand, design system, UI, specs, review, build, launch — from your terminal.**
+**Design engineering system for AI coding tools.**
 
 [![npm version](https://img.shields.io/npm/v/get-shit-pretty?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/get-shit-pretty)
 [![npm downloads](https://img.shields.io/npm/dm/get-shit-pretty?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/get-shit-pretty)
@@ -21,11 +19,13 @@ npx get-shit-pretty
 
 <br>
 
-*"Vibe-coded apps work. They also all look the same. GSP fixes that."*
+*"GSD gets shit done. GSP gets shit pretty."*
+
+*Brief to build. In your terminal.*
 
 <br>
 
-[Why GSP Exists](#why-gsp-exists) · [How It Works](#how-it-works) · [Commands](#commands) · [Agents & Prompts](#agents--prompts) · [AI Tool Support](#ai-coding-tool-support)
+[Why GSP Exists](#why-gsp-exists) · [How It Works](#how-it-works) · [Branding Diamond](#-diamond-1--branding) · [Project Diamond](#-diamond-2--project) · [Commands](#commands) · [Agents](#agents) · [AI Tool Support](#ai-coding-tool-support)
 
 </div>
 
@@ -55,202 +55,208 @@ The missing half of the bridge.
 
 ## How It Works
 
-### 1. Start a Project
+GSP follows a **dual-diamond** architecture — two complete design cycles that take you from nothing to shipped.
 
 ```
-/gsp:start
+/gsp:start → picks up where you left off, routes you forward
+
+         ◆ Diamond 1 — Branding                  ◆ Diamond 2 — Project
+    ┌──────────────────────────┐           ┌──────────────────────────────┐
+    │  brand-research          │           │  project-brief               │
+    │    ↓                     │           │    ↓                         │
+    │  brand-strategy          │           │  project-research            │
+    │    (includes voice       │           │    ↓                         │
+    │     and messaging)       │           │  project-design              │
+    │    ↓                     │           │    ↓                         │
+    │  brand-identity          │           │  project-critique ←──┐      │
+    │    ↓                     │           │    ↓            loop │      │
+    │  brand-patterns          │           │  project-build       │      │
+    └──────────────────────────┘           │    ↓                 │      │
+                                           │  project-review ─────┘      │
+                                           └──────────────────────────────┘
+                                                      ↓
+                                                  /gsp:launch (optional)
 ```
 
-Answer questions about your product — what it does, who it's for, the vibe you're going for. GSP creates a design brief that guides everything downstream.
-
-**Creates:** `.design/BRIEF.md`
+All artifacts live in `.design/` within your project directory.
 
 ---
 
-### 2. Research
+### ◆ Diamond 1 — Branding
 
-```
-/gsp:project-research
-```
+Build your brand from research to design system. Each phase feeds the next.
 
-Analyzes design trends in your space — competitor patterns, emerging styles, what's working and what's not. Start with context, not guesses.
+> **Already have a brand?** Start with `/gsp:brand-audit` to assess what you have before evolving it.
 
-**Creates:** `.design/research/TRENDS.md`
+#### 1. `/gsp:brand-research` — Market landscape
 
----
+Research your audience, competitors, and market position. Understand the terrain before making decisions.
 
-### 3. Brand
+**Creates:** `.design/branding/{brand}/discover/`
 
-```
-/gsp:brand
-```
+#### 2. `/gsp:brand-strategy` — Who you are and how you sound
 
-Builds your complete identity — positioning, personality, logo directions, color palette, typography system. Your brand, not a default theme.
+Define your archetype, positioning, and personality using the Kapferer Brand Identity Prism. Includes voice, tone spectrum, messaging framework, and naming conventions — verbal identity is part of strategy.
 
-**Creates:** `.design/brand/IDENTITY.md`
+**Creates:** `.design/branding/{brand}/strategy/`
 
----
+#### 3. `/gsp:brand-identity` — How you look
 
-### 4. Design System
+Create your visual identity — logo directions, color palette, typography system, imagery style. Design decisions, not decoration.
 
-```
-/gsp:system
-```
+**Creates:** `.design/branding/{brand}/identity/`
 
-Translates your brand into a functional design system — color scales, type scales, spacing, component foundations, and design tokens. Your system, in code.
+#### 4. `/gsp:brand-patterns` — Your design system
 
-**Creates:** `.design/system/SYSTEM.md`, `tokens.json`
+Translate your brand into tokens, components, and a living design system. Everything codified and ready to build with.
+
+**Creates:** `.design/branding/{brand}/system/`
 
 ---
 
-### 5. UI Design
+### ◆ Diamond 2 — Project
 
-```
-/gsp:project-design
-```
+Design and build a product using your brand. Critique loops catch issues before they ship.
 
-Designs your screens and interaction flows following Apple HIG patterns. Layout, navigation, states, responsive behavior — all documented with enough detail to build from.
+#### 1. `/gsp:project-brief` — Scope what you're building
 
-**Creates:** `.design/screens/SCREENS.md`
+Define your project through guided Q&A — what it does, who it's for, what screens it needs. The brief that guides everything downstream.
 
----
+**Creates:** `.design/projects/{project}/BRIEF.md`
 
-### 6. Implementation Specs
+#### 2. `/gsp:project-research` — Patterns and precedents
 
-```
-/gsp:spec
-```
+Deep research into UX patterns, competitor approaches, and technical considerations for your specific project.
 
-Maps your screen designs to your implementation target — shadcn/ui components, React Native Reusables, an existing design system, Figma specs, or lightweight code specs. Bridges design decisions to whatever UI framework your project uses.
+**Creates:** `.design/projects/{project}/research/`
 
-**Creates:** `.design/specs/SPECS.md`
+#### 3. `/gsp:project-design` — Screens and flows
 
----
+Design your UI screens and interaction flows following Apple HIG patterns. Layout, navigation, states, responsive behavior — documented to build from.
 
-### 7. Review
+**Creates:** `.design/projects/{project}/design/`
 
-```
-/gsp:project-review
-```
+#### 4. `/gsp:project-critique` — Critique + accessibility
 
-Two parallel agents audit your designs:
-- **Design Critique** — Structured critique using Nielsen's 10 usability heuristics
-- **Accessibility Audit** — WCAG 2.2 AA compliance check
+Two parallel audits: structured design critique using Nielsen's 10 usability heuristics, and a WCAG 2.2 AA accessibility check. If issues surface, loop back and fix before building.
 
-If issues are found, loop back to fix before building.
+**Creates:** `.design/projects/{project}/critique/`
 
-**Creates:** `.design/review/CRITIQUE.md`, `ACCESSIBILITY.md`
+#### 5. `/gsp:project-build` — Designs to code
 
----
+Translate reviewed designs into production-ready frontend code — written directly into your codebase. Components, styles, interactions built from your design system and tokens.
 
-### 8. Build
+**Creates:** Components and styles in your codebase
 
-```
-/gsp:project-build
-```
+#### 6. `/gsp:project-review` — QA against designs
 
-Translates reviewed designs into production-ready frontend code. Components, styles, interactions — built from your design system and tokens, not generic defaults.
+Validate what was built against the original design intent. Catches drift between design decisions and implementation.
 
-**Creates:** `.design/build/CODE.md`, `components/`
+**Creates:** `.design/projects/{project}/review/`
 
 ---
 
-### 9. Launch
-
-```
-/gsp:launch
-```
+### Optional: `/gsp:launch`
 
-Creates marketing campaign assets — landing page copy, social media content, launch materials. Your product ships with a story, not just code.
+Create marketing campaign assets — landing page copy, social media content, launch materials. Your product ships with a story, not just code.
 
-**Creates:** `.design/launch/CAMPAIGN.md`
+**Creates:** `.design/projects/{project}/launch/`
 
 ---
 
-### The Full Pipeline
+## Commands
 
-```
-/gsp:start → BRIEF.md
-       ↓
-/gsp:project-research    → .design/research/TRENDS.md
-       ↓
-/gsp:brand       → .design/brand/IDENTITY.md
-       ↓
-/gsp:system      → .design/system/SYSTEM.md + tokens.json
-       ↓
-/gsp:project-design      → .design/screens/SCREENS.md
-       ↓
-/gsp:spec        → .design/specs/SPECS.md
-       ↓
-/gsp:project-review      → .design/review/CRITIQUE.md + ACCESSIBILITY.md
-       ↓  (loop back if issues found)
-/gsp:project-build       → .design/build/CODE.md + components/
-       ↓
-/gsp:launch      → .design/launch/CAMPAIGN.md
-```
+### Entry
 
-All artifacts live in `.design/` within your project directory.
+| Command | What it does |
+|---------|--------------|
+| `/gsp:start` | Pick up where you left off — routes you forward |
+| `/gsp:progress` | Check project status |
+| `/gsp:help` | Show command reference |
 
----
+### Branding
 
-## Commands
+| Command | What it does |
+|---------|--------------|
+| `/gsp:brand-audit` | Audit an existing brand before evolving it |
+| `/gsp:brand-research` | Research market, audience, competitors |
+| `/gsp:brand-strategy` | Define archetype, positioning, personality, voice, messaging |
+| `/gsp:brand-identity` | Create visual identity — logo, color, type |
+| `/gsp:brand-patterns` | Build design system — tokens, components |
+
+### Project
 
 | Command | What it does |
 |---------|--------------|
-| `/gsp:start` | Initialize a design brief through guided Q&A |
-| `/gsp:project-research` | Analyze design trends for your industry |
-| `/gsp:brand` | Create brand identity (strategy, logo, color, type) |
-| `/gsp:system` | Build design system foundations + tokens |
-| `/gsp:project-design` | Design UI/UX screens and flows |
-| `/gsp:spec` | Generate implementation specifications |
-| `/gsp:project-review` | Design critique + accessibility audit |
+| `/gsp:project-brief` | Scope through guided Q&A |
+| `/gsp:project-research` | UX patterns, competitor analysis |
+| `/gsp:project-design` | Design screens and interaction flows |
+| `/gsp:project-critique` | Nielsen's heuristics + WCAG 2.2 AA audit |
 | `/gsp:project-build` | Translate designs to production code |
-| `/gsp:launch` | Create marketing campaign assets |
-| `/gsp:progress` | Check project status |
-| `/gsp:help` | Show command reference |
+| `/gsp:project-review` | QA validation against designs |
+| `/gsp:launch` | Marketing campaign assets |
+
+### Utility
+
+| Command | What it does |
+|---------|--------------|
+| `/gsp:add-reference` | Add reference material to a project |
+| `/gsp:doctor` | Check project health |
+| `/gsp:update` | Update GSP to latest version |
+| `/gsp:art` | Craft ASCII art interactively |
+| `/gsp:pretty` | Surprise ASCII art in the terminal |
 
 ---
 
-## Agents & Prompts
+## Agents
 
 GSP ships with 15 specialized agents, each modeled after a real design discipline:
 
 | Agent | Role |
 |-------|------|
-| **Design System Architect** | Complete design systems (Apple Principal Designer level) |
-| **Brand Strategist** | Full brand strategies (Pentagram Creative Director level) |
-| **Identity Designer** | Visual identity — logo directions, color palettes, typography systems |
-| **Verbal Strategist** | Verbal identity — voice, tone spectrum, messaging, naming |
-| **UI/UX Designer** | App UI design following Apple HIG |
-| **Campaign Director** | Marketing campaign asset libraries |
-| **Project Scoper** | Implementation specifications for any UI target |
-| **Design Critic** | Structured critiques using Nielsen's 10 heuristics |
-| **Trend Researcher** | Industry trend analysis and competitive research |
-| **Project Researcher** | Deep UX patterns, competitor analysis, technical research |
-| **Design-to-Code Builder** | Design to production-ready frontend code |
-| **Deliverable Reviewer** | Deliverable validation — token compliance, screen coverage |
+| **Brand Strategist** | Brand strategy using Kapferer Prism, archetypes, positioning, voice, and messaging |
+| **Identity Designer** | Visual identity — logo, color palettes, typography systems |
+| **Design System Architect** | Complete design systems — tokens, components, foundations |
 | **Brand Auditor** | Brand coherence assessment and evolution mapping |
-| **Codebase Scanner** | Codebase inventory and existing design system detection |
-| **Pipeline Auditor** | Pipeline consistency auditing |
+| **Trend Researcher** | Market landscape, competitor analysis, emerging patterns |
+| **Project Researcher** | Deep UX patterns, competitor UX, technical approaches |
+| **Project Scoper** | Project scope through guided Q&A |
+| **UI/UX Designer** | Screen design and interaction flows following Apple HIG |
+| **Design Critic** | Structured critiques using Nielsen's 10 heuristics |
+| **Accessibility Auditor** | WCAG 2.2 AA compliance auditing |
+| **Design-to-Code Builder** | Designs to production-ready frontend code |
+| **Deliverable Reviewer** | QA validation — implementation against design intent |
+| **Campaign Director** | Marketing campaign asset libraries |
+| **Codebase Scanner** | Tech stack detection and existing pattern inventory |
+| **ASCII Artist** | Terminal ASCII art — context-aware art generation |
 
-Each agent has deep reference material — Apple HIG patterns, Nielsen's heuristics, WCAG checklists, design token standards — baked into its prompts.
+Each agent carries deep reference material — Apple HIG patterns, Nielsen's heuristics, WCAG checklists, design token standards — baked into its prompts.
 
 ---
 
 ## AI Coding Tool Support
 
-GSP works across all major AI coding tools:
+GSP works across all major AI coding tools. The installer converts Claude Code's native format into each runtime's expected format.
 
 | Feature | Claude Code | OpenCode | Gemini CLI | Codex CLI |
 |---------|:-----------:|:--------:|:----------:|:---------:|
-| Slash commands | `/gsp:command` | `/gsp-command` | `/gsp:command` | `$gsp-command` |
-| Agents | Yes | Yes | Yes | Yes |
-| Prompts | Yes | Yes | Yes | Yes |
-| Templates | Yes | Yes | Yes | Yes |
+| Skills | 24 | 24 | 24 | 24 |
+| Agents | 15 | 15 | 15 (experimental) | — |
+| Slash syntax | `/gsp:command` | `/gsp-command` | `/gsp:command` | `$gsp-command` |
+| Prompts + templates | Yes | Yes | Yes | Yes |
 | References | Yes | Yes | Yes | Yes |
-| Statusline | Yes | — | — | — |
-| Global install | `~/.claude` | `~/.config/opencode` | `~/.gemini` | `~/.codex` |
-| Local install | `.claude/` | `.opencode/` | `.gemini/` | `.codex/` |
+| Statusline hooks | Yes | — | — | — |
+
+### Runtime directories
+
+| Runtime | Config / bundle | Skills | Agents |
+|---------|-----------------|--------|--------|
+| Claude Code | `~/.claude/` | `~/.claude/skills/` | `~/.claude/agents/` |
+| OpenCode | `~/.config/opencode/` | `~/.config/opencode/skills/` | `~/.config/opencode/agents/` |
+| Gemini CLI | `~/.gemini/` | `~/.gemini/skills/` | `~/.gemini/agents/` |
+| Codex CLI | `~/.codex/` | `~/.agents/skills/` | — |
+
+> **Codex note:** Skills are discovered at `~/.agents/skills/`, not `~/.codex/skills/`. Config and bundle files (prompts, templates, references) stay at `~/.codex/get-shit-pretty/`. Codex does not support agent `.md` files.
 
 ---
 
@@ -293,25 +299,73 @@ npx get-shit-pretty --all --global
 ```bash
 npx get-shit-pretty --claude --global --uninstall
 npx get-shit-pretty --opencode --global --uninstall
+npx get-shit-pretty --gemini --global --uninstall
 npx get-shit-pretty --codex --global --uninstall
 ```
 
 </details>
 
 <details>
-<summary><strong>Legacy install (bash)</strong></summary>
+<summary><strong>Use as Claude Code plugin</strong></summary>
 
 ```bash
-git clone https://github.com/jubscodes/get-shit-pretty.git ~/get-shit-pretty
-cd ~/get-shit-pretty
-chmod +x install.sh
-./install.sh
+# From a project directory:
+claude --plugin-dir /path/to/get-shit-pretty
 ```
 
+Uses the `.claude-plugin/plugin.json` manifest. Skills, agents, and hooks load directly from source — no install step needed.
+
 </details>
 
 ---
 
+## Repo Structure
+
+```
+get-shit-pretty/
+├── .claude-plugin/        Plugin manifest (plugin.json)
+├── bin/
+│   └── install.js         Multi-runtime installer
+├── scripts/               Hook scripts and utilities
+├── gsp/                   Source of truth for all content
+│   ├── agents/            15 subagents (gsp-*.md)
+│   ├── commands/gsp/      20 slash commands (backward compat)
+│   ├── skills/            24 skills (*/SKILL.md — primary)
+│   ├── hooks/             Plugin-level hooks (hooks.json)
+│   ├── prompts/           12 agent system prompts
+│   ├── templates/         Config, state, brief, roadmap templates
+│   └── references/        Shared reference material
+├── dev/                   Internal dev tools (not installed)
+│   ├── skills/            Dev-only skills (gsp-audit, gsp-runtime-compat)
+│   └── scripts/           Test suite (audit-tests.sh)
+├── package.json           npm package config
+├── VERSION                Single source for version string
+└── CLAUDE.md              AI agent instructions for this repo
+```
+
+Skills take precedence over commands when both exist. The installer reads from `gsp/` and writes to each runtime's config directory.
+
+---
+
+## Contributing
+
+Edit source under `gsp/` — never edit inside `.claude/` or other runtime dirs directly. For local development, the installer creates symlinks so changes reflect immediately without reinstalling.
+
+```bash
+# Install locally with symlinks
+node bin/install.js --claude --local
+
+# Test as a plugin
+claude --plugin-dir .
+
+# Run the integrity test suite
+bash dev/scripts/audit-tests.sh
+```
+
+See [CLAUDE.md](CLAUDE.md) for editing rules, key files, and dev tool setup.
+
+---
+
 ## Requirements
 
 - An AI coding tool: [Claude Code](https://claude.ai/claude-code), [OpenCode](https://opencode.ai), [Gemini CLI](https://github.com/google-gemini/gemini-cli), or [Codex CLI](https://github.com/openai/codex)
@@ -326,6 +380,6 @@ MIT License. See [LICENSE](LICENSE) for details.
 
 <div align="center">
 
-**Your code works. GSP makes it yours.**
+**Code is a commodity, your brand is not.**
 
 </div>