Strengthen UX prototype reuse and coverage checks

ux-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ux-design
-version: 0.3.0
+version: 0.4.0
 description: >-
   UX design workflow that supports early research and exploratory prototyping
   from a Jira Feature or published PRD, then enriches the same context from its

ux-design/skills/prototype.md

@@ -68,8 +68,17 @@ into the UX Design namespace.
 Using `01-discovery.md` and `02-research.md` when present, propose one or two
 design directions. For each, identify the user needs it prioritizes, the core
 interaction pattern, its tradeoffs, and how it compares with patterns from
-discovery. Present the directions and wait for the researcher to choose or
-suggest another.
+discovery. When the feature modifies existing UI (workspace mode), also
+prepare concrete source examples for affected areas — navigation, page
+scaffolding, table/list layouts, filter controls, action menus, inline
+editors, modal patterns as applicable. For each, record the source file
+reference and classify as **reuse** (keep) or **depart** (change, with
+rationale). Present the directions and this reuse organization together;
+wait for the researcher to choose or suggest changes. After selection, persist
+that direction's examples in **Source Example Baseline** in
+`prototype-notes.md` — conformance baseline; preserve on regen/refinement,
+update on human-approved direction change.
+Standalone: "No source baseline — {reason}".
 
 Settle the create skill's onboarding answers with the researcher:
 
@@ -141,6 +150,11 @@ Record the chosen strategy and rationale in `prototype-notes.md`.
 
 ### Step 2: Generate the Prototype
 
+Before invoking the create skill, populate the **User Stories Covered**
+table in `prototype-notes.md` with the planned mapping (status `planned`
+for every row). Derive rows from discovery goals, PRD requirements, or
+confirmed decisions; a linked `[UX]` story is not required.
+
 When invoking the create skill with a workspace (local or Git URL), supply
 the expected discovery baseline SHA as task context alongside the source and
 flags — not as a CLI flag, but as an explicit constraint in the invocation
@@ -304,6 +318,19 @@ complete prototype must have:
   served or opened, record the verification as **unverified** with the
   reason rather than claiming completion. Copied unchanged app scaffolding
   alone is not proof that the requested prototype content exists.
+- **Source-conformance check (workspace mode):** Compare rendered prototype
+  against saved **Source Example Baseline** in `prototype-notes.md`; outcome
+  starts `unverified`, write `matched`/`mismatch`/`limited` + Evidence per
+  entry. Approved departures can match; unavailable → `limited`+reason.
+  Never inherit passes or silently rebaseline mismatches; refresh each
+  generation/revision. Step 4 preserves results.
+- **Coverage update:** Update every **User Stories Covered** row. `verified`
+  requires browser-observed match without stand-in data/interactions.
+  Otherwise-complete flows using stand-ins are `mocked` even if behavior
+  matches — record checks+limits in Evidence (no production claim);
+  `partial`/`deferred`(researcher-approved)/`missing` for gaps/scope
+  (disclose mocks too). Surface core gaps at existing gate; never silently
+  complete or drop scope; recheck previous rows each revision.
 
 Do not diagnose completion or failure from the presence or absence of a
 directory alone. Check for the actual agreed output artifacts.
@@ -415,11 +442,22 @@ Do not invent research evidence.
 |----------|-----------|-------------------|
 | {what} | {why} | {finding or researcher direction} |
 
+## Source Example Baseline
+
+| Area | Source Reference | Classification | Rationale | Outcome | Evidence |
+|------|-----------------|----------------|-----------|---------|----------|
+| {area} | {frontend-relative path} | {reuse/depart} | {why} | {unverified/matched/mismatch/limited} | {observation or reason} |
+
+{Metadata: Step 1, preserve on regen/refinement. Outcome/Evidence: Step 3.
+Standalone: "No source baseline"}
+
 ## User Stories Covered
 
-| Story | Acceptance Criteria | Status |
-|-------|-------------------|--------|
-| {story} | {criteria} | {covered / partial / deferred} |
+| Requirement / Decision | Screen / Control | State / Action | Status | Evidence / Reason |
+|------------------------|------------------|----------------|--------|-------------------|
+| {source requirement or confirmed decision} | {screen/control} | {state/action} | {planned/verified/mocked/partial/deferred/missing} | {evidence, mock limits, or reason} |
+
+{See Steps 2–3 for lifecycle.}
 
 ## Page Context