@sun-asterisk/sungen 2.5.0 → 2.5.1

package/dist/orchestrator/figma/spec-figma-section-renderers.js

@@ -0,0 +1,47 @@
+"use strict";
+/**
+ * Section-render helpers for spec-figma-renderer.ts.
+ *
+ * After the shift to LLM-synthesized narrative sections, the envelope only
+ * needs: frontmatter, Frame metadata, Screenshots, and the SYNTHESIS marker.
+ * All prose sections (Purpose, ASCII Layout, Regions, Actions, Form Fields,
+ * Data Columns, Navigation) are appended below the marker by the
+ * sungen-figma-source skill.
+ *
+ * Pure — no I/O.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.SYNTHESIS_MARKER = void 0;
+exports.renderFrontmatter = renderFrontmatter;
+exports.renderFrame = renderFrame;
+exports.renderScreenshots = renderScreenshots;
+/**
+ * Sentinel comment that separates the deterministic envelope (above) from
+ * the LLM-synthesized narrative (below). Re-synthesis replaces everything
+ * from this marker to EOF.
+ */
+exports.SYNTHESIS_MARKER = '<!-- SYNTHESIS-BELOW -->';
+function renderFrontmatter(input) {
+    return [
+        '---',
+        'source: figma',
+        `file_key: ${input.fileKey}`,
+        `node_id: ${input.nodeId}`,
+        `figma_version_id: ${input.versionId}`,
+        `fetched_at: ${input.fetchedAt}`,
+        `generator: ${input.generatorVersion}`,
+        '---',
+    ].join('\n');
+}
+function renderFrame(node) {
+    const bb = node.boundingBox;
+    const dims = bb ? `${bb.w}x${bb.h}` : '—';
+    return ['## Frame', `- Name: ${node.name}`, `- Dimensions: ${dims}`, `- Type: ${node.type}`].join('\n');
+}
+function renderScreenshots(imagePaths) {
+    if (imagePaths.length === 0)
+        return '## Screenshots\n- (no images downloaded)';
+    const items = imagePaths.map((p, i) => `- \`${p}\` — ${i === 0 ? 'default state' : `variant ${i}`}`);
+    return ['## Screenshots', ...items].join('\n');
+}
+//# sourceMappingURL=spec-figma-section-renderers.js.map

package/dist/orchestrator/figma/spec-figma-section-renderers.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"spec-figma-section-renderers.js","sourceRoot":"","sources":["../../../src/orchestrator/figma/spec-figma-section-renderers.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;GAUG;;;AAYH,8CAWC;AAED,kCAIC;AAED,8CAIC;AA9BD;;;;GAIG;AACU,QAAA,gBAAgB,GAAG,0BAA0B,CAAC;AAE3D,SAAgB,iBAAiB,CAAC,KAA2B;IAC3D,OAAO;QACL,KAAK;QACL,eAAe;QACf,aAAa,KAAK,CAAC,OAAO,EAAE;QAC5B,YAAY,KAAK,CAAC,MAAM,EAAE;QAC1B,qBAAqB,KAAK,CAAC,SAAS,EAAE;QACtC,eAAe,KAAK,CAAC,SAAS,EAAE;QAChC,cAAc,KAAK,CAAC,gBAAgB,EAAE;QACtC,KAAK;KACN,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACf,CAAC;AAED,SAAgB,WAAW,CAAC,IAAuB;IACjD,MAAM,EAAE,GAAG,IAAI,CAAC,WAAW,CAAC;IAC5B,MAAM,IAAI,GAAG,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC;IAC1C,OAAO,CAAC,UAAU,EAAE,WAAW,IAAI,CAAC,IAAI,EAAE,EAAE,iBAAiB,IAAI,EAAE,EAAE,WAAW,IAAI,CAAC,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC1G,CAAC;AAED,SAAgB,iBAAiB,CAAC,UAAoB;IACpD,IAAI,UAAU,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,0CAA0C,CAAC;IAC/E,MAAM,KAAK,GAAG,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,eAAe,CAAC,CAAC,CAAC,WAAW,CAAC,EAAE,EAAE,CAAC,CAAC;IACrG,OAAO,CAAC,gBAAgB,EAAE,GAAG,KAAK,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACjD,CAAC"}

