qfai 1.8.4 → 1.8.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (57) hide show
  1. package/README.md +17 -5
  2. package/assets/init/.qfai/assistant/agents/acceptance-test-engineer.md +6 -0
  3. package/assets/init/.qfai/assistant/agents/architecture-reviewer.md +6 -2
  4. package/assets/init/.qfai/assistant/agents/backend-engineer.md +6 -3
  5. package/assets/init/.qfai/assistant/agents/completion-reviewer.md +6 -0
  6. package/assets/init/.qfai/assistant/agents/delivery-planner.md +6 -0
  7. package/assets/init/.qfai/assistant/agents/devops-ci-engineer.md +6 -0
  8. package/assets/init/.qfai/assistant/agents/discovery-analyst.md +6 -0
  9. package/assets/init/.qfai/assistant/agents/doc-steward.md +6 -0
  10. package/assets/init/.qfai/assistant/agents/frontend-engineer.md +6 -3
  11. package/assets/init/.qfai/assistant/agents/implementation-reviewer.md +6 -1
  12. package/assets/init/.qfai/assistant/agents/orchestrator.md +6 -0
  13. package/assets/init/.qfai/assistant/agents/product-experience-architect.md +6 -2
  14. package/assets/init/.qfai/assistant/agents/product-surface-reviewer.md +11 -2
  15. package/assets/init/.qfai/assistant/agents/qa-gatekeeper.md +6 -0
  16. package/assets/init/.qfai/assistant/agents/qa-strategist.md +6 -0
  17. package/assets/init/.qfai/assistant/agents/requirements-analyst.md +6 -0
  18. package/assets/init/.qfai/assistant/agents/requirements-reviewer.md +6 -0
  19. package/assets/init/.qfai/assistant/agents/solution-architect.md +6 -2
  20. package/assets/init/.qfai/assistant/agents/test-design-analyst.md +6 -0
  21. package/assets/init/.qfai/assistant/instructions/shared-skill-operating-baseline.md +13 -0
  22. package/assets/init/.qfai/assistant/skills/qfai-atdd/SKILL.md +3 -0
  23. package/assets/init/.qfai/assistant/skills/qfai-configure/SKILL.md +1 -0
  24. package/assets/init/.qfai/assistant/skills/qfai-discussion/SKILL.md +7 -3
  25. package/assets/init/.qfai/assistant/skills/qfai-discussion/references/design-dna-intake.md +28 -0
  26. package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/31_reference_pool.md +6 -6
  27. package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/33_exploration_rubric.md +19 -0
  28. package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/34_evaluator_calibration.md +4 -0
  29. package/assets/init/.qfai/assistant/skills/qfai-implement/SKILL.md +13 -7
  30. package/assets/init/.qfai/assistant/skills/qfai-prototyping/SKILL.md +67 -202
  31. package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/design-differentiation.md +17 -0
  32. package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/evidence-requirements.md +9 -1
  33. package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/iteration-cycle.md +14 -3
  34. package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/l2-review-guide.md +2 -3
  35. package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/prototype-workspace.md +45 -0
  36. package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/surface-framing.md +38 -0
  37. package/assets/init/.qfai/assistant/skills/qfai-prototyping/templates/contracts/design-system.sample.yaml +19 -0
  38. package/assets/init/.qfai/assistant/skills/qfai-prototyping/templates/contracts/prototype-handoff.sample.yaml +38 -0
  39. package/assets/init/.qfai/assistant/skills/qfai-prototyping/templates/contracts/selected-direction.sample.yaml +8 -0
  40. package/assets/init/.qfai/assistant/skills/qfai-sdd/SKILL.md +5 -2
  41. package/assets/init/.qfai/assistant/skills/qfai-sdd/references/ui-design-contract-normalization.md +34 -0
  42. package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/contracts/brand-design.sample.yaml +20 -0
  43. package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/contracts/reference-pool.sample.yaml +15 -0
  44. package/assets/init/.qfai/assistant/skills/qfai-verify/SKILL.md +4 -1
  45. package/assets/init/.qfai/assistant/steering/ui-definition-protocol.md +53 -49
  46. package/assets/init/.qfai/contracts/design/README.md +10 -7
  47. package/dist/cli/index.cjs +3230 -1676
  48. package/dist/cli/index.cjs.map +1 -1
  49. package/dist/cli/index.mjs +3078 -1524
  50. package/dist/cli/index.mjs.map +1 -1
  51. package/dist/index.cjs +1116 -290
  52. package/dist/index.cjs.map +1 -1
  53. package/dist/index.mjs +1089 -263
  54. package/dist/index.mjs.map +1 -1
  55. package/package.json +1 -1
  56. package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/contracts/design-system.sample.yaml +0 -22
  57. package/assets/init/.qfai/assistant/skills/qfai-sdd/templates/contracts/selected-direction.sample.yaml +0 -7
