@sun-asterisk/sungen 2.7.0-beta.1 → 3.0.0-beta.72

package/src/orchestrator/templates/ai-instructions/claude-cmd-create-test.md

@@ -9,7 +9,7 @@ allowed-tools: Read, Grep, Bash, Glob, Write, AskUserQuestion, Skill, mcp__playw
 
 If `spec_figma.md` exists OR the user provides a Figma URL for the PAT flow:
 - Do NOT call any `mcp__figma__*` tool. The PAT flow uses the `sungen` CLI, not MCP.
-- Run `sungen add --screen <screen> --figma '<url>'` via Bash (**single-quote the URL**) then invoke `sungen-figma-source` skill.
+- Run `sungen add --screen <screen> --figma '<url>'` via Bash (**single-quote the URL**) then invoke the `sungen-capture` skill (**mode figma-pat**).
 
 ---
 
@@ -17,6 +17,8 @@ If `spec_figma.md` exists OR the user provides a Figma URL for the PAT flow:
 
 You are a **Senior QA Engineer** specialized in test case design. You structure test cases by viewpoint categories and translate UI into Gherkin test cases following `sungen-gherkin-syntax` and `sungen-tc-generation` skills. **Tier 1 (critical+high) first** — expand coverage later. Focus on **Gherkin scenarios and test data only** — selectors are handled during `/sungen:run-test`.
 
+**Quality is built in, not a second command.** After generating, you run a **harness loop**: `sungen audit` measures the output (viewpoint gate, assertion depth, balance, duplicates, traceability) and you **repair the findings** until critical viewpoints are covered — the user does not need to ask for this. Auto-load the `sungen-harness-audit` skill for how to read the report and map each finding to a repair. (`/sungen:design` is an **alias** of this command.)
+
 ## Parameters
 
 Parse **name** from `$ARGUMENTS`. If missing, ask the user.
@@ -46,38 +48,60 @@ Parse **name** from `$ARGUMENTS`. If missing, ask the user.
      - **Fill test-viewpoint.md first** — I'll help you identify edge cases, known issues, and design decisions for this screen before generating tests
      - **Continue without it** — generate tests from spec and other sources only
 
+   **Context discovery (prefer an isolated agent).** Reading all sources here can flood this context. **Claude Code:** spawn the **`sungen-discovery`** sub-agent (Task tool, `subagent_type: sungen-discovery`) to read spec/figma/ui/live in isolation and return a **compact discovery report** (sources, completeness, conflicts, recommended route, key facts); use that report instead of pasting raw sources. **Copilot / no sub-agents:** do the reading inline as below.
+
    **Auto-detect visual source** — do NOT ask the user to pick a source. Instead, check what already exists and use it:
    1. If `spec_figma.md` exists → read it as Figma supplement (PAT flow already completed during `add-screen`). Do NOT call any `mcp__figma__*` tool.
    2. If `ui/` has images (`.png`, `.jpg`, etc.) → read them for visual context (layout, element positions, states).
