get-shit-pretty 0.6.3 → 0.7.0

package/gsp/skills/{gsp-video/SKILL.md → gsp-visuals/domains/video.md}

@@ -1,59 +1,24 @@
----
-name: gsp-video
-description: Define video & motion graphics direction — editing style, pacing, transitions, brand motion language
-user-invocable: true
-model: sonnet
-allowed-tools:
-  - Read
-  - Write
-  - AskUserQuestion
-  - Glob
-  - Grep
-  - WebSearch
----
-<context>
-You are a GSP video director. You define the brand's video and motion graphics language — editing style, pacing, transitions, title cards, and how movement expresses brand personality.
+# Video Domain
 
-This is a standalone composable skill. It works two ways:
-1. **Standalone** — user runs `/gsp-video` directly for video direction
-2. **As a building block** — invoked during identity or project phases when the brand needs video content direction
+**Output filename:** `video-direction.md`
 
-Video is increasingly essential — product demos, hero backgrounds, social content, onboarding flows. A consistent video language prevents every piece from feeling like a different brand.
-</context>
+## Role
 
-<objective>
-Define video and motion graphics direction for a brand or project.
+You are a GSP video director. You define the brand's video and motion graphics language — editing style, pacing, transitions, title cards, and how movement expresses brand personality.
 
-**Input:** Brand context or user description, OR `--enrich` mode
-**Output:** `video-direction.md` chunk with editing style, pacing, transitions, and motion graphics specs
-**Agent:** None — inline skill with structured questioning
-</objective>
+Video is increasingly essential — product demos, hero backgrounds, social content, onboarding flows. A consistent video language prevents every piece from feeling like a different brand.
 
-<execution_context>
-@${CLAUDE_SKILL_DIR}/../../references/chunk-format.md
-</execution_context>
+## Rules
 
-<rules>
-- Always use `AskUserQuestion` for user interaction — never prompt via plain text
-- One decision per question — never batch multiple questions in a single message
 - Video direction must align with brand intensity dials — a variance:2 brand gets calm, steady video; variance:8 gets dynamic cuts
 - Motion graphics must use the brand's color palette and typography
 - Specify concrete parameters (duration ranges, easing curves, fps) not vague adjectives
-</rules>
 
-<process>
-## Step 0: Determine mode
-
-| Input | Mode |
-|-------|------|
-| `/gsp-video --enrich` | Enrich existing video direction |
-| `/gsp-video` | Interactive — define video language |
-
-## Step 1: Enrich mode (`--enrich`)
+## Enrich mode (`--enrich`)
 
 Read existing brand context (`.yml` intensity dials, color palette, typography). Derive video direction that's coherent with the brand's visual language.
 
-## Step 2: Interactive mode
+## Interactive mode
 
 One `AskUserQuestion` at a time:
 
@@ -70,7 +35,7 @@ One `AskUserQuestion` at a time:
    - **Dynamic & energetic** — "fast cuts, match cuts, high energy"
    - **Cinematic & dramatic** — "slow motion, depth of field, orchestrated"
 
-## Step 3: Define video direction
+## Direction framework
 
 ### Editing Style
 - **Pacing:** cut frequency (e.g., "3-5 second holds, cut on action")
@@ -95,7 +60,48 @@ One `AskUserQuestion` at a time:
 - 3-5 principles (e.g., "Movement always has purpose", "Transitions serve the narrative, not decoration")
 - **Anti-patterns:** what to avoid (e.g., "no star wipes", "no text on busy backgrounds without contrast overlay")
 
-## Step 4: Write output + completion
+## Output structure (target: 80-120 lines)
+
+```markdown
+# Video Direction
+
+> Phase: identity | Brand: {name} | Generated: {DATE}
+
+---
+
+## Editing Style
+{pacing, transitions, camera movement, color grading}
+
+## Motion Graphics
+{typography animation, timing, easing, color, style}
+
+## Title Cards & Lower Thirds
+{layout, typography, background, animation}
+
+## Brand Motion Principles
+{3-5 principles + anti-patterns}
+
+---
+
+## Related
+- [imagery-style.md](./imagery-style.md)
+- [STYLE.md](../patterns/STYLE.md)
+```
+
+## Completion display
+
+```
+  /gsp-visuals --video — video direction defined
+
+    editing        {style} — {pacing}
+    motion gfx     {style} — {easing}
+    titles         {treatment}
+    principles     {count} defined
+```
+
+## Completion options
 
-Write `video-direction.md` chunk. Target: 80-120 lines.
-</process>
+Use `AskUserQuestion`:
+- **Continue to identity** — proceed with `/gsp-brand-identity`
+- **Refine** — adjust a specific area
+- **Done** — that's all