package/README.md CHANGED
@@ -17,8 +17,7 @@ The agent reads the repository, produces the required artifacts, and iterates un
17
17
 
18
18
  ## Release status
19
19
 
20
- - Current package version: `1.7.15`
21
- - Release posture: v1.7.15 enforces runtime truthfulness.
20
+ - Release posture: runtime truthfulness is enforced.
22
21
  - Prototyping is UI-only; `full-harness` is measurement-driven iteration accumulation for UI-bearing surfaces only.
23
22
  - Runtime observation is observed-only (no synthetic 200 / API / DB prototyping coverage).
24
23
  - Browser QA is mandatory per screen in full-harness, and `actionsWired` reports action coverage rather than finding count.
@@ -57,8 +56,18 @@ npx qfai report
57
56
  - Produces a human-readable report (`report.md` by default) or an internal JSON export (`report.json`) from `validate.json`; use `--base-url` to link file paths in Markdown to your repository viewer.
58
57
  - `npx qfai doctor`
59
58
  - Diagnoses configuration discovery, path resolution, glob scanning, and `validate.json` inputs before running validate/report; use `--fail-on` to enforce failures in CI.
59
+ Use `--profile prototyping` to add prototyping-specific preflight checks for the
60
+ primary spec, UI contracts, design contract readiness, active agent-wrapper
61
+ integrations, shipped role-input readiness, Playwright CLI launcher
62
+ resolution/probing, and target URL reachability.
60
63
  Note: prototyping evidence (`.qfai/evidence/prototyping.json`) is produced by the AI workflow / skills
61
64
  (`/qfai-prototyping` — any mode; modes differ only in `maxCycles`, see spec-0012), not by a general-purpose end-user CLI flow.
65
+ Use `npx qfai prototyping preflight --target-url <url>` for a focused
66
+ prototyping preflight before the skill starts; it now surfaces blocking
67
+ `QFAI-DCON-*` design-contract issues alongside runtime assumptions, resolves
68
+ a runnable Playwright CLI launcher (project wrapper / local bin / PATH /
69
+ `npx --no-install`), and still treats the first real delegation failure as a
70
+ runtime hard-stop.
62
71
  Use `npx qfai prototyping round-start --round <r5|r3|r2|r1> --candidates <csv> --target-url <url> --mode <mode>`
63
72
  to generate the round-scoped review bundle and command plans the AI evaluator sub-agent consumes, then use
64
73
  `round-harvest`, `round-narrow`, `round-absorb`, and `round-reimplement-verify` to advance the candidate funnel.
@@ -220,9 +229,9 @@ Notes.
220
229
  - `validate.json`, `report.json`, `doctor.json`, and `run-*` JSON logs are internal exports and are not a stable external contract; prefer `report.md` for integrations that must survive tool upgrades.
221
230
  - Scenario files are expected to use the Gherkin extension `*.feature` (not `*.md`).
222
231
  - `prototyping.calibration.packPath` points to the calibration pack SSOT; runtime and validator both resolve thresholds and iteration parameters from that pack.
223
- - `prototyping.calibration.thresholds`, `maxIterations`, `plateauDelta`, and `plateauLookback` are unsupported public config fields in v1.7.15.
232
+ - `prototyping.calibration.thresholds`, `maxIterations`, `plateauDelta`, and `plateauLookback` are unsupported public config fields.
224
233
  Put calibration values in the referenced pack instead of `qfai.config.yaml`.
225
- - Observability modules (`src/core/observability/`) exist as foundation code but are **not integrated into blocking validation** in v1.7.14. They are reserved for future operational instrumentation.
234
+ - Observability modules (`src/core/observability/`) exist as foundation code but are **not yet integrated into blocking validation**. They are reserved for future operational instrumentation.
226
235
 
227
236
  ## Specifications and contracts (SDD)