-   3. If neither exists → use `AskUserQuestion` to ask: *"No visual source found. Pick one:"*
-      - **Figma PAT** — ask for URL, run `sungen add --screen <screen> --figma '<url>'` via Bash, then invoke `sungen-figma-source` skill
-      - **Figma MCP** — invoke `sungen-capture-figma` skill
-      - **Live page scan** — invoke `sungen-capture-live` skill
+   3. If neither exists → use `AskUserQuestion` to ask: *"No visual source found. Pick one:"* — then invoke the **`sungen-capture`** skill with the matching **mode** (read only that mode's file):
+      - **Figma PAT** — ask for URL, run `sungen add --screen <screen> --figma '<url>'` via Bash, then `sungen-capture` **mode figma-pat**
+      - **Figma MCP** — `sungen-capture` **mode figma-mcp**
+      - **Live page scan** — `sungen-capture` **mode live**
       - **Skip** — generate from spec.md only
 
+   (When `spec_figma.md` exists, that is also `sungen-capture` **mode figma-pat**; when `ui/` images exist, that is **mode local**.)
+
    **Cross-check**: if both `spec.md` and visual sources exist, flag any discrepancies (missing fields, different labels) before moving on. When `spec_figma.md` is present, follow the Figma supplement rules in `sungen-tc-generation` skill (reading order, Text Inventory, conflict handling).
 
    Summarize what you found in requirements and present to the user.
 
-4. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. **For flows**, use the "Flow Test Generation" section in the skill. When requirements exist, use the "Requirements-Driven Generation" strategy. **For Tier 1**, apply the **Lightweight Guard** — verify required fields, validation rules, business rules, security checks, and key state transitions all have TCs after generation. **For Tier 2+**, **MUST** apply the full **Mapping Contract** — walk every `spec.md` section top-to-bottom and produce the indicated TCs per Table 1; handle `test-viewpoint.md` per Table 2. Do not silently skip sections.
+4. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. **Viewpoint loading discipline:** `sungen-viewpoint` is a **router** — from the page-type (form / list / detail / auth / dashboard …) read **only the matching group file(s)** (e.g. a login screen → group-e-identity; a product list → group-c-data-explore), never all five groups. This keeps the generation context lean. **For flows**, use the "Flow Test Generation" section in the skill. When requirements exist, use the "Requirements-Driven Generation" strategy. **For Tier 1**, apply the **Lightweight Guard** — verify required fields, validation rules, business rules, security checks, and key state transitions all have TCs after generation. **For Tier 2+**, **MUST** apply the full **Mapping Contract** — walk every `spec.md` section top-to-bottom and produce the indicated TCs per Table 1; handle `test-viewpoint.md` per Table 2. Do not silently skip sections.
 5. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills. **For flows**: use `[Screen:Element]` namespace format, namespace test-data by phase, add `@flow` tag.
-6. Show summary, then use `AskUserQuestion` to offer next steps based on which tier was just generated:
+
+5.5. **Quality gate & repair (harness — always run, do NOT skip).** Follow the `sungen-harness-audit` skill:
+   - Run `sungen audit --screen <name>` (Bash) and read `gateStatus` + `findings` (deterministic, structural).
+   - **Independent semantic review.** **Claude Code:** spawn the **`sungen-reviewer`** sub-agent (Task tool, `subagent_type: sungen-reviewer`) — it judges what the gate can't (does each scenario's steps PROVE its title/viewpoint, observable Thens, business-critical assertion depth) and returns `VERDICT` + `ISSUES` with concrete fixes. **Merge its NEEDS-REPAIR issues with the audit findings.** (Copilot / no sub-agents: run the same review inline using the `sungen-reviewer` criteria.)
+   - Repair **both** the audit findings and the reviewer issues (budget 3 rounds), then re-audit:
+   - If the gate FAILs or there are findings, **repair** (budget 3 rounds), then re-audit:
+     - **GATE** missing critical theme → generate scenarios for it. If it is **cross-screen** (cart-correctness, product-detail-consistency, filter-result-correctness): write the scenario with **observable data assertions** (`... with {{value}}`, `table ... with {{value}}`), tag it `@manual`, and add a comment `# Deferred to a flow (<screen> -> <target>) for automation`. Do **not** fake a shallow single-screen pass.
+     - **DEPTH** → replace `see [X] page/section` on business-critical scenarios with data assertions.
+     - **BALANCE** → stop expanding secondary viewpoints; add business-core scenarios first.
+     - **TRACE** → align `VP-` ids with the viewpoint-overview.
+   - Stop when the gate PASSes and findings clear, **or** the budget is exhausted → report residual gaps honestly (never fake a pass).
+
+5.6. **Record (reuse + observability).** Build the manifest and report usage:
+   - `sungen manifest --screen <name>` — fingerprints for next-run change detection. On a **re-run**, start the whole command by `sungen manifest --screen <name> --diff` and only regenerate scenarios whose spec section changed (keep/regenerate/retire).
+   - **Ledger each phase** (so `sungen trace` can map the whole process): pick one `runId` at the start (e.g. a timestamp) and append `sungen ledger record --screen <name> --run <runId> --step <discovery|viewpoint|gherkin|audit|repair:N> --ms <elapsed>` (add `--tokens-in/--tokens-out` if known). The `--run` id groups this invocation so `trace`/`ledger report` show THIS run, not a mix of past runs. Do this for **every** phase, not just repair.
+
+6. **Converge — show the trace.** Run `sungen trace --screen <name>` and present to the user: the process map (phases + repair rounds), bottlenecks, and the **HUMAN-LOOP FOCUS** (@manual scenarios they must verify) + audit score & gate status & residual/cross-screen gaps. Then use `AskUserQuestion` to offer next steps based on which tier was just generated:
+
+   > The harness gate + reviewer already ran above — you do **not** need `/sungen:review` as a next step (it's the independent checkpoint for hand/prompt-authored or pre-delivery cases). Recommend `run-test` or expanding coverage.
+
+   **Optional — exploration mode (Loop 2).** The suite above is the deterministic, official output. If the user wants to push past "the machine always gives the same thing", offer to run the **challenge pass**: `sungen challenge --screen <name>` (deterministic structural critics) then the **`sungen-challenge` agent** (Task tool, `subagent_type: sungen-challenge`) for semantic + novelty candidates. It is **advisory** — surfaces blind spots + ≤20% novelty candidates, never auto-merges. When the user confirms a recurring miss, record it with `sungen blindspot add` so future runs don't repeat it.
 
    **After Tier 1 generation:**
-   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
-   - **`/sungen:run-test <name>`** — Skip review, generate selectors and run tests now
+   - **`/sungen:run-test <name>`** — Generate selectors and run tests now (Recommended)
    - **`/sungen:create-test <name>`** — Expand coverage: add @normal + @low scenarios (Tier 2)
    - **Done for now** — I'll come back later
 
    **After Tier 2 generation:**
    - **`/sungen:create-test <name>`** — Deep coverage: add BVA combos, cross-field validation, negative inputs, race conditions (Tier 3) (Recommended)
-   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality
    - **`/sungen:run-test <name>`** — Generate selectors and run tests now
    - **Done for now** — I'll come back later
 
    **After Tier 3 or Full generation:**
-   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
-   - **`/sungen:run-test <name>`** — Generate selectors and run tests now
+   - **`/sungen:run-test <name>`** — Generate selectors and run tests now (Recommended)
+   - **`/sungen:create-test <name>`** — Add more sections if the screen changed
    - **Done for now** — I'll come back later
 
 **No selectors.yaml** — selectors are generated during `/sungen:run-test`.

package/src/orchestrator/templates/ai-instructions/claude-cmd-design.md

@@ -0,0 +1,12 @@
+---
+name: design
+description: 'Alias of create-test. Generates test cases AND runs the quality harness (gate + repair). Kept for discoverability; create-test now does this by default.'
+argument-hint: [screen-name]
+allowed-tools: Read, Grep, Bash, Glob, Write, AskUserQuestion, Skill, mcp__playwright__browser_navigate, mcp__playwright__browser_snapshot, mcp__playwright__browser_take_screenshot
+---
+
+## `/sungen:design` is an alias of `/sungen:create-test`
+
+As of v3.0 the quality harness (discovery → viewpoint overview → generate → **`sungen audit` gate → repair loop** → manifest/ledger) is built into **`/sungen:create-test`** by default — the user does not need a second command to get quality.
+
+**Do exactly what `/sungen:create-test <name>` does.** Follow the `create-test` command instructions verbatim (including the mandatory harness gate & repair step and the `sungen-harness-audit` skill). This `design` entry exists only so the name remains discoverable for users who learned it during the beta.

package/src/orchestrator/templates/ai-instructions/claude-cmd-feedback.md

@@ -0,0 +1,36 @@
+---
+name: feedback
+description: 'Record QA feedback locally (test-design knowledge or product telemetry). Auto-attaches context and stores to .sungen/feedback/.'
+argument-hint: [message]
+allowed-tools: Read, Grep, Bash, Glob
+---
+
+## Role
+
+You capture QA feedback and store it **locally** (no server) via `sungen feedback record`. The value is closing the learning loop inside this project — the harness can later reuse it (don't regenerate rejected viewpoints; include added ones) and it feeds the spec-change/reuse plan.
+
+## Steps
+
+1. Read the message from `$ARGUMENTS` (ask if empty).
+2. **Classify the type** (do not over-ask — infer, confirm only if ambiguous):
+   - `test-design` — about a viewpoint/scenario being wrong, missing, duplicate, low-value, or a new viewpoint to add.
+   - `product` — about Sungen itself behaving wrong (a command failed, generated bad output structurally, a bug).
+   - `other` — anything else.
+3. **Auto-attach context** (do not make the user repeat it):
+   - `--screen <name>`: the screen/flow currently in focus (from the conversation or cwd `qa/screens|flows/`).
+   - `--target <ref>`: if the message references a viewpoint id (`VP-...`), a scenario title, a command, or an artifact, pass it.
+   - `--decision <accept|reject|edit|add|none>`: if the feedback is a decision on an AI suggestion (e.g. "this viewpoint is wrong" → `reject`; "also test X" → `add`).
+   - `--reason <text>`: the rationale, if distinct from the message.
+4. Run, e.g.:
+   ```bash
+   sungen feedback record --type test-design --screen <name> \
+     --target "VP-DATA-CONSISTENCY" --decision add \
+     --message "<message>" --reason "<why>"
+   ```
+5. Confirm what was recorded and where (`.sungen/feedback/feedback.jsonl`). Note it is **local now**; cross-project sync is opt-in and added later.
+6. If the feedback implies a concrete next action (e.g. a missing critical viewpoint), offer it: `/sungen:design <name>` to regenerate with the gate, or `/sungen:add-flow` for a cross-screen gap.
+
+## Notes
+- **Never send anywhere** — this only writes a local file.
+- Keep `product` feedback separate from `test-design` so it can route to telemetry vs the viewpoint knowledge later.
+- View history: `sungen feedback list [--screen <name>] [--type <t>]`.

package/src/orchestrator/templates/ai-instructions/claude-cmd-review.md

@@ -1,45 +1,42 @@
 ---
 name: review
-description: 'Review test cases for a Sungen screen — validate syntax, score coverage, check viewpoint quality.'
+description: 'Independent quality checkpoint for test cases — runs the harness (audit gate + reviewer + script-check) from a fresh context and presents one unified scorecard. Use for manually/prompt-authored or hand-edited testcases, before delivery, or in CI.'
 argument-hint: [screen-name]
-allowed-tools: Read, Grep, Glob, Edit, Write, AskUserQuestion
+allowed-tools: Read, Grep, Glob, Bash, Edit, Write, AskUserQuestion
 ---
 
 ## Role
 
-You are a **Senior QA Reviewer**. You evaluate Gherkin test cases using the `sungen-tc-review`, `sungen-viewpoint`, and `sungen-gherkin-syntax` skills.
+You are an **independent QA Reviewer** running in a **fresh context** — you did not author these tests. You do **not** invent a parallel score; you run the **harness** and present its signals as a human scorecard. Skills: `sungen-tc-review` (presentation rubric), `sungen-viewpoint`, `sungen-gherkin-syntax`.
 
-## Parameters
+## When this matters (positioning)
 
-Parse **name** from `$ARGUMENTS`. If missing, ask the user.
-
-**Auto-detect context**: check if `qa/flows/<name>/` exists → flow mode (base path: `qa/flows/<name>/`). Else check `qa/screens/<name>/` → screen mode (base path: `qa/screens/<name>/`).
+`/sungen:create-test` already runs the harness gate + repair while generating, so you do **not** need to review right after it. Run `/sungen:review` when the harness did **not** run, or when you need an independent sign-off:
+- Test cases **written by hand or by a free-form prompt** (bypassing create-test).
+- A `.feature` that was **hand-edited** after generation.
+- **Before `/sungen:delivery`** — an independent quality + integrity gate before client hand-off.
+- In **CI** — fail the build on a failing gate or spec drift.
 
 ## Steps
 
-1. **Enumerate feature files** — glob `<base>/<name>/features/*.feature`. A screen may have one main file (`<name>.feature`) plus sub-features (`<name>-<sub>.feature` like `awards-modal.feature`); a flow has a single `<name>.feature`. If zero `.feature` files found → `/sungen:create-test` first.
-2. **Review every feature file** — for each `<basename>.feature` discovered in step 1:
-   - Read `<basename>.feature` and the matching `test-data/<basename>.yaml`.
-   - Apply the `sungen-tc-review` skill — score the **7-dimension rubric (100 pts)**: Structure & Format (15), Coverage (30), Assertion Quality (20), Test Data (10), Security & Permission (10), Automation Readiness (10), Maintainability (5). **For flows**, also apply the flow-specific checks (Layer A7 "Tags & Flow"). Use `sungen-viewpoint` for pattern checklists.
-   - Apply the **Unverified Selectors check** — if `<base>/<name>/selectors/<basename>.yaml` exists, count lines matching `@needs-live-verify`. Include in the per-file report as a non-scoring metric. Does NOT affect the score or the PASS threshold.
-3. **Aggregated output** — present scores in a per-feature table, then a screen-level rollup:
+1. **Enumerate feature files** — glob `<base>/<name>/features/*.feature` (main + any sub-features). If none → `/sungen:create-test` first.
+2. **Run the harness (source of truth) — do NOT re-score with a separate rubric:**
+   - `sungen audit --screen <name>` (Bash) → gate status, business-weighted score, findings, gaps (coverage / assertion-depth / balance / duplicate / traceability).
+   - **`sungen-reviewer`** sub-agent (Task tool, `subagent_type: sungen-reviewer`) → semantic verdict the gate can't see (do steps prove the title, observable Then, @manual justified). Copilot/no-sub-agents: apply the `sungen-reviewer` criteria inline.
+   - `sungen script-check --screen <name>` (Bash) → is the generated spec a 1:1 of the Gherkin (only if a spec exists; flags hand-edit / stale drift).
+3. **Unified scorecard** — present ONE report per feature, anchored on the harness signals (the `sungen-tc-review` 7 dimensions are a *presentation layer* over these, not a competing score):
 
    ```
-   Feature              Total  Verdict       Unverified
-   ─────────────────────────────────────────────────────
-   home.feature           88   PASS          0
-   home-modal.feature     64   CONDITIONAL   2
-   ─────────────────────────────────────────────────────
-   Screen rollup (mean)   76   PASS
+   Feature        Gate   Score   Reviewer        Spec 1:1     Verdict
+   ───────────────────────────────────────────────────────────────────
+   home.feature   PASS   8.4/10  2 minor issues  in-sync      PASS
    ```
-
-   - **>= 70**: PASS that file.
-   - **50–69**: CONDITIONAL — fix before execution.
-   - **< 50**: FAIL — revise & re-review.
-   - "Unverified" = count of `@needs-live-verify` selectors (non-scoring). Show the full per-file report (dimension breakdown, recommendations, top issues) **only for files that are CONDITIONAL or FAIL**, or when the user asks for the deep report.
-4. If any file is CONDITIONAL or FAIL and user confirms → update that file's test cases following `sungen-gherkin-syntax` and `sungen-tc-generation` skills, then re-review **only those files** (skip already-passing ones to save time).
-5. After all files PASS (or user decides to proceed), use `AskUserQuestion` to offer next steps:
-
-- **`/sungen:run-test <name>`** — Generate selectors, compile, and run tests for **every feature** in this screen (Recommended)
-- **`/sungen:create-test <name>`** — Add more test cases before running
-- **Done for now** — I'll come back later
+   - **Gate PASS + reviewer clean + spec in-sync** → PASS.
+   - **Gate FAIL or reviewer NEEDS-REPAIR or drift** → CONDITIONAL/FAIL — show the findings + reviewer issues + fixes.
+   - The score is the **audit business-weighted score** adjusted down by unresolved reviewer issues — never a parallel number that contradicts the gate.
+4. **Repair (on confirm)** — if CONDITIONAL/FAIL, apply the audit findings + reviewer fixes (use `remember`/`see all` for cross-screen/filter per `sungen-harness-audit`), then re-run step 2 for the affected file. If a drift was found, `sungen generate` to resync the spec (never hand-edit it).
+5. **Trace + next steps** — run `sungen trace --screen <name>` to show the **human-loop focus** (@manual scenarios to verify). Then `AskUserQuestion`:
+   - **`/sungen:run-test <name>`** — generate selectors, compile, run (if not yet run) **(Recommended)**
+   - **`/sungen:delivery <name>`** — export the deliverable (review passed)
+   - **`/sungen:create-test <name>`** — add more coverage
+   - **Done for now**

package/src/orchestrator/templates/ai-instructions/claude-cmd-run-test.md

@@ -45,7 +45,7 @@ Skip this pre-flight when `--env` matches the base locale (no overlay needed in
             one browser_snapshot → cross-verify every [Reference] label vs snapshot name →
             generate selectors.yaml (verified entries; explicit YAML for any label≠DOM-name mismatch)
      NO  → spec_figma.md exists in requirements/?
-             YES → provisional flow (sungen-figma-source + sungen-selector-fix skills):
+             YES → provisional flow (sungen-capture mode figma-pat + sungen-selector-fix skills):
                    1. Read filtered Figma node data from spec_figma.md (## Components + ## Text Inventory)
                    2. Apply selector priority from sungen-selector-fix § Step 3 (testid > role+name > label > placeholder > text > locator CSS last)
                    3. Write selectors.yaml — every provisional entry gets this comment on the line above:
@@ -83,6 +83,9 @@ Skip this pre-flight when `--env` matches the base locale (no overlay needed in
 6. **Phase 2 — Priority Wave**: Run all `@high` scenarios. Fix only failures from this wave. Max 2 attempts. Shared selectors fixed here cascade to later phases.
 7. **Phase 3 — Full Run**: Run all tests. Fix only **new** failures (elements unique to `@normal`/`@low`). Max 1 attempt. Don't loop on low-priority failures.
 8. **Phase 4 — Regression**: One final full run. Report results. No more fix loops.
+9. **Integrity check & trace (always run after the final run).**
+   - `sungen script-check --screen <name>` — verify the generated spec is a **1:1** of the Gherkin (every non-@manual scenario ↔ one `test()`, no drift). If it reports **DRIFT** (spec hand-edited or stale), re-run `sungen generate --screen <name>` so the spec matches the feature, then re-run — **never hand-edit the generated spec** (auto-fix must edit `selectors.yaml`, not the `.spec.ts`).
+   - `sungen ledger record --screen <name> --step run --ms <elapsed>` (record this run), then `sungen trace --screen <name>` — show the process map + bottlenecks + **HUMAN-LOOP FOCUS** (the @manual scenarios the QA must verify) to the user.
 
 ## Playwright command guidelines
 

package/src/orchestrator/templates/ai-instructions/claude-config.md

@@ -16,10 +16,7 @@ You generate 3 files for sungen — a Gherkin compiler that produces Playwright
 | `sungen-selector-keys` | YAML key generation from `[Reference]` names, suffixes, lookup priority |
 | `sungen-selector-fix` | Selector generation from live page, auto-fix strategy |
 | `sungen-delivery` | Export Gherkin + Playwright results → CSV test case deliverable |
-| `sungen-capture-figma` | Fetch design context + PNG from a Figma frame URL via Figma Dev Mode MCP |
-| `sungen-capture-local` | Load existing UI assets (screenshots, mockups, Figma exports) from `requirements/ui/` |
-| `sungen-capture-live` | Capture a live running page via Playwright MCP (snapshot + screenshot) |
-| `sungen-figma-source` | Figma URL → spec_figma.md + ui/*.png + provisional selectors |
+| `sungen-capture` | Acquire visual/design context — one skill, 4 modes: figma-mcp (Dev Mode MCP), figma-pat (URL → spec_figma.md), live (Playwright MCP scan), local (images in `requirements/ui/`) |
 | `sungen-locale` | Bootstrap i18n — audit selectors, detect locale switch mechanism, generate test-data overlay |
 
 ## Workflow (7 AI commands)

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-figma-mcp.md

@@ -0,0 +1,82 @@
+# Capture mode: figma-mcp
+
+Pull **structured design data** (layout, typography, colors, component tree, design tokens) and a **PNG screenshot** from a Figma frame URL via the **Figma Dev Mode MCP**, so `sungen-tc-generation` can author Gherkin + test-data before a live domain exists. Use when the project is pre-launch or Figma is the source of truth and the live build lags the design.
+
+## Prerequisites
+
+- **Figma MCP server** (`https://mcp.figma.com/mcp`, HTTP transport) connected in `.mcp.json` — `sungen init` scaffolds this. On first use, Claude Code opens a browser for Figma OAuth. Official tools: `get_design_context`, `get_variable_defs`, `get_screenshot`.
+- Figma account signed in with access to the file. **Dev/Full seats** get per-minute rate limits; **Starter/View seats** get monthly tool-call limits.
+- A Figma URL with both **fileKey** and **nodeId**.
+
+If the MCP is not connected, **do not fail silently** — tell the user:
+> "Figma MCP not detected. Run `sungen init` to scaffold the config, or manually add `figma` with `url: https://mcp.figma.com/mcp` to `.mcp.json`. Then sign in when Claude Code prompts."
+
+Then stop.
+
+## Steps
+
+### 1. Resolve Figma URL
+
+Prefer in this order:
+1. `Figma URL` field in `requirements/spec.md` (Overview section)
+2. If empty/missing → `AskUserQuestion`: *"Paste the Figma frame URL"* (free text)
+
+Accept any of these shapes:
+```
+https://www.figma.com/file/<fileKey>/<title>?node-id=<nodeId>
+https://www.figma.com/design/<fileKey>/<title>?node-id=<nodeId>
+https://www.figma.com/proto/<fileKey>/<title>?node-id=<nodeId>
+```
+Parse: `fileKey` = segment after `/file/`, `/design/`, or `/proto/`; `nodeId` = the `node-id` query param (pass `-` or `:` through as-is). If `node-id` is missing, ask the user to select a frame in Figma and copy the **frame URL** (not the file root).
+
+### 2. Fetch design context
+
+Call **both** in parallel:
+```
+get_design_context({ fileKey, nodeId })
+get_variable_defs({ fileKey, nodeId })
+```
+`get_design_context` → layout, typography, colors, component structure, spacing. `get_variable_defs` → named design tokens.
+
+### 3. Fetch screenshot
+
+```
+get_screenshot({ fileKey, nodeId })
+```
+Save the PNG to `requirements/ui/figma-<sanitized-nodeId>.png` (replace `:` and `-` with `_`, e.g. `42-15` → `figma-42_15.png`).
+
+### 4. Write metadata dump
+
+Combine design context + variables into `requirements/ui/figma-meta.md`:
+```markdown
+# Figma Capture — <nodeId>
+**Source:** <full Figma URL>
+**Captured:** <ISO date>
+## Components
+<component names + variants>
+## Typography
+<font families, sizes, weights, line heights>
+## Colors
+<color tokens + raw hex>
+## Spacing & Layout
+<spacing tokens, auto-layout specs>
+## Text Content
+<visible text strings — used by tc-generation to populate test-data>
+```
+Consumed by `sungen-tc-generation` as a secondary source alongside `spec.md`.
+
+### 5. Report back
+
+> Captured Figma frame `<nodeId>`: Components N · Text strings M · Design tokens K · Screenshot `requirements/ui/figma-<nodeId>.png` · Metadata `requirements/ui/figma-meta.md`
+
+Then hand back to the calling command.
+
+## Error handling
+
+| Error | Action |
+|---|---|
+| MCP tool not available | Print setup instructions, stop, do not fall back silently |
+| `fileKey` missing from URL | Ask user to paste a valid frame URL |
+| `nodeId` missing from URL | Ask user to right-click a frame in Figma → *Copy link to selection* |
+| `get_design_context` 403 | Ask user to check Dev Mode seat on that file |
+| `get_screenshot` returns no image | Continue with metadata only; warn no PNG was captured |

package/{dist/orchestrator/templates/ai-instructions/copilot-skill-figma-source.md → src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-figma-pat.md}

@@ -1,18 +1,6 @@
----
-name: sungen-figma-source
-description: 'Figma URL → spec_figma.md envelope + LLM-synthesized narrative from cached raw node JSON. Auto-loaded when --figma flag present or spec_figma.md exists.'
-user-invocable: false
----
+# Capture mode: figma-pat
 
-## When This Skill Loads
-
-Auto-load triggers (any one is sufficient):
-
-- Any sungen AI command invoked with `--figma` flag
-- `requirements/spec_figma.md` exists in the screen directory
-- User mentions a Figma URL or says "generate from Figma"
-
----
+Figma URL → `spec_figma.md` envelope + LLM-synthesized narrative from cached raw node JSON. This mode is the active one when any of these is true: a sungen command was invoked with `--figma`, `requirements/spec_figma.md` exists, or the user says "generate from Figma".
 
 ## Prerequisites
 
@@ -22,8 +10,6 @@ Auto-load triggers (any one is sufficient):
 
 **Never paste the PAT into any transcript, spec file, or commit.**
 
----
-
 ## Two-Layer Architecture
 
 `spec_figma.md` has two layers separated by the `<!-- SYNTHESIS-BELOW -->` marker:
@@ -31,34 +17,27 @@ Auto-load triggers (any one is sufficient):
 | Layer | Producer | Overwrite Rule |
 |---|---|---|
 | **Envelope** (above marker) | sungen CLI | Regenerated each `sungen figma` run — deterministic |
-| **Narrative** (below marker) | This skill (LLM) | Replaced on re-synthesis — everything from marker to EOF |
+| **Narrative** (below marker) | This mode (LLM) | Replaced on re-synthesis — everything from marker to EOF |
 
 The envelope contains: YAML frontmatter, Frame metadata, Screenshots. The narrative is synthesized by YOU from the cached raw Figma node JSON.
 
----
-
 ## Inputs You Read
 
 The scaffolder persists a raw (unfiltered) Figma node tree to:
-
 ```
 .sungen/figma-cache/<fileKey>/<versionId>/<nodeId>-raw.json
 ```
-
 Read this file + the envelope frontmatter of `requirements/spec_figma.md` + any PNGs under `requirements/ui/`. You MUST NOT call the Figma REST API directly — the PAT is not available to you.
 
----
-
 ## Synthesis Task
 
-Append 7 narrative sections below `<!-- SYNTHESIS-BELOW -->`. Each section is inferred from the raw node tree (names, types, `characters`, layout bounds, auto-layout direction, componentProperties):
+Append 7 narrative sections below `<!-- SYNTHESIS-BELOW -->`. Each is inferred from the raw node tree (names, types, `characters`, layout bounds, auto-layout direction, componentProperties):
 
 ### 1. Purpose
 One paragraph. What screen is this? Primary user goal? Infer from frame name + top-level text + dominant CTA.
 
 ### 2. ASCII Layout
-Rough spatial sketch using box characters. Reflect top-bottom / left-right ordering from absoluteBoundingBox. Keep under ~20 lines. Example:
-
+Rough spatial sketch using box characters. Reflect top-bottom / left-right ordering from absoluteBoundingBox. Keep under ~20 lines:
 ```
 ┌──────────────────────────────────────┐
 │ [Logo]                     [Sign In] │
@@ -72,55 +51,46 @@ Rough spatial sketch using box characters. Reflect top-bottom / left-right order
 ```
 
 ### 3. Regions
-Bulleted list of the major layout regions (header, sidebar, main, footer, modal, etc.) with a one-line purpose each. Use auto-layout frames as region hints.
+Bulleted list of major layout regions (header, sidebar, main, footer, modal…) with a one-line purpose each. Use auto-layout frames as region hints.
 
 ### 4. Actions
-Every interactive element the user can trigger. Derive from nodes whose name/type suggests a button, link, icon-button, menu-item, toggle, etc. Format:
-
+Every interactive element the user can trigger (button, link, icon-button, menu-item, toggle…):
 ```
 - **<Action name>** — <what it does> (source: <node name>)
 ```
 
 ### 5. Form Fields
-Every input the user can fill. Include label, type (text/email/password/select/checkbox/radio/textarea/date), required hint if inferable, and placeholder.
-
+Every input. Include label, type (text/email/password/select/checkbox/radio/textarea/date), required hint if inferable, placeholder:
 ```
 | Label | Type | Required | Placeholder |
 |---|---|---|---|
 ```
-
-Omit entirely (write `_none_`) if no inputs exist.
+Omit (write `_none_`) if no inputs exist.
 
 ### 6. Data Columns
-If the screen shows a table, list, or card grid — enumerate the columns/fields displayed per row. Otherwise write `_none_`.
+If the screen shows a table/list/card grid — enumerate the columns/fields per row. Otherwise `_none_`.
 
 ### 7. Navigation
-Outgoing links, tab bars, breadcrumbs, back buttons — anything that moves the user to another screen. Include both explicit navigation components and implicit CTAs that navigate.
-
----
+Outgoing links, tab bars, breadcrumbs, back buttons — anything that moves to another screen. Include explicit nav components and implicit CTAs that navigate.
 
 ## Synthesis Workflow
 
 1. Read `requirements/spec_figma.md` — note `file_key`, `node_id`, `figma_version_id` from frontmatter
 2. Read `.sungen/figma-cache/<file_key>/<figma_version_id>/<safe_node_id>-raw.json` (colons in node_id become underscores)
-3. Traverse the tree. Collect: names, types, `characters`, `componentProperties`, `absoluteBoundingBox`
+3. Traverse the tree. Collect names, types, `characters`, `componentProperties`, `absoluteBoundingBox`
 4. Produce the 7 sections above
 5. **Locate the insertion point** in `spec_figma.md`:
    - **If `<!-- SYNTHESIS-BELOW -->` is present** → replace everything from the marker (inclusive) to EOF with: the marker line, a blank line, then the 7 sections.
-   - **If the marker is NOT present** (older `spec_figma.md` pre-envelope-refactor, or hand-edited file) → locate the last non-empty line of the envelope (usually the end of `## Screenshots`), append a blank line, then write the marker, another blank line, then the 7 sections. Do NOT delete any existing envelope content.
+   - **If the marker is NOT present** (older file or hand-edited) → locate the last non-empty line of the envelope (usually the end of `## Screenshots`), append a blank line, then the marker, another blank line, then the 7 sections. Do NOT delete any envelope content.
    - **If the file is missing entirely** → advise the user to re-run `sungen add --screen <screen> --figma <url> --refresh` to regenerate the envelope first. Do not fabricate one.
 6. Preserve the envelope (frontmatter + Frame + Screenshots) byte-for-byte. Never touch content above the marker.
 
----
-
 ## Re-synthesis
 
 - If the envelope's `figma_version_id` changed → envelope is fresh; re-run synthesis
-- If only the narrative is stale (user wants a rewrite) → truncate from marker to EOF and regenerate
+- If only the narrative is stale → truncate from marker to EOF and regenerate
 - Never edit content ABOVE the marker — that is the scaffolder's territory
 
----
-
 ## Selector Heuristics (for downstream `run-test`)
 
 During `run-test` Phase 0, provisional selectors can be seeded from the raw JSON:
@@ -135,15 +105,11 @@ During `run-test` Phase 0, provisional selectors can be seeded from the raw JSON
 | Node name ends `Icon` | `role: img` + `name: "<accessible name>"` |
 
 Every provisional entry MUST carry:
-
 ```
 # @needs-live-verify source=figma node_id=<id>
 ```
-
 Provisional selectors feed `selectors.yaml` as candidates. `run-test` Phase 0 verifies them against the live page and overwrites incorrect entries.
 
----
-
 ## Security
 
 - Never include the PAT in `spec_figma.md`, selectors, test data, or any committed file

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-live.md

@@ -0,0 +1,60 @@
+# Capture mode: live
+
+Navigate a running application, take **one accessibility snapshot** and **one screenshot**, and save them as visual context for test generation. Use when the app is live (dev, staging, or production with read-only access) and you want tests grounded in the actual rendered UI. Handles auth gracefully: if the page redirects to login, ask the user to sign in manually rather than injecting cookies.
+
+## Prerequisites
+
+- Playwright MCP connected.
+- Dev/staging server reachable (or a public URL).
+- `playwright.config.ts` exists at the project root (for `baseURL` fallback).
+
+## Steps
+
+### 1. Resolve target URL
+
+1. `Live URL` field in `requirements/spec.md` (Overview section)
+2. `baseURL` from `playwright.config.ts` + `URL Path` from `spec.md`
+3. Neither → `AskUserQuestion`: *"Paste the full URL for the page to scan"*
+
+### 2. Navigate
+
+`browser_navigate` to the resolved URL.
+
+### 3. Handle auth redirect
+
+If the page redirects to a login route (URL contains `/login`, `/signin`, `/auth`, or content indicates a login screen):
+1. Tell the user which login URL they landed on.
+2. `AskUserQuestion`:
+   - **I'll log in manually** — wait for confirmation, then re-navigate to the target URL
+   - **Skip live scan** — switch to mode `local`
+   - **Cancel**
+3. **Never** inject cookies or localStorage via `browser_evaluate` / `browser_run_code`. Auth belongs to the user.
+
+### 4. Snapshot
+
+Take **ONE** `browser_snapshot`. This accessibility tree is the primary AI context — roles, names, text, structure that tc-generation uses to identify sections and fields.
+
+### 5. Screenshot (recommended)
+
+Take **ONE** `browser_take_screenshot` with `fullPage: true`. Save to `requirements/ui/live-<timestamp>.png`, where `<timestamp>` is `YYYYMMDD-HHMM` local time (e.g. `live-20260421-1430.png`).
+
+### 6a. Verify unauthenticated redirect target (flow capture only)
+
+When capturing for a **flow** with security scenarios (e.g. "unauthenticated user cannot access X"):
+1. Open a **fresh incognito/unauthenticated** context (no storage state).
+2. `browser_navigate` to the protected route.
+3. Record the **actual redirect URL** — do NOT assume `/login`; it may be `/register`, `/`, etc.
+4. Report the redirect target: *"Unauthenticated access to `/dashboard` redirects to `/register`"*.
+5. The caller must use the **actual redirect URL** in Gherkin assertions, never an assumed one.
+
+Skip if the flow has no security scenarios or the user says to skip.
+
+### 6. Detect discrepancies vs spec
+
+If `spec.md` exists, cross-check the snapshot against spec sections: fields in spec but not in snapshot → *missing in UI*; elements in snapshot but not in spec → *missing in spec*. Report findings but **do not** auto-edit `spec.md`.
+
+### 7. Report back
+
+> Captured live page `<URL>`: Snapshot N interactive elements · Screenshot `requirements/ui/live-<timestamp>.png` · Discrepancies vs spec: <count or "none">
+
+Hand back to the calling command. Scans **exactly one** page per invocation.

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-local.md

@@ -0,0 +1,38 @@
+# Capture mode: local
+
+Use **pre-existing images** in `requirements/ui/` as visual context. No network, no MCP, no live site — works for any design tool (Figma export, Sketch, Penpot, Zeplin, hand-drawn, staging screenshots). This is the **baseline fallback**: if the live domain is down and Figma MCP isn't configured, this always works as long as the user drops images in the folder.
+
+## Steps
+
+### 1. List available images
+
+Glob `requirements/ui/*.{png,jpg,jpeg,webp,gif}` and report count + filenames. Filter out metadata files (e.g. `figma-meta.md` written by mode figma-mcp) — those are read by `tc-generation` separately, not treated as images here.
+
+### 2. Handle empty folder
+
+If no images found:
+1. Tell the user the folder is empty, with the full path so they can open it in Finder.
+2. `AskUserQuestion`:
+   - **I'll drop images now** — wait for confirmation, then re-glob
+   - **Switch to Figma** — switch to mode `figma-mcp`
+   - **Switch to live page scan** — switch to mode `live`
+   - **Cancel** — abort create-test
+3. If "drop images now", wait for confirmation (e.g. "done") then re-run step 1.
+
+### 3. Read images for context
+
+Use the `Read` tool on each image — Claude Code reads PNG/JPG/WebP directly as visual context. For large sets (>10 images), ask which are primary and which are states/variants to avoid loading too much at once.
+
+### 4. Summarize
+
+> Loaded N image(s) from `requirements/ui/`:
+> - `<filename-1>` — <one-line description of what's visible>
+> - `<filename-2>` — <one-line description>
+
+Hand back to the calling command.
+
+## File naming hints for users
+
+Nudge users toward consistent filenames (don't enforce):
+- `<section>-default.png` / `-error.png` / `-loading.png` / `-empty.png` — section states
+- `full-page.png` / `viewport.png` — whole screen (auto-generated by `sungen add --capture`)