@hegemonart/get-design-done 1.57.1 → 1.57.3

package/skills/discover/discover-procedure.md

@@ -1,222 +0,0 @@
----
-name: discover-procedure
-type: meta-rules
-version: 1.0.0
-phase: 28.5
-tags: [discover, procedure, extracted, pipeline-stage, connection-probe, design-context-builder]
-last_updated: 2026-05-18
----
-
-Source: extracted from `skills/discover/SKILL.md` (Phase 28.5 rework - D-10 extract-then-link).
-The skill's essential workflow stays in `../skills/discover/SKILL.md`; this file holds the
-detail the agent reaches for when executing a specific step (state integration, three
-connection probes, design-context-builder + design-context-checker agent prompts, lazy gate
-prompt, auto-mode CSS detection).
-
-# Discover Procedure
-
-Detailed procedure for the get-design-done `discover` Stage 1.5 orchestrator. Companion to
-`../skills/discover/SKILL.md`. Read this file when executing a specific discover step.
-
----
-
-## State Integration
-
-1. Read `.design/STATE.md`.
-   - If missing: create minimal skeleton from `reference/STATE-TEMPLATE.md` with stage=discover, status=in_progress, task_progress=0/1, and log warning: "STATE.md not found - created fresh. If this is a resumed session, run /get-design-done:scan first."
-   - If present and stage==discover and status==in_progress: RESUME - continue existing interview; do not reset.
-   - Otherwise: normal transition - set frontmatter stage=discover, <position> stage=discover, status=in_progress, task_progress=0/1.
-2. **Probe connection availability** - ToolSearch runs FIRST because MCP tools may be in the deferred tool set. This is the canonical probe pattern (spec lives in `connections/connections.md`; copied inline because SKILL.md has no include mechanism - if the probe pattern changes, update all stages that copied it). See §Connection Probes below.
-3. Update last_checkpoint. Write STATE.md.
-
----
-
-## Connection Probes
-
-### A - Figma probe (variant-agnostic)
-
-```
-A1. ToolSearch({ query: "figma get_metadata use_figma", max_results: 10 })
-A2. Parse tool names matching /^mcp__([^_]*figma[^_]*)__(get_metadata|use_figma)$/i
-    into read-capable and write-capable prefix sets.
-A3. Empty read set -> figma: not_configured (skip all Figma paths)
-    One or more matches -> pick prefix via tiebreaker:
-      (1) both-sets > reads-only,
-      (2) `figma` > others,
-      (3) non-`figma-desktop` > desktop,
-      (4) alphabetical.
-A4. Call {prefix}get_metadata:
-      Success -> figma: available (prefix=mcp__<prefix>__, writes=<true|false>)
-      Error   -> figma: unavailable
-```
-
-### B - Refero probe (ToolSearch presence is sufficient - no tool call needed)
-
-```
-B1. ToolSearch({ query: "refero", max_results: 5 })
-B2. Empty result  -> refero: not_configured
-    Non-empty     -> refero: available
-```
-
-### C - Pinterest probe (ToolSearch-only, same pattern as Refero)
-
-```
-C1. ToolSearch({ query: "mcp-pinterest", max_results: 5 })
-C2. Empty result  -> pinterest: not_configured
-    Non-empty     -> pinterest: available
-```
-
-No live `pinterest_search` call at probe time - ToolSearch presence is sufficient. The synthesizer makes the actual search calls.
-
-### D - Lazyweb probe (ToolSearch-only - free, discover Tier 1 per D-01)
-
-```
-D1. ToolSearch({ query: "lazyweb", max_results: 5 })
-D2. Empty result  -> lazyweb: not_configured
-    Non-empty     -> lazyweb: available
-```
-
-### E - Mobbin probe (ToolSearch-only - paid, discover Tier 2 per D-01)
-
-```
-E1. ToolSearch({ query: "mobbin", max_results: 5 })
-E2. Empty result  -> mobbin: not_configured
-    Non-empty     -> mobbin: available
-```
-
-**Reference-source tier order (cost-aware, D-01):** Lazyweb (free, tried first) → Mobbin / Refero (paid, whichever is bound + subscribed) → Pinterest → awesome-design-md → WebFetch.
-
-After all probes (A, B, C, D, E), update `.design/STATE.md` `<connections>` with the results and continue. Downstream stages (design-context-builder) read `<connections>` from STATE.md rather than re-probing.
-
----
-
-## Auto Mode
-
-Auto Mode CSS detection (when `auto_mode: true` is passed to the builder):
-
-  1. If tailwind.config.{js,cjs,mjs,ts} exists -> Tailwind-only project
-     - Skip CSS file grep
-     - Parse tailwind.config for color palette, spacing scale, font families
-     - Use tailwind.config values as the baseline style signal
-  2. Else -> fall through to existing CSS file grep logic
-
----
-
-## Step 1 - Spawn design-context-builder
-
-```
-Task("design-context-builder", """
-<required_reading>
-@.design/STATE.md
-@reference/audit-scoring.md
-@reference/anti-patterns.md
-</required_reading>
-
-You are the design-context-builder agent. Auto-detect existing design system
-state via grep/glob before asking questions. Interview the user ONLY for areas
-where auto-detect returned no confident answer. Write .design/DESIGN-CONTEXT.md.
-
-Baseline audit directory detection (ordered fallback chain):
-  1. If src/ exists -> use src/
-  2. Elif app/ exists -> use app/ (Next.js App Router)
-  3. Elif pages/ exists -> use pages/ (Next.js Pages Router)
-  4. Elif lib/ exists -> use lib/ (library-only projects)
-  5. Else -> flag "layout unknown", skip baseline, note in DESIGN-CONTEXT.md
-
-Common gray areas to probe during discovery (Area 7):
-  1. font-change risk — switching type families when existing UI has body copy in a specific family. Ask: "Is the current body font intentional or inherited? OK to change?"
-  2. token-layer introduction risk — adding CSS custom properties to a codebase that uses direct values. Ask: "Do you want design tokens (--primary, --surface) or inline values (hex, rgb)?"
-  3. Component rebuild vs restyle — when to keep existing component, when to rebuild from scratch. Ask: "For <component>, restyle in place or rebuild?"
-
-Context:
-  auto_mode: <true|false>
-
-Output file: .design/DESIGN-CONTEXT.md
-Emit `## CONTEXT COMPLETE` when done.
-""")
-```
-
-Wait for `## CONTEXT COMPLETE`. Update STATE.md task_progress = 0.5.
-
----
-
-## Step 1.75 - Lazy gate: should design-context-checker run? (Plan 10.1-04, D-21)
-
-Spawn the cheap Haiku gate before the full context-checker:
-
-    Task("design-context-checker-gate", """
-    <required_reading>
-    @.design/STATE.md
-    </required_reading>
-
-    You are the design-context-checker-gate.
-
-    Context:
-      diff_files: <git diff `--name-only` HEAD~1..HEAD>
-      diff_body: (not needed - single-file heuristic)
-      baseline_sha: <HEAD~1>
-
-    Apply the heuristic (DESIGN-CONTEXT.md in diff_files?). Emit JSON + `## GATE COMPLETE`.
-    """)
-
-Wait for `## GATE COMPLETE`. Parse JSON:
-
-- `spawn: false` -> append `lazy_skipped: true` telemetry row for `design-context-checker`, skip Step 2, set STATE.md `<position>` as if checker passed (rationale: DESIGN-CONTEXT.md didn't change, last validation still holds), emit `design-context-checker skipped — <rationale>`.
-- `spawn: true` -> proceed to Step 2 as currently written.
-
-**Note:** On first-run discover, the builder just wrote DESIGN-CONTEXT.md so the gate returns `spawn: true`. The gate meaningfully short-circuits only on re-runs where the builder made no changes.
-
-**Parallel synthesizer note:** discover does not spawn parallel researchers in v1, so `skills/synthesize/` is not wired here. If future variants spawn N parallel interviewers/auto-detectors, wire synthesize between dispatch and collate as in `skills/map/` Step 3.5.
-
----
-
-## Step 2 - Spawn design-context-checker
-
-```
-Task("design-context-checker", """
-<required_reading>
-@.design/STATE.md
-@.design/DESIGN-CONTEXT.md
-</required_reading>
-
-You are the design-context-checker agent. Validate DESIGN-CONTEXT.md across
-6 dimensions. Return APPROVED or BLOCKED with per-dimension verdicts.
-
-Emit `## CONTEXT CHECK COMPLETE` when done.
-""")
-```
-
-Wait for `## CONTEXT CHECK COMPLETE`.
-
----
-
-## Step 3 - Handle checker verdict
-
-If APPROVED: proceed to state update.
-If BLOCKED: present dimensions that BLOCKED to user, offer fix-and-retry loop (re-spawn builder with specific fix instructions). Do not proceed to planning.
-
----
-
-## State Update (exit)
-
-1. Set <position> status=completed, task_progress=1/1.
-2. Set <timestamps> discover_completed_at=<ISO 8601 now>.
-3. Update last_checkpoint. Write STATE.md.
-
----
-
-## After Writing
-
-```
-=== Discovery complete ===
-Saved: .design/DESIGN-CONTEXT.md
-
-Baseline score: [N]/100 ([grade])
-Key issues: [top issue 1], [top issue 2], [top issue 3]
-
-Next: /get-design-done:plan
-  -> Decomposes your context into executable design tasks.
-==========================
-```
-
-Do not proceed to planning automatically unless `--auto` was passed.

package/skills/new-cycle/milestone-completeness-rubric.md

@@ -1,87 +0,0 @@
----
-name: milestone-completeness-rubric
-type: heuristic
-version: 1.0.0
-phase: 28.5
-tags: [milestone, closeout, rubric, completion, turn-closeout, new-cycle, complete-cycle]
-last_updated: 2026-05-18
----
-
-# Milestone Completeness Rubric
-
-What "complete" means at each layer of the gdd lifecycle. Used by `skills/turn-closeout/`,
-`skills/new-cycle/`, `skills/complete-cycle/`, the phase closeout discipline (Plan -12 of
-every phase), and the cycle wrap-up flow. Centralized here so the rubric stays consistent
-across consumers and updates land in one place rather than fanning out across N skills.
-
-## Layers
-
-The lifecycle has four nested layers. A layer is complete only when EVERY criterion at
-that layer is satisfied. Layers above can only flip complete when every layer below has
-flipped complete first - closeout walks bottom-up.
-
-### Task level
-
-The smallest unit of work - one row in a PLAN.md `<tasks>` list.
-
-- Verify command runs with exit 0 (the `<verify>` block's command).
-- The `<done>` criterion is observable (the file exists, the test passes, the output
-  matches the contract).
-- If the task is `tdd="true"`: tests pass after the GREEN step; tests fail before it.
-- File diff is scoped to the declared `files_modified` only - no collateral damage.
-- A single commit per task in conventional form `{type}({phase}-{plan}): {description}`.
-- Deviations (Rules 1, 2, 3) tracked for the SUMMARY.md "Deviations" section.
-
-### Plan level
-
-A self-contained chunk of work - one `XX-YY-PLAN.md`.
-
-- All tasks complete (per task level above).
-- Plan-level validator passes (e.g. `validate-skill-length.cjs` for Phase 28.5 buckets;
-  `validate-frontmatter.ts` for agent-frontmatter plans).
-- SUMMARY.md written at `.planning/phases/XX-name/XX-YY-SUMMARY.md` with the canonical
-  shape: deviations, files-modified table, commits, verification result, decisions.
-- No collateral damage outside the plan's declared `files_modified` list - out-of-scope
-  edits are forbidden (executor Rule 5 boundary).
-- A final docs commit aggregates `SUMMARY.md`, `STATE.md`, `ROADMAP.md`, and
-  `REQUIREMENTS.md` updates.
-
-### Phase level
-
-A coherent batch of plans - one `XX-name/` directory under `.planning/phases/`.
-
-- All plans complete (per plan level above).
-- Phase-level verification ALL pass (`<verification>` block in each PLAN.md).
-- ROADMAP.md flipped `[ ]` → `[x]` for all plans in this phase (rule #14: scoped flip
-  only - never flip plans outside this phase).
-- Phase SUMMARY ladder coherent - each `XX-YY-SUMMARY.md` exists and reads top-to-bottom
-  as a single story.
-- All decisions surfaced through the SUMMARY frontmatter and rolled up into STATE.md's
-  `<decisions>` block.
-
-### Cycle level
-
-A shipping milestone - typically one minor version bump in the gdd project.
-
-- All phases for the cycle's target version complete (per phase level above).
-- 4 manifests version-aligned: `plugin.json`, `marketplace.json`, `package.json`, and
-  the phase-20 manifests-version baseline (`test-fixture/baselines/phase-XX/manifests-version.txt`).
-- CHANGELOG.md entry written for the new version with one block per phase.
-- Off-cadence registration if applicable - `tests/semver-compare.test.cjs` adds
-  `OFF_CADENCE_VERSIONS.add('<version>')` for `.5`/`.6`/`.7` insertion-style versions.
-- Regression baseline at `test-fixture/baselines/phase-XX/` exists and the
-  `tests/phase-XX-baseline.test.cjs` suite passes (version-agnostic - reads
-  `package.json#version`).
-- NOTICE attribution updated if any third-party content was adopted in this cycle.
-- Closeout plan's scoped ROADMAP flip touches only this cycle's checkboxes (precedent:
-  Phase 28 closeout flipped exactly 7 inline + 1 overview entry).
-
-## Cross-references
-
-- `./STATE-TEMPLATE.md` - STATE.md schema; closeout updates the `<position>` block's
-  `last_checkpoint` field.
-- `../skills/turn-closeout/SKILL.md` - consumer at the turn boundary (within a stage).
-- `../skills/new-cycle/SKILL.md` - consumer at cycle ingress.
-- `../skills/complete-cycle/SKILL.md` - consumer at cycle egress.
-- `../skills/quality-gate/SKILL.md` - Stage 4.5 gate that gates the plan-level "verify
-  command runs with exit 0" criterion when project tooling exists.

package/skills/scan/SKILL.md

@@ -1,92 +0,0 @@
----
-name: scan
-description: "Pre-pipeline initializer that maps an existing repo's design system (colors, typography, spacing, components, tokens), runs the anti-pattern audit, scores the 7 weighted categories, and writes DESIGN.md + .design/DESIGN-DEBT.md. Use when starting work in any new or existing repo before /gdd:discover. Activates for requests involving a fast read-only anti-pattern sweep, a quick design lint, or spotting slop without a full audit."
-argument-hint: "[--quick] [--full]"
-user-invocable: true
----
-
-# Get Design Done - Scan
-
-**Pre-pipeline initializer.** Run once in any new or existing repo before starting the Discover -> Plan -> Design -> Verify pipeline.
-
-Full procedure detail: `./scan-procedure.md`.
-
-Produces:
-- `DESIGN.md` - snapshot of the existing design system as it actually is
-- `.design/DESIGN-DEBT.md` - prioritized debt roadmap
-
-`--quick`: Skip component inventory, focus on tokens + anti-patterns only (~2 min)
-`--full`: Include component-by-component analysis (slower, more thorough)
-
-Default: full scan of tokens, patterns, and anti-patterns. Component inventory is a summary count, not per-file.
-
----
-
-## State Integration
-
-At scan entry, before running any step:
-
-1. Read or create `.design/STATE.md` from `reference/STATE-TEMPLATE.md` (set `stage=scan`, `status=in_progress`, `task_progress=0/8`; preserve `started_at` on resume). See `./scan-procedure.md` §State Integration for the full read/create/resume decision tree.
-2. Probe Figma + Refero connections (variant-agnostic ToolSearch + tiebreaker resolution). Detail: `./scan-procedure.md` §Probe connection availability.
-3. Run the four Phase 8 probes (preview, storybook, chromatic, graphify) and batch-write results to STATE.md `<connections>`. Detail: `./scan-procedure.md` §Phase 8 Connection Probes.
-4. Emit the first-run connection nudge if every probe returned `not_configured` AND `.design/config.json > connections_onboarding` is absent.
-5. Update `last_checkpoint`; persist STATE.md before proceeding to Step 1.
-
----
-
-## Workflow
-
-The scan executes eight steps in order. Each step's full grep commands, analysis prompts, and decision rules live in `./scan-procedure.md` - keep that file open while executing.
-
-### Step 1 - Orient
-
-Detect framework, CSS approach, component count, style file count, token system. Detect source root by ordered fallback (`src/` -> `app/` -> `pages/` -> `lib/`) and substitute into subsequent grep commands. Log the detected source root in DESIGN.md frontmatter. Detail: `./scan-procedure.md` §Step 1.
-
-### Step 2 - Extract Color System
-
-Grep hex / `oklch()` / `hsl()` / `rgb()` colors, CSS custom properties, and Tailwind color config. Analyze palette size, token discipline, AI-slop colors (#6366f1, #8b5cf6, #06b6d4), semantic naming, dark-mode purity. Produce a color inventory table. Detail: `./scan-procedure.md` §Step 2.
-
-### Step 2A - Figma Token Augmentation
-
-If `figma: available` in STATE.md `<connections>`: call `{prefix}get_variable_defs`, translate variables by type/name pattern, merge with grep-derived tokens (never replace). Skip silently if `figma` is `not_configured` or `unavailable`. Detail: `./scan-procedure.md` §Step 2A.
-
-### Step 3 - Extract Typography System
-
-Grep font families, sizes, weights, line-heights. Analyze family count, scale compliance, weight hierarchy, line-height on body, reflex-font signals. Read `${CLAUDE_PLUGIN_ROOT}/reference/typography.md` for comparison criteria. Detail: `./scan-procedure.md` §Step 3.
-
-### Step 4 - Extract Spacing System
-
-Grep CSS spacing values, Tailwind spacing overrides, space tokens. Score grid compliance against the 4/8/12/16/24/32/48/64 series. Detail: `./scan-procedure.md` §Step 4.
-
-### Step 5 - Anti-Pattern Audit
-
-Read `${CLAUDE_PLUGIN_ROOT}/reference/anti-patterns.md`. Run all BAN-XX and SLOP-XX grep commands, plus a11y checks (focus rings, reduced-motion, div onClick, small fonts). Detail: `./scan-procedure.md` §Step 5.
-
-### Step 6 - Component Inventory
-
-If `--quick`, skip. Otherwise run the three-pass multi-signal filter (JSX-return + className + framework-import) to produce an authoritative component list, then enumerate primitives. In `--full` mode, emit one row per file. Detail: `./scan-procedure.md` §Step 6.
-
-### Step 7 - Score All 7 Categories
-
-Read `${CLAUDE_PLUGIN_ROOT}/reference/audit-scoring.md`. Score each category 0–10 and apply the weighted formula `(A11Y * 0.25) + (Visual Hierarchy * 0.20) + (Typography * 0.15) + (Color * 0.15) + (Layout * 0.10) + (Anti-Patterns * 0.10) + (Motion * 0.05)`. Grade A=90+, B=75+, C=60+, D=45+, F<45.
-
-### Step 8 - Generate Design Debt Roadmap
-
-Classify each finding P0/P1/P2/P3, estimate effort XS/S/M/L/XL, group by debt theme, compute `priority_score = (severity_weight * effort_weight) + (dependency_depth * 2)`. Mark P1+XS/S items as quick wins. Detail: `./scan-procedure.md` §Step 8.
-
----
-
-## Outputs
-
-Write both artifacts using the templates in `./scan-procedure.md`:
-
-- **`DESIGN.md`** (project root) - design-system snapshot with score table, color/typography/spacing/component inventories, anti-pattern status, motion summary. Frontmatter records `score`, `framework`, `css_approach`, `token_layer`, and (if Figma ran) `figma_variables_used` + `figma_source`. Template: `./scan-procedure.md` §Output 1.
-- **`.design/DESIGN-DEBT.md`** - prioritized debt roadmap grouped P0/P1/P2/P3, with priority_score ordering, recommended fix order, and pipeline recommendation. Template: `./scan-procedure.md` §Output 2.
-
----
-
-## After Writing
-
-Print the user-facing summary block from `./scan-procedure.md` §After Writing - project name, score, P0/P1 counts, quick-win count, artifact paths, and next-step options (start pipeline, fix quick wins first, or just reference the debt).
-
-## SCAN COMPLETE