228
237
 
@@ -251,7 +260,7 @@ flowchart LR
251
260
  - Contracts SSOT: `.qfai/contracts/**`
252
261
  - Report outputs (`.qfai/report/**`) are derived artifacts and not SSOT.
253
262
 
254
- ## Minimal tutorial (v1.7.7)
263
+ ## Minimal tutorial
255
264
 
256
265
  1. `npx qfai init`
257
266
  2. Run `/qfai-discussion` to structure scope, open questions, and produce a discussion pack under `.qfai/discussion/discussion-<ts>/`.
@@ -424,6 +433,9 @@ Integration wrappers are also generated for immediate use:
424
433
 
425
434
  `npx qfai init` installs canonical skills under `.qfai/assistant/skills/**` (SSOT)
426
435
  and generates thin wrapper assets for Agents/Codex VS Code / Copilot / Claude Code / Codex.
436
+ Canonical agent markdown under `.qfai/assistant/agents/**` uses a shared YAML frontmatter
437
+ subset (`name`, `description`, `tools`) compatible with Claude Code and GitHub Copilot,
438
+ while Codex consumes mirrored `.codex/agents/*.toml` profiles.
427
439
  If wrapper assets drift from canonical skills, rerun `npx qfai init --force` to resync.
428
440
 
429
441
  ## Contributing (for QFAI maintainers)
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: acceptance-test-engineer
3
+ description: "Implement E2E, API, and integration acceptance coverage with explicit traceability."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Acceptance Test Engineer
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: architecture-reviewer
3
+ description: "Review architecture and contract decisions for consistency, safety, and rejected-option protection."
4
+ tools: [Read, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Architecture Reviewer
2
8
 
3
9
  ## Mission
@@ -22,8 +28,6 @@
22
28
  - .qfai/specs/spec-\*/09_delta.md
23
29
  - .github/instructions/code-review.instructions.md
24
30
  - .github/instructions/principles.instructions.md
25
- - .instruction/00_universal/development-principles-checklist.md
26
- - .instruction/01_specialties/design.md
27
31
  - Architecture decisions, diagrams, and `.qfai/contracts/**`
28
32
 
29
33
  ## Deliverables
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: backend-engineer
3
+ description: "Implement backend behavior aligned with specs, API and DB contracts, and operational constraints."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Backend Engineer
2
8
 
3
9
  ## Mission
@@ -21,9 +27,6 @@
21
27
  - .qfai/specs/spec-\*/09_delta.md
22
28
  - .qfai/specs/spec-\*/01_Spec.md
23
29
  - .github/instructions/principles.instructions.md
24
- - .instruction/00_universal/development-principles-checklist.md
25
- - .instruction/01_specialties/implementation.md
26
- - .instruction/01_specialties/design.md
27
30
  - .qfai/contracts/api/\*\*
28
31
  - .qfai/contracts/db/\*\*
29
32
 
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: completion-reviewer
3
+ description: "Independently audit completion contract, prompt DoD, and drift-protocol compliance."
4
+ tools: [Read, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Completion Reviewer
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: delivery-planner
3
+ description: "Create phased delivery plans, ownership splits, risk controls, and rerun policies."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Delivery Planner
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: devops-ci-engineer
3
+ description: "Run quality gates and capture reproducible CI and runtime evidence."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # DevOps CI Engineer
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: discovery-analyst
3
+ description: "Gather pre-knowledge, ask focused questions, and facilitate decision-making."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Discovery Analyst
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: doc-steward
3
+ description: "Keep docs, changelog, and migration notes synchronized with implementation and workflow changes."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Doc Steward
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: frontend-engineer
3
+ description: "Implement frontend behavior aligned with the selected direction, finalized design system, screen contracts, and product experience decisions."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Frontend Engineer
2
8
 
3
9
  ## Mission
@@ -20,9 +26,6 @@
20
26
  - .qfai/specs/spec-\*/09_delta.md
21
27
  - .qfai/specs/spec-\*/01_Spec.md
22
28
  - .github/instructions/principles.instructions.md
23
- - .instruction/00_universal/development-principles-checklist.md
24
- - .instruction/01_specialties/implementation.md
25
- - .instruction/01_specialties/design.md
26
29
  - .qfai/contracts/ui/\*\*
27
30
  - UI evidence artifacts when available
28
31
 
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: implementation-reviewer
3
+ description: "Review code changes for correctness, maintainability, backend safety, and implementation risk."
4
+ tools: [Read, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Implementation Reviewer
2
8
 
3
9
  ## Mission
@@ -23,7 +29,6 @@
23
29
  - .qfai/specs/spec-\*/09_delta.md
24
30
  - .github/instructions/code-review.instructions.md
25
31
  - .github/instructions/principles.instructions.md
26
- - .instruction/00_universal/development-principles-checklist.md
27
32
  - Diff of changed files
28
33
  - `.qfai/contracts/api/**` and `.qfai/contracts/db/**`
29
34
 
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: orchestrator
3
+ description: "Plan, delegate, integrate, and enforce stage gates without self-authoring."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Orchestrator
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: product-experience-architect
3
+ description: "Own UX, visual design, navigation, screen transitions, and integrated experience direction."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Product Experience Architect
2
8
 
3
9
  ## Mission
@@ -22,8 +28,6 @@
22
28
  - .qfai/specs/spec-\*/09_delta.md
23
29
  - .qfai/specs/spec-\*/01_Spec.md
24
30
  - .github/instructions/principles.instructions.md
25
- - .instruction/00_universal/development-principles-checklist.md
26
- - .instruction/01_specialties/design.md
27
31
  - Exploration brief, reference pool, evaluation rubric, evaluator calibration, selected direction, finalized design system,
28
32
  screen contracts, optional tokens, optional fallback HTML/CSS mock, and Mermaid flows
29
33
  - Runtime screenshots or rendered evidence when available
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: product-surface-reviewer
3
+ description: "Review UI implementation, usability, design coherence, and service-level product-surface quality."
4
+ tools: [Read, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Product Surface Reviewer
2
8
 
3
9
  ## Mission
@@ -11,6 +17,10 @@
11
17
  - Audit visual design, token alignment, and service-level UX coherence.
12
18
  - Reconcile sidecar artifacts (selected anchor, strategy, screen contracts), design tokens, mermaid flows, and rendered output consistency.
13
19
  HTML mock is optional fallback evidence only. Design tokens are supporting input.
20
+ - For UI implementation, compare rendered output against `.qfai/contracts/design/prototype-handoff.yaml`, canonical prototype screenshots, HTML snapshots, and `.qfai/prototypes/winner/index.html`.
21
+ - Reject prototype parity when implementation loses CTA hierarchy, spacing rhythm, information density,
22
+ surface framing intent, transition clarity, state coverage, or component character captured by the winning
23
+ prototype.
14
24
  - Review UI changes for KISS and YAGNI at the surface layer: avoid needless states, controls, flows, animations, and configuration that are not justified by the product goal.
15
25
  - Check naming, structure, and responsibility split of UI components for clarity, cohesion, and minimal surprise.
16
26
  - Validate docs/UX consistency so usage text, labels, error states, and user flows match the intended product behavior.
@@ -24,9 +34,8 @@
24
34
  - .qfai/specs/spec-\*/09_delta.md
25
35
  - .github/instructions/code-review.instructions.md
26
36
  - .github/instructions/principles.instructions.md
27
- - .instruction/00_universal/development-principles-checklist.md
28
- - .instruction/01_specialties/design.md
29
37
  - UI contract files under `.qfai/contracts/ui/`
38
+ - Prototype handoff contract under `.qfai/contracts/design/prototype-handoff.yaml` when available
30
39
  - Runtime screenshots / HTML evidence / relevant diffs
31
40
 
32
41
  ## Deliverables
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: qa-gatekeeper
3
+ description: "Enforce validate, coverage, runtime-proof, and prototyping evidence gates before completion."
4
+ tools: [Read, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # QA Gatekeeper
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: qa-strategist
3
+ description: "Own QA strategy, quality posture, traceability expectations, and failure-handling design."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # QA Strategist
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: requirements-analyst
3
+ description: "Produce testable requirements, option sets, and explicit open-question ledgers."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Requirements Analyst
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: requirements-reviewer
3
+ description: "Review requirements, options, and open-question handling for completeness, neutrality, and safe deferral."
4
+ tools: [Read, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Requirements Reviewer
2
8
 
3
9
  ## Mission
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: solution-architect
3
+ description: "Define architecture and contract decisions aligned with specs, constraints, and rejected-option history."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Solution Architect
2
8
 
3
9
  ## Mission
@@ -23,8 +29,6 @@
23
29
  - .qfai/discussion/discussion-\*/04_Sources.md
24
30
  - .qfai/discussion/discussion-\*/06_REQ.md
25
31
  - .github/instructions/principles.instructions.md
26
- - .instruction/00_universal/development-principles-checklist.md
27
- - .instruction/01_specialties/design.md
28
32
  - Existing architecture docs and `.qfai/contracts/**`
29
33
 
30
34
  ## Deliverables
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: test-design-analyst
3
+ description: "Define test structure, coverage obligations, traceability, and test-scope boundaries."
4
+ tools: [Read, Write, Edit, Glob, Grep, Bash]
5
+ ---
6
+
1
7
  # Test Design Analyst
2
8
 
3
9
  ## Mission
@@ -39,6 +39,19 @@ Rules:
39
39
  - Do not reintroduce options marked as rejected in `09_delta.md`.
40
40
  - If a rejected option must be reconsidered, create a `[RE-OPEN]` decision record that references the prior DR-ID, states what changed, and includes explicit approval.
41
41
 
42
+ ## Gate Failure Autorepair Protocol
43
+
44
+ When validate, doctor, test, lint, typecheck, build, capture, or report gates fail:
45
+
46
+ - inspect exit code, logs, `validate.json`, and cited files before reporting;
47
+ - classify each finding as skill-owned artifact, upstream spec/contract, code/test defect, environment/tooling, or user decision;
48
+ - fix skill-owned artifacts and code/test defects autonomously when the fix is local and non-destructive;
49
+ - rerun the same failing gate after each fix batch;
50
+ - do not weaken profiles, lower `--fail-on`, waive errors, invent evidence, or skip required reviewers;
51
+ - stop only for destructive changes, ambiguous product/spec decisions, missing permissions/tools, or repeated no-progress failures.
52
+
53
+ When stopping, report: cause, attempted fixes, remaining blocker, user action, and retry gate.
54
+
42
55
  ## Completion Contract (Shared)
43
56
 
44
57
  Before declaring completion, you MUST:
@@ -60,6 +60,8 @@ When unsure, read inputs in this order:
60
60
  - `.qfai/specs/<spec-id>/scenario.feature`
61
61
  - coverage ledger files
62
62
 
63
+ Do not read discussion-pack UI/UX sidecars. UI-bearing acceptance tests consume only specs and contracts normalized by `/qfai-sdd`.
64
+
63
65
  ## Read Set Contract (Mandatory)
64
66
 
65
67
  - Default Mode:
@@ -162,6 +164,7 @@ Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#delta-re
162
164
  ## Completion Contract (Shared)
163
165
 
164
166
  Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#completion-contract-shared`.
167
+ Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#gate-failure-autorepair-protocol` for validate, doctor, and quality-gate failures.
165
168
 
166
169
  ## Goal
167
170
 
@@ -131,6 +131,7 @@ Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#delta-re
131
131
  ## Completion Contract (Shared)
132
132
 
133
133
  Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#completion-contract-shared`.
134
+ Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#gate-failure-autorepair-protocol` for validate, doctor, and quality-gate failures.
134
135
 
135
136
  ## Goal
136
137
 
@@ -64,17 +64,21 @@ UI-bearing packs must produce the following sidecars as primary truth:
64
64
  9. Generate `prototyping.yaml` only when the latest discussion pack is UI-bearing and an explicit prototyping recommendation is useful.
65
65
  10. Request review and record the Reviewer result.
66
66
 
67
+ For UI-bearing targets, follow `references/design-dna-intake.md` while authoring the UI/UX sidecars. Keep this `SKILL.md` compact; put detailed interview prompts and examples in the reference file.
68
+
67
69
  ## UI-bearing Authoring Requirements
68
70
 
69
71
  - `30_exploration_brief.md` must define product intent, must-preserve interactions, brand signals, and differentiation targets.
70
- - `31_reference_pool.md` must define exploration references, adopted points, rejected points, and local translation.
72
+ - `31_reference_pool.md` must define exploration references, adopted points, rejected points, local translation, copy risk, and template usage policy.
71
73
  - `32_design_anti_goals.md` must contain explicit anti-goals and recurrence prevention notes.
72
- - `33_exploration_rubric.md` must define design quality, originality, craft, and functionality grading criteria.
73
- - `34_evaluator_calibration.md` must include good critique examples, too-lenient examples, blandness-fail examples, and originality-fail examples.
74
+ - `33_exploration_rubric.md` must define design quality, originality, craft, functionality, brand memorability, category distinctiveness, template dependency risk, and localization-fit grading criteria.
75
+ - `34_evaluator_calibration.md` must include good critique examples, too-lenient examples, blandness-fail examples, originality-fail examples, and template-copy fail examples.
74
76
  - `50_review_input_bundle.md` must document best-of-history handling so later iterations are not automatically preferred.
75
77
 
76
78
  ## Completion Contract (Shared)
77
79
 
80
+ Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#gate-failure-autorepair-protocol` for validate, doctor, and quality-gate failures.
81
+
78
82
  Before declaring completion, you MUST:
79
83
 
80
84
  - verify all 15 mandatory output files exist and are populated;
@@ -0,0 +1,28 @@
1
+ # Design DNA Intake
2
+
3
+ Use this reference only for UI-bearing discussion packs.
4
+
5
+ ## Interview Targets
6
+
7
+ - Brand personality: list 3-5 traits the product should express.
8
+ - Audience emotion: define what users should feel after the primary task.
9
+ - Category conventions: name the expected layout and interaction patterns for this market.
10
+ - Differentiation targets: state what must feel unlike generic SaaS, generic shadcn, or direct competitors.
11
+ - Anti-template constraints: name default visual patterns that must not survive into prototyping.
12
+ - Reference strategy: collect competitor, adjacent, aspirational, template-seed, and anti-pattern references.
13
+
14
+ ## Reference Rules
15
+
16
+ - Treat templates as seeds, not winners.
17
+ - Capture both adopted and rejected points for every reference.
18
+ - Translate references into local product rules instead of copying visual surfaces.
19
+ - Record copy risk as `low`, `medium`, or `high`.
20
+ - Record template usage policy as `none`, `reference-only`, or `implementation-seed`.
21
+
22
+ ## Output Mapping
23
+
24
+ - Put product intent and brand signals in `30_exploration_brief.md`.
25
+ - Put all reference decisions in `31_reference_pool.md`.
26
+ - Put prohibited visual directions in `32_design_anti_goals.md`.
27
+ - Put brand and template-risk scoring in `33_exploration_rubric.md`.
28
+ - Put examples of good critique and weak critique in `34_evaluator_calibration.md`.
@@ -2,12 +2,12 @@
2
2
 
3
3
  ## Exploration References
4
4
 
5
- | Ref | Type | Why it matters | Adopted points | Rejected points | Local translation |
6
- | ------- | ------- | -------------- | -------------- | --------------- | ----------------- |
7
- | REF-001 | Product | [why] | [adopted] | [rejected] | [translation] |
5
+ | Ref | Kind | Source URL | Why it matters | Adopted points | Rejected points | Local translation | Copy risk | Template usage policy |
6
+ | ------- | ---------- | ----------- | -------------- | -------------- | --------------- | ----------------- | --------- | --------------------- |
7
+ | REF-001 | competitor | https://... | ... | ... | ... | ... | medium | reference-only |
8
8
 
9
9
  ## Design Guideline Research
10
10
 
11
- | Ref | Guideline | Rule refs | Why it matters | Local translation |
12
- | ------ | ----------- | ----------- | -------------- | ----------------- |
13
- | GL-001 | [guideline] | [rule refs] | [why] | [translation] |
11
+ | Ref | Guideline | Rule refs | Why it matters | Local translation |
12
+ | ------ | --------- | --------- | -------------- | ----------------- |
13
+ | GL-001 | ... | ... | ... | ... |
@@ -25,3 +25,22 @@
25
25
  ## Implementation Plausibility
26
26
 
27
27
  - What level of complexity is acceptable for the current slice:
28
+
29
+ ## Brand Memorability
30
+
31
+ - What makes the screen recognizable after one use:
32
+ - What makes it forgettable:
33
+
34
+ ## Category Distinctiveness
35
+
36
+ - Which category conventions are intentionally kept:
37
+ - Which category conventions are intentionally broken:
38
+
39
+ ## Template Dependency Risk
40
+
41
+ - What indicates an unmodified shadcn/Tailwind/template surface:
42
+ - What local translation is required before passing:
43
+
44
+ ## Localization Fit
45
+
46
+ - How language length, density, and domain terms affect the design:
@@ -15,3 +15,7 @@
15
15
  ## Originality Fail
16
16
 
17
17
  - Example of a design that copies defaults without deliberate product-specific choices:
18
+
19
+ ## Template Copy Fail
20
+
21
+ - Example of a shadcn/Tailwind/template-derived design that keeps default tokens, rhythm, or component composition without local translation:
@@ -78,11 +78,14 @@ Execute the TDD micro-cycle for each pending item in `test-list.md`, transitioni
78
78
  - Read spec + contract inputs first whenever implementation touches UI or critique-driven behavior.
79
79
  - Read order: `01_Spec.md` → `03_Acceptance-Criteria.md` → `05_Examples.md` →
80
80
  `.qfai/contracts/design/exploration-brief.yaml` →
81
- `.qfai/contracts/design/anchor-selection.yaml` (legacy alias, when present)
82
- `.qfai/contracts/design/evaluation-axes.yaml` (legacy alias, when present) →
81
+ `.qfai/contracts/design/reference-pool.yaml` `.qfai/contracts/design/brand-design.yaml`
83
82
  `.qfai/contracts/design/evaluation-rubric.yaml` → `.qfai/contracts/design/evaluator-calibration.yaml` →
84
- `.qfai/contracts/design/selected-direction.yaml` → `.qfai/contracts/design/design-system.yaml` → `.qfai/contracts/ui/*.yaml` →
85
- optional design tokens optional fallback mock mermaid flows.
83
+ `.qfai/contracts/design/selected-direction.yaml` → `.qfai/contracts/design/design-system.yaml` →
84
+ `.qfai/contracts/design/prototype-handoff.yaml``.qfai/contracts/ui/*.yaml`
85
+ canonical prototype screenshots / HTML snapshots → `.qfai/prototypes/winner/index.html`.
86
+ - Do not read discussion-pack UI/UX sidecars, fallback mocks, or legacy design aliases.
87
+ - Prototype code is analysis input, not production source. Reimplement with project-native patterns while preserving `prototype-handoff.yaml` `mustPreserve`; adapt `mayAdapt`; do not copy `mustNotCopy`.
88
+ - UI-affecting items require product-surface-reviewer prototype parity review before `done`.
86
89
  - If code intent and rendered output diverge, treat the rendered/HTML result as the blocking review input and reconcile before DONE.
87
90
 
88
91
  ## Non-goals
@@ -253,8 +256,9 @@ Use the shared schema (per-row `Status (PASS/REVISE)` column, reviewer response
253
256
  ## Completion Contract (Shared)
254
257
 
255
258
  Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#completion-contract-shared`.
259
+ Follow `.qfai/assistant/instructions/shared-skill-operating-baseline.md#gate-failure-autorepair-protocol` for validate, doctor, and quality-gate failures.
256
260
 
257
- ### Item completion checklist (10-point gate)
261
+ ### Item completion checklist (11-point gate)
258
262
 
259
263
  An item in `test-list.md` may transition to `done` only when ALL of the following are satisfied:
260
264
 
@@ -266,8 +270,9 @@ An item in `test-list.md` may transition to `done` only when ALL of the followin
266
270
  6. Refactor was performed and GREEN was re-confirmed after refactor
267
271
  7. `completion-reviewer` returned PASS (spec / completion review gate)
268
272
  8. `implementation-reviewer` returned PASS (code quality review gate)
269
- 9. `test-list.md` Status and Evidence columns are updated with fresh evidence
270
- 10. Checkpoint verification passed
273
+ 9. UI-affecting items have prototype parity PASS from `product-surface-reviewer`
274
+ 10. `test-list.md` Status and Evidence columns are updated with fresh evidence
275
+ 11. Checkpoint verification passed
271
276
 
272
277
  ### Spec completion conditions
273
278
 
@@ -317,6 +322,7 @@ Each TDD item MUST have fresh evidence containing at minimum:
317
322
  - `Refactor verify result` — the output confirming GREEN is maintained
318
323
  - `Spec review` — completion-reviewer result (PASS or FAIL)
319
324
  - `Code quality review` — implementation-reviewer result (PASS or FAIL)
325
+ - `Prototype parity` — product-surface-reviewer result for UI-affecting items (PASS or REVISE)
320
326
 
321
327
  ### Evidence hard rules
322
328