package/dist/orchestrator/templates/ai-instructions/claude-cmd-add-screen.md

@@ -1,7 +1,7 @@
 ---
 name: add-screen
 description: 'Add a new Sungen screen — scaffolds directories, helps fill spec.md, and can capture visuals from Figma (pre-launch) or live page via the capture skills'
-argument-hint: [screen-name] [url-path]
+argument-hint: [screen-name] [url-path] [--figma <url>]
 allowed-tools: Read, Grep, Bash, Glob, Edit, Write, AskUserQuestion, mcp__playwright__browser_navigate, mcp__playwright__browser_take_screenshot, mcp__playwright__browser_snapshot, mcp__figma__get_design_context, mcp__figma__get_variable_defs, mcp__figma__get_screenshot
 ---
 
@@ -11,37 +11,82 @@ You are adding a new Sungen screen for test generation.
 
 Parse from `$ARGUMENTS`:
 - **screen** — screen name (e.g., `login`, `dashboard`, `settings`)
-- **path** — URL path (e.g., `/login`, `/dashboard`, `/settings`)
+- **path** — URL path (e.g., `/login`, `/dashboard`, `/settings`) - optional when `--figma` is provided
+- **--figma \<url\>** — Figma share URL (optional)
+- **--refresh** — bypass Figma cache and re-fetch (optional, use with `--figma`)
+- **--scale \<n\>** — PNG export scale factor, default 2 (optional)
+- **--hi-res** — export at 4× scale, shorthand for `--scale 4` (optional)
 
 If **screen** is missing, ask: "What is the screen name? (e.g., `login`, `dashboard`)"
-If **path** is missing, ask: "What is the URL path? (e.g., `/login`, `/dashboard`)"
+If **path** is missing and `--figma` was NOT provided, ask: "What is the URL path? (e.g., `/login`, `/dashboard`)"
 
 ## Steps
 
 ### 1. Scaffold the screen
 
-Run:
+**Standard path (no `--figma`):**
 ```bash
 sungen add --screen <screen> --path <path>
 ```
 
-### 2. Fill spec.md
+**Figma branch (when `--figma <url>` is in `$ARGUMENTS`):**
 
-Use `AskUserQuestion`: *"Fill `spec.md` now?"* — offer **Yes, fill now (Recommended)** / **Skip, fill later**.
+Invoke the `sungen-figma-source` skill by running:
+```bash
+sungen add --screen <screen> --figma '<url>' [--path <path>] [--refresh] [--scale <n>]
+# Single-quote the URL — Figma links contain `&` which bash otherwise treats as a background operator.
+```
+
+This CLI command automatically:
+1. Parses the Figma URL and fetches the design node.
+2. Downloads frame + variant PNGs to `qa/screens/<screen>/requirements/ui/`.
+3. Writes `qa/screens/<screen>/requirements/spec_figma.md` (auto-generated, always overwritten on re-run).
+4. Creates `qa/screens/<screen>/requirements/spec.md` stub **only if the file does not already exist** — never overwrites existing human content.
+
+**Important coexistence rules:**
+- `--figma` and `--path` can be passed together: `--path` provides the live URL for `run-test`; `--figma` provides design context.
+- `spec.md` is the human-authored source of truth. Never modify it automatically.
+- `spec_figma.md` is auto-generated — always overwritten; tell the user to copy useful sections into `spec.md`.
+- `--capture` (Playwright screenshot) and `--figma` can be used simultaneously; they produce different outputs.
+
+**If Figma auth is missing**, the command will fail with a message like:
+> Figma PAT is not configured. Run: sungen figma auth set
+
+In that case, guide the user to run `sungen figma auth set` and retry.
 
-If yes → open `qa/screens/<screen>/requirements/spec.md` and help the user fill sections, fields, validation rules, business rules, and states. Especially prompt for the optional **Figma URL** and **Live URL** fields in Overview — those unlock auto-capture without re-asking next run.
+### 1a. Synthesize narrative sections (Figma branch only)
 