package/gsp/templates/branding/config.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.3",
+  "version": "0.7.0",
   "project_type": "brand",
   "brand": {
     "name": "",

package/gsp/templates/phases/brief.md

@@ -22,7 +22,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`. Below is the structural reference for what each chunk should contain:
+Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
 
 ### scope.md
 - **Screen list:** prioritized list of screens to design and build

package/gsp/templates/phases/critique.md

@@ -28,7 +28,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`. Below is the structural reference for what each chunk should contain:
+Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
 
 ### critique.md
 - **Heuristics evaluation:** 10 heuristics table (Heuristic, Score 1-5, Notes)

package/gsp/templates/phases/design.md

@@ -38,7 +38,7 @@ Self-contained HTML wireframe preview:
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`. Below is the structural reference for what each chunk should contain:
+Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
 
 ### screen-{NN}-{name}.md
 - **Purpose:** what this screen does

package/gsp/templates/phases/discover.md

@@ -23,7 +23,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`.
+Each chunk follows the standard chunk format.
 
 ### market-landscape.md
 - Industry overview and trajectory

package/gsp/templates/phases/identity.md

@@ -31,7 +31,7 @@ Also produces `palettes.json` — machine-readable OKLCH color scales.
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`.
+Each chunk follows the standard chunk format.
 
 ### logo-directions.md
 - 3 directions each with:

package/gsp/templates/phases/launch.md

@@ -20,7 +20,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`. Below is the structural reference for what each chunk should contain:
+Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
 
 ### campaign-strategy.md
 - **Objective:** campaign goal

package/gsp/templates/phases/patterns.md

@@ -42,7 +42,7 @@ If no UI library is detected, write up to 15 core component specs.
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`.
+Each chunk follows the standard chunk format.
 
 ### {brand-name}.yml
 

package/gsp/templates/phases/research.md

@@ -24,7 +24,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`. Below is the structural reference for what each chunk should contain:
+Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
 
 ### ux-patterns.md
 - **Product type patterns:** established UX patterns for this category (e.g., dashboard, e-commerce, social, SaaS)

package/gsp/templates/phases/review.md

@@ -19,7 +19,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`. Below is the structural reference for what each chunk should contain:
+Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
 
 ### acceptance-report.md
 - **Overall verdict:** Pass / Conditional Pass / Fail

package/gsp/templates/phases/strategy.md

@@ -27,7 +27,7 @@
 
 ## Content Reference
 
-Each chunk follows the format in `references/chunk-format.md`.
+Each chunk follows the standard chunk format.
 
 ### positioning.md
 - Positioning statement: For {audience} who {need}, {brand} is the {category} that {benefit} because {reason}

package/gsp/templates/projects/config.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.3",
+  "version": "0.7.0",
   "project_type": "design",
   "project": {
     "name": "",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-pretty",
-  "version": "0.6.3",
+  "version": "0.7.0",
   "description": "Design engineering system for AI coding agents. Brand identity + design projects, from strategy to code.",
   "bin": {
     "get-shit-pretty": "bin/install.js"

package/gsp/references/phase-transitions.md

@@ -1,132 +0,0 @@
-# Phase Transition Screen
-
-Rendered at the end of every phase skill. Confirms what was accomplished, shows output artifacts, and routes the user forward.
-
-## When to render
-
-Every skill that completes a phase must render a transition. The skill itself just says:
-
-```
-Render phase transition (see `references/phase-transitions.md`).
-```
-
-This reference handles all the logic — skills should NOT hardcode pipeline layouts.
-
-## Styling
-
-Output as plain text using Unicode characters for visual hierarchy:
-
-- `◆` for completed phases
-- `◈` for next phase (the one the user is about to enter)
-- `◇` for pending phases
-- `───` connecting phases in the pipeline line
-- `──────` divider between sections
-- Tree connectors `├──`, `└──`, `│` for file listings
-
-## Rendering logic
-
-Read the brand or project STATE.md to determine context.
-
-### Step 1: Pipeline progress line (conditional)
-
-Show the pipeline line **only when 2+ phases are complete** (i.e., the user is clearly in a flow). If this is the first phase completed, skip the pipeline line — the user may have invoked the skill standalone.
-
-```
-  {brand-or-project-name}
-  ◆ discover ─── ◆ strategy ─── ◈ identity ─── ◇ system
-```
-
-#### Branding phases
-
-`discover ─── strategy ─── identity ─── patterns`
-
-If audit phase exists (evolve mode), prepend: `audit ─── `
-
-#### Project phases
-
-`brief ─── research ─── design ─── critique ─── build ─── review`
-
-If launch is in scope, append: ` ─── launch`
-
-### Step 2: Phase completion + file tree (always)
-
-Always show what was accomplished and what was produced:
-
-```
-  ◆ {phase} complete — {completion_message}
-
-    {phase_dir}/
-    ├── {file1}.md
-    ├── {file2}.md
-    └── INDEX.md
-
-  ──────────────────────────────
-```
-
-### Step 3: Routing options (adaptive)
-
-Use `AskUserQuestion` with options adapted to context:
-
-**When in a pipeline flow** (previous phase was completed in this or a recent session):
-1. **Continue to {next}** — "{description of next phase}"
-2. **View progress** — "see the full dashboard"
-3. **Done for now** — "pick up later with /gsp-start"
-
-**When standalone** (user invoked the skill directly, no clear pipeline context):
-1. **View output** — "review what was generated"
-2. **Done** — "that's all I needed"
-
-Use judgment — if the user explicitly asked for one skill, don't push them into the next phase. If they're clearly flowing through the pipeline, offer the next step.
-
-## Completion Messages
-
-### Branding Phases
-
-| Phase | Completion Message | Next Phase |
-|-------|-------------------|------------|
-| audit | brand assessed | discover — `/gsp-brand-research` |
-| discover | market landscape mapped | strategy — `/gsp-brand-strategy` |
-| strategy | brand platform defined | identity — `/gsp-brand-identity` |
-| identity | visual system designed | patterns — `/gsp-brand-guidelines` |
-| patterns | design system built | project setup — `/gsp-start` (scans codebase, gathers brief, creates project) |
-
-### Project Phases
-
-| Phase | Completion Message | Next Phase |
-|-------|-------------------|------------|
-| brief | project scoped | research — `/gsp-project-research` |
-| research | patterns and approaches researched | design — `/gsp-project-design` |
-| design | screens designed | critique — `/gsp-project-critique` |
-| critique | designs critiqued | build — `/gsp-project-build` |
-| build | code implemented | review — `/gsp-project-review` |
-| review | implementation validated | launch — `/gsp-launch` (or done) |
-| launch | campaign assets created | done |
-
-### Special cases
-
-**Critique with critical issues:**
-```
-  ◈ critique — critical issues found, revising designs
-
-  ──────────────────────────────
-```
-Options: Revise designs / Override and continue / View issues
-
-**Review with QA failures:**
-```
-  ◈ review — QA found issues, needs revision
-
-  ──────────────────────────────
-```
-Options: Fix and rebuild / View issues / Done for now
-
-**Final phase (all complete):**
-Add `  fully pretty.` after the divider.
-
-## File Tree Rules
-
-- Root is the phase directory name followed by `/`
-- Files sorted alphabetically, directories first
-- INDEX.md always listed last
-- Use `├──` for all items except the last, which uses `└──`
-- Subdirectories show their contents with `│` continuation

package/gsp/references/style-preset-schema.md

@@ -1,63 +0,0 @@
-# Style Preset YAML Schema
-
-Template for brand-derived style preset files (`{brand-name}.yml`). All values must trace to foundation chunks.
-
-```yaml
-name: {brand-slug}
-description: {one-line brand aesthetic summary}
-tags: [5-8 fuzzy-match tags for style discovery]
-source: brand  # marks this as brand-derived, not a GSP preset
-
-tokens:
-  color:
-    primary: "{hex}"        # from foundations/color-system.md
-    secondary: "{hex}"
-    accent: "{hex}"
-    background: "{hex}"
-    surface: "{hex}"
-    on-primary: "{hex}"
-    on-background: "{hex}"
-    error: "{hex}"
-    success: "{hex}"
-    warning: "{hex}"
-    info: "{hex}"
-
-  typography:
-    font-family-primary: "{font stack}"  # from foundations/typography.md
-    font-family-mono: "{font stack}"
-    font-weight-heading: {number}
-    font-weight-body: {number}
-    font-size-base: "{px}"
-    line-height-base: {number}
-
-  shape:
-    border-radius-sm: "{px}"  # from foundations/border-radius.md
-    border-radius-md: "{px}"
-    border-radius-lg: "{px}"
-    border-width: "{px}"
-    border-color: "{hex}"
-
-  elevation:
-    shadow-sm: "{value}"  # from foundations/elevation.md
-    shadow-md: "{value}"
-    shadow-lg: "{value}"
-    shadow-xl: "{value}"
-
-  spacing:
-    base: {number}  # from foundations/spacing.md
-    scale: [{values}]
-
-  motion:
-    duration-fast: "{ms}"
-    duration-normal: "{ms}"
-    easing: "{value}"
-
-dark_mode:
-  color:
-    background: "{hex}"
-    surface: "{hex}"
-    on-background: "{hex}"
-
-compatibility: []  # leave empty for brand styles
-clashes: []
-```