-### 3. Capture visual source
+After `sungen add --figma` succeeds, the envelope of `spec_figma.md` is deterministic but the narrative below the `<!-- SYNTHESIS-BELOW -->` marker is empty. Invoke the `sungen-figma-source` skill to fill it:
 
-Use `AskUserQuestion`: *"Capture a visual reference for this screen?"* — always offer all three so pre-launch projects work:
+1. Read `qa/screens/<screen>/requirements/spec_figma.md` — note `file_key`, `node_id`, `figma_version_id` from frontmatter.
+2. Read the cached raw node JSON at `.sungen/figma-cache/<file_key>/<figma_version_id>/<safe_node_id>-raw.json` (colons in node_id become underscores).
+3. Follow the skill's 7-section template (Purpose / ASCII Layout / Regions / Actions / Form Fields / Data Columns / Navigation) and **replace** everything from the marker to EOF.
+4. Preserve the envelope above the marker byte-for-byte.
 
+**Review gate.** Before moving on, show the user the synthesized narrative and use `AskUserQuestion`:
+
+- **Approve** — narrative looks right, continue to Step 2
+- **Edit** — user will tweak `spec_figma.md` now; wait for confirmation before continuing
+- **Cancel** — abort; advise the user that `spec.md` was NOT modified and they can re-run `sungen add --figma --refresh` later
+
+### 2. Capture visual source
+
+**If Figma branch (Step 1) already downloaded PNGs** → visuals already exist. Use `AskUserQuestion` to offer:
+- **Continue** — Figma visuals are enough (Recommended)
+- **Also capture live page** — supplement Figma with real page scan (invoke `sungen-capture-live` skill)
+
+**If standard path (no `--figma`)** → go straight to source selection. Use `AskUserQuestion`: *"Pick a visual source for this screen:"*
 - **Figma design** (Recommended for pre-launch) — invoke `sungen-capture-figma` skill
 - **Live page scan** (dev/staging is up) — invoke `sungen-capture-live` skill
-- **Skip** — user will drop images manually into `requirements/ui/` later, or rely on `/sungen:create-test` to prompt again
+- **Skip** — user will drop images manually into `requirements/ui/` later
 
 Each capture skill writes outputs into `qa/screens/<screen>/requirements/ui/` and reports back a summary. Do not inline capture logic here — always delegate to the skill so behavior stays consistent with `/sungen:create-test`.
 
-If the user has additional UI designs (mockups, hand-drawn sketches), suggest copying them to `requirements/ui/` — `sungen-capture-local` will pick them up during `/sungen:create-test`.
+### 3. Fill spec.md
+
+Use `AskUserQuestion`: *"Fill `spec.md` now? (You can reference the captured visuals)"* — offer **Yes, fill now (Recommended)** / **Skip, fill later**.
+
+If yes → open `qa/screens/<screen>/requirements/spec.md` and help the user fill sections, fields, validation rules, business rules, and states. Reference the captured visuals from Step 2 to suggest field names, form elements, and UI states. Especially prompt for the optional **Figma URL** and **Live URL** fields in Overview — those unlock auto-capture without re-asking next run.
 
 ### 4. Next steps
 

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

@@ -1,13 +1,21 @@
 ---
 name: create-test
-description: 'Create or update test cases for a Sungen screen — generates feature + test-data files (20+ scenarios per viewpoint)'
+description: 'Create or update test cases for a Sungen screen — generates feature + test-data files (tier-based: critical+high first, expand later)'
 argument-hint: [screen-name]
-allowed-tools: Read, Grep, Bash, Glob, Write, AskUserQuestion, mcp__playwright__browser_navigate, mcp__playwright__browser_snapshot, mcp__playwright__browser_take_screenshot, mcp__figma__get_design_context, mcp__figma__get_variable_defs, mcp__figma__get_screenshot
+allowed-tools: Read, Grep, Bash, Glob, Write, AskUserQuestion, Skill, mcp__playwright__browser_navigate, mcp__playwright__browser_snapshot, mcp__playwright__browser_take_screenshot
+---
+
+## ⛔ HARD RULE — No Figma MCP when PAT data exists
+
+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.
+
 ---
 
 ## Role
 
-You are a **Senior QA Engineer** specialized in exhaustive test case design. You structure test cases by viewpoint categories and translate UI into comprehensive Gherkin test cases following the `sungen-gherkin-syntax` and `sungen-tc-generation` skills. Your focus is on **Gherkin scenarios and test data only** — selectors are handled later during `/sungen:run-test`.
+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`.
 
 ## Parameters
 
@@ -17,27 +25,32 @@ Parse **screen** from `$ARGUMENTS`. If missing, ask the user.
 
 1. Verify `qa/screens/<screen>/` exists. If not → `/sungen:add-screen` first.
 2. Check if `.feature` file already has scenarios. If yes → use `AskUserQuestion` to ask the update mode (see `sungen-tc-generation` skill for details). If no → fresh creation.
-3. **Read requirements** — check `qa/screens/<screen>/requirements/`:
+3. **Read requirements & resolve visual source** — check `qa/screens/<screen>/requirements/`:
    - If `spec.md` exists → read it as PRIMARY source (sections, fields, validation rules, business rules, states).
-   - If `ui/` has images → read them for visual context (layout, element positions, states).
    - If `test-viewpoint.md` exists → read it. If it only contains HTML comments (scaffold template), use `AskUserQuestion` to ask:
      - **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
-   - Summarize what you found in requirements and present to the user.
-4. **Screen input** (supplements requirements, or is primary source if no requirements):
-   - Use `AskUserQuestion` to ask the user to pick a visual source — always offer all three options so pre-launch projects work:
-     - **Figma design** (Recommended for pre-launch) — invoke `sungen-capture-figma` skill
-     - **UI images** (existing screenshots/mockups in `requirements/ui/`) — invoke `sungen-capture-local` skill
-     - **Live page scan** (dev/staging is up) — invoke `sungen-capture-live` skill
-   - Each capture skill writes outputs into `qa/screens/<screen>/requirements/ui/` and reports back a summary. Do not inline capture logic here — always delegate to the skill so behavior stays consistent across commands.
-   - After the capture skill returns, cross-check its output against `spec.md` and flag any discrepancies before moving on.
-5. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. When requirements exist, use the "Requirements-Driven Generation" strategy.
-6. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills.
-7. Show summary, then use `AskUserQuestion` to offer next steps:
+
+   **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
+      - **Skip** — generate from spec.md only
+
+   **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. When requirements exist, use the "Requirements-Driven Generation" strategy.
+5. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills.
+6. Show summary, then use `AskUserQuestion` to offer next steps:
 
 - **`/sungen:review <screen>`** — Review syntax, coverage, viewpoint quality (Recommended)
 - **`/sungen:run-test <screen>`** — Skip review, generate selectors and run tests now
-- **`/sungen:create-test <screen>`** — Add more test cases for another section/viewpoint
+- **`/sungen:create-test <screen>`** — Expand coverage: add @normal + @low scenarios
 - **Done for now** — I'll come back later
 
 **No selectors.yaml** — selectors are generated during `/sungen:run-test`.

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

@@ -17,9 +17,10 @@ Parse **screen** from `$ARGUMENTS`. If missing, ask the user.
 
 1. Read `qa/screens/<screen>/features/<screen>.feature` and `qa/screens/<screen>/test-data/<screen>.yaml`. If missing → `/sungen:create-test` first.
 2. Follow the `sungen-tc-review` skill — score 3 dimensions: Syntax (30pts), Coverage (40pts), Viewpoint (30pts). Use `sungen-viewpoint` for pattern checklists.
-3. Output review report per `sungen-tc-review` format. **>= 60%**: PASS. **< 60%**: FAIL with recommendations.
-4. If FAIL and user confirms → update test cases following `sungen-gherkin-syntax` and `sungen-tc-generation` skills, then re-review.
-5. After PASS (or user decides to proceed), use `AskUserQuestion` to offer next steps:
+3. **Unverified Selectors check** — if `qa/screens/<screen>/selectors/<screen>.yaml` exists, count lines matching `@needs-live-verify`. Include in the review report as a non-scoring metric (see `sungen-tc-review` skill for report format). Does NOT affect the 60% threshold.
+4. Output review report per `sungen-tc-review` format. **>= 60%**: PASS. **< 60%**: FAIL with recommendations.
+5. If FAIL and user confirms → update test cases following `sungen-gherkin-syntax` and `sungen-tc-generation` skills, then re-review.
+6. After PASS (or user decides to proceed), use `AskUserQuestion` to offer next steps:
 
 - **`/sungen:run-test <screen>`** — Generate selectors, compile, and run tests (Recommended)
 - **`/sungen:create-test <screen>`** — Add more test cases before running

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

@@ -16,7 +16,39 @@ Parse **screen** from `$ARGUMENTS`. If missing, ask the user.
 ## Pre-run (phased — per `sungen-selector-fix` skill)
 
 1. Verify `qa/screens/<screen>/` has `.feature` + `test-data.yaml`.
-2. **Phase 0 — Selector Pre-gen**: if `selectors.yaml` is missing/empty or doesn't cover the feature file's `[Reference]`s, run Phase 0 from `sungen-selector-fix` — confirm with user, `browser_navigate` → one `browser_snapshot` → merge YAML entries.
+2. **Phase 0 — Selector Pre-gen**: if `selectors.yaml` is missing/empty or doesn't cover the feature file's `[Reference]`s, apply the following decision tree before running Phase 0 from `sungen-selector-fix`:
+
+   ```
+   Phase 0 — Selector Generation decision tree
+
+   Live page reachable? (URL provided and loads without error)
+     YES → existing flow: browser_navigate → one browser_snapshot → generate selectors.yaml (verified entries)
+     NO  → spec_figma.md exists in requirements/?
+             YES → provisional flow (sungen-figma-source + sungen-selector-fix skills):
+                   1. Read filtered Figma node data from spec_figma.md (## Components + ## Text Inventory)
+                   2. Apply selector heuristics from sungen-figma-source skill (testid > role+name > placeholder > label > locator > text)
+                   3. Write selectors.yaml — every provisional entry gets this comment on the line above:
+                          # @needs-live-verify source=figma node_id=<id>
+                   4. Compile: sungen generate --screen <screen> — must succeed
+                   5. Phase 1 smoke check runs; tests using unverified selectors may fail
+                      → auto-fix triggers on next run-test invocation when a live page is available
+             NO  → hard stop: print the following message and stop:
+                   "Cannot generate selectors: no live page URL and no spec_figma.md found.
+                    Options:
+                    • Provide the live URL so Playwright MCP can snapshot the page, OR
+                    • Run: sungen add --screen <screen> --figma <figma-url>  to generate spec_figma.md first"
+   ```
+
+   **Auto-fix on subsequent runs**: when `run-test` is invoked again with a reachable live page, Phase 0 compares the DOM snapshot against existing `selectors.yaml` entries. Entries tagged `# @needs-live-verify` are treated as candidates — if the actual selector differs, the entry is replaced and the comment removed (entry becomes verified). Entries that already match are also promoted to verified (comment removed).
+
+   **`@needs-live-verify` comment format** (one comment line, directly above the YAML key):
+   ```yaml
+   # @needs-live-verify source=figma node_id=<figma-node-id>
+   submit-button:
+     type: role
+     value: button
+     name: "Submit"
+   ```
 3. **Phase 0.5 — Auth Persistence**: if the feature has `@auth:<role>` tags and `specs/.auth/<role>.json` is missing/expired, run Phase 0.5 from `sungen-selector-fix` — user logs in manually in MCP browser → `browser_storage_state` → `specs/.auth/<role>.json`. Offer `sungen makeauth <role>` as CLI fallback only if `browser_storage_state` isn't available in this MCP version.
 4. Compile: `sungen generate --screen <screen>` (default: runtime data loading from YAML). Use `--inline-data` only if user requests compile-time hardcoded values.
 

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

@@ -19,6 +19,7 @@ You generate 3 files for sungen — a Gherkin compiler that produces Playwright
 | `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 |
 
 ## Workflow (5 AI commands)
 

package/dist/orchestrator/templates/ai-instructions/claude-skill-figma-source.md

@@ -0,0 +1,151 @@
+---
+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
+---
+
+## 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"
+
+---
+
+## Prerequisites
+
+- [ ] `sungen figma auth check` succeeds — PAT is stored and valid
+- [ ] Figma file URL is available (shared file or frame link)
+- [ ] If auth missing → run `sungen figma auth set` and follow the walkthrough
+
+**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:
+
+| 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 |
+
+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):
+
+### 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:
+
+```
+┌──────────────────────────────────────┐
+│ [Logo]                     [Sign In] │
+├──────────────────────────────────────┤
+│  Welcome back                        │
+│  ┌────────────────────────────────┐  │
+│  │ email@example.com              │  │
+│  └────────────────────────────────┘  │
+│  [ Continue ]                        │
+└──────────────────────────────────────┘
+```
+
+### 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.
+
+### 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:
+
+```
+- **<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.
+
+```
+| Label | Type | Required | Placeholder |
+|---|---|---|---|
+```
+
+Omit entirely (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_`.
+
+### 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.
+
+---
+
+## 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`
+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 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
+- 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:
+
+| Figma Signal | Provisional YAML Entry |
+|---|---|
+| Node name ends `Button`, has text | `role: button` + `name: "<text>"` |
+| Node name ends `Input`/`Field` | `placeholder: "<placeholder text>"` |
+| Node name ends `Link`, has text | `role: link` + `name: "<text>"` |
+| componentProperties has `data-testid` | `testid: <value>` |
+| Plain text leaf (outside interactive) | `text: "<content>"` |
+| 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
+- Never log or echo the PAT in terminal output
+- Read only from `.sungen/figma-cache/` and screen directories — never from `.env`

package/dist/orchestrator/templates/ai-instructions/claude-skill-tc-generation.md

@@ -6,14 +6,25 @@ user-invocable: false
 
 ## Goal
 
-Generate **focused test cases per screen section** with **20+ scenarios per viewpoint**. Output `.feature` + `test-data.yaml` only — selectors are deferred to `/sungen:run-test`.
+Generate **focused test cases per screen section** using a **tier-based approach** for faster results. Output `.feature` + `test-data.yaml` only — selectors are deferred to `/sungen:run-test`.
+
+### Tier System
+
+| Tier | Priority | What to generate | When |
+|---|---|---|---|
+| **Tier 1** (default) | `@critical` + `@high` | Happy paths, required validation, core business rules, security basics | First run of `create-test` |
+| **Tier 2** (expand) | `@normal` + `@low` | UI presence, optional validation, edge cases, cosmetic checks | User runs `create-test` again with "Add viewpoints" mode |
+
+**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior.
+
+**Round 2 (Tier 2)** expands to full coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
 
 ## Update Mode
 
 When `.feature` already has scenarios, summarize and ask:
-1. **Add new sections** — append, continue numbering
-2. **Add viewpoints** — add to existing sections
-3. **Replace all** — overwrite
+1. **Add new sections** — append new sections with Tier 2 (`@normal` + `@low`) scenarios, continue numbering
+2. **Add viewpoints** — expand existing sections with Tier 2 (`@normal` + `@low`) scenarios
+3. **Replace all** — overwrite with fresh Tier 1 (`@critical` + `@high`) generation
 
 For append: read highest `VP-<CAT>-<NNN>`, continue from next number. Never modify existing scenarios.
 
@@ -30,12 +41,13 @@ If also exploring live page: verify spec vs actual, flag mismatches, capture exa
 
 ## Screen Input Sources
 
-**Recommended** (in priority order):
-1. **Figma designs** — use Figma MCP to read design context, screenshots, and component metadata
-2. **UI images** — screenshots or mockups in `qa/screens/<screen>/requirements/ui/`
-3. **`spec.md`** — written specification with sections, fields, validation rules
+**Auto-detect** — the parent command (`create-test`) resolves visual sources before invoking this skill. By the time generation starts, the available sources are already determined:
+- `spec.md` — primary, always read if present
+- `spec_figma.md` — Figma supplement, read if present (PAT flow already completed)
+- `ui/*.png` — visual context, read if present
+- `test-viewpoint.md` — edge cases and known issues, read if present
 
-**Optional**: **Live page scan** via Playwright MCP — useful to verify specs vs actual UI, capture real data (error messages, labels). If auth needed → ask user to log in manually via MCP browser.
+**IMPORTANT:** If `spec_figma.md` exists, do NOT call any `mcp__figma__*` tool. The PAT flow is complete — just read the file.
 
 **Single screen focus**: one URL = one screen. Don't explore sibling paths. Modals on same page = part of this screen.
 
@@ -76,7 +88,9 @@ Apply `sungen-test-design-techniques` to spec-extracted conditions:
 
 Use `sungen-viewpoint` skill for per-pattern checklists across 4 viewpoints: UI/UX, Data & Validate, Logic, Security.
 
-Add scenarios for generic UI coverage that spec didn't explicitly state (empty states, loading states, keyboard nav, hover effects). Skip viewpoints truly N/A.
+**Tier-aware gap filling:**
+- **Tier 1 (first run)**: only add `@critical` and `@high` items from the checklists — core security checks (VP-SEC), required field validation (VP-VAL), key state transitions (VP-LOGIC). Skip `@normal`/`@low` items like hover states, empty states, tooltips.
+- **Tier 2 (expand run)**: add `@normal` + `@low` scenarios — UI presence, optional validation, edge cases, cosmetic checks, keyboard nav, hover effects.
 
 **Validation rule**: capture actual error messages from live page or spec.md. Use `User see {{error_var}}` — never assert just "is visible".
 
@@ -168,13 +182,14 @@ Feature: <Screen> Screen
     When User click [Create] button
     Then User see [Form] dialog
 
-  # --- Section: Create User Form ---
+  # --- Section: Create User Form (Tier 1: @critical + @high) ---
 
-  @normal @extend:open_form
-  Scenario: VP-UI-001 Form displays all fields with correct defaults
+  @critical @extend:open_form
+  Scenario: VP-LOGIC-001 Submit form with valid data creates record
     Given User is on [Form] dialog
-    Then User see [Name] field
-    And User see [Submit] button is disabled
+    When User fill [Name] field with {{valid_name}}
+    And User click [Submit] button
+    Then User see {{success_message}} message
 
   @high @extend:open_form
   Scenario: VP-VAL-001 Submit with all empty fields shows errors
@@ -182,19 +197,23 @@ Feature: <Screen> Screen
     When User click [Submit] button
     Then User see [Name error] message with {{name_required_error}}
 
-  # --- Section: User Table ---
-
-  @normal
-  Scenario: VP-UI-010 Table displays all columns
-    Then User see [Name] column in [Users] table
+  # --- Section: User Table (Tier 1: @critical + @high) ---
 
   @high
   Scenario: VP-VAL-010 Table displays correct data
     Then User see [Users] table match data:
       | Name       | Email        |
       | {{name_1}} | {{email_1}}  |
+
+  @critical
+  Scenario: VP-SEC-010 Unauthorized user cannot access page
+    Given User is not logged in
+    When User navigate to [Screen] page
+    Then User is on [Login] page
 ```
 
+**Tier 2 (expand run)** adds `@normal` + `@low` scenarios like UI field presence, hover states, tooltips, empty states.
+
 ### When to use DataTable vs Row Scope
 
 | Pattern | Use when |

package/dist/orchestrator/templates/ai-instructions/claude-skill-tc-review.md

@@ -43,6 +43,8 @@ Score: `(dimensions_covered / 6) * 40`. Validate technique application with `sun
 
 **Classification**: UI = static/always-same appearance. VAL = input validation/errors. LOGIC = behavior/state changes (includes persisted state without When). SEC = auth/permissions.
 
+**Tier-aware scoring**: If the feature file only contains `@critical` + `@high` scenarios (Tier 1), do NOT penalize for missing VP-UI viewpoint — UI scenarios are intentionally deferred to Tier 2. Score "All applicable VP present" based on Tier 1-relevant viewpoints only (VAL, LOGIC, SEC). Note in the review output: *"VP-UI deferred to Tier 2 — run `/sungen:create-test` with 'Add viewpoints' to expand."*
+
 ---
 
 ## Quality Rules