Findings are tagged P0-P3 (Blocking / Major / Minor / Polish) and reported individually — there is NO aggregate score, health score, or letter grade, ever; an aggregated number invites self-grading theater.
The visual review is a bounded loop, maximum 2 fix cycles: the loop exits PASS only once the register-applicable positive floors are actually met, and a plateau (cycle 2 repeating cycle 1's finding) stops immediately even at cycle 1 of 2.
Before any "done" claim, a mandatory in-loop challenger gate judges the deliverable blind — fresh-context, off a rendered PNG only, never fed this procedure's own reasoning. A Block from the challenger must be resolved or owner-accepted before "done" is reported.
Design Review — Final Quality Gate
When
After design-motion (web/webapp) or directly after the mockup (design-ios/
design-android). The last step before reporting any design deliverable done — never
skipped, never reported as passed if it wasn't actually run
(references/review-procedure.md Failure Handling).
Input
- The complete rendered artifact: components/mockup with animations (if any) and
interactive states.
design-system.md as the audit baseline (tokens, forbidden fonts, contrast floors).
- The
Je reproduis line written by design-web/design-webapp — three declared
elements, two tagged [corpus: {reference}/{tokens section}] (measured procedure,
the craft) and one tagged [sector: {url} — register] (register signal only;
[sector: none — register from brief] is valid, an empty slot is not). A missing or
untagged line is a blocking Part 1 finding — the binary verdict has no input without it.
- The corpus pages opened (Gate 0 artefact 3): at least two
{reference}-recode/index.html, named. The [corpus: …] tags prove the corpus was read,
never that it was seen — and a page sourced from markdown alone clears every mechanical
check and reads dead. Absent ⇒ blocking Part 1 finding.
- The on-screen inventory (Gate 0 artefact 4): what each section physically carries,
plus the screen-holding-floor verdict. Blocking when
VISUAL_DENSITY ≤ 3 or
DESIGN_VARIANCE ≥ 6; reported otherwise.
- Any declared premium pattern(s); the signature element (
design-method Step 2) instead
gets a Signature Dominance verdict.
- The plan's two structural picks — hero treatment
(
design-method/references/macrostructure-bank.md) and body sequence
(design-method/references/body-sequence-bank.md). A plan naming neither is itself a
detector signal (anti-slop entry 15). brand register; a product deliverable carries
neither.
- The register (
brand/product, from design-method Gate 0) — an input, never
inferred mid-review: check 14's floors, Part 2 item 8's floors and the Lookalike Test
(item 8b) all branch on it.
The two assessments — ISOLATED, never in the same head
This is the structural rule the whole procedure hangs on: the mechanical read and the
subjective read must not anchor on each other.
- Deterministic detection (
references/anti-ai-slop-audit.md +
references/pre-flight-checklist.md) — grep/count/compute, zero taste involved. Run
by design-expert itself; there is nothing to isolate here because there is no
judgment call to bias.
- Subjective visual review — screenshots, named elicitation techniques
(
references/elicitation-visual.md), Nielsen heuristics
(references/ux-nielsen.md), UX laws (references/ux-laws.md). This pass is run by
design-expert, so it is not yet independent — independence is delivered by the
mandatory challenger gate below, which judges blind, fresh-context, off the rendered
PNG only, never this procedure's own reasoning. Do not treat the elicitation-technique
pass alone as "isolated" — it isn't; the challenger is the isolation.
Never collapse these into one pass "to save a round" — that is exactly how the
cream/serif/terracotta cluster shipped through this audit once already (documented in
anti-ai-slop-audit.md Gate Semantics).
Part 1 — Deterministic Checks (mechanical, run first)
Full 15-item list is canonical in references/review-procedure.md Part 1 — contrast
(4.5:1 text / 3:1 UI, light+dark), forbidden fonts, OKLCH-only color format in the
produced code (corpus values arrive as hex/rgb — convert them, never drop them), em-dash
crutch (2+ occurrences), token adherence, the anti-AI-slop audit
(references/anti-ai-slop-audit.md, 15 detectors — including entry 15, the generic body
sequence: canonical order verbatim AND uniform vertical rhythm, a conjunction because the
canon treated is legitimate; clusters 9-11 are
FLAG-with-justification, not a block, if declared per design-method Step 2), the
mechanical pre-flight (references/pre-flight-checklist.md), WCAG beyond contrast
(references/ux-wcag.md), cross-component consistency (references/consistency-checks.md),
mobile nav functionality, doc↔code animation diff, integrity (no fabricated numbers/false
urgency), no-JS baseline, Type-Scale/Body-Size/Measure/Focal-Block floors, and
Dark-Elevation Direction. Any Critical/Major finding here is fixed before Part 2 runs.
Part 2 — Bounded Visual Review
Serve → screenshot per section + one full-page capture, light AND dark via
colorScheme → cross-viewport (mobile/tablet/desktop) → compare declared elements
(binary present/absent, no partial credit; signature element gets Signature Dominance) →
localized critique only (name the exact section/element, never "improve the style") →
motion verdict if any animation exists (references/motion-verdict.md, Before/After/Why
table + tiered impact + explicit Block/Approve) → cite at least two named techniques
from references/elicitation-visual.md (Squint / Subtraction / Competitor Line-up /
5-Second / Persona) → fix gaps → Lookalike Test, brand only / product exempt (item
8b — this procedure is the only executant of the test design-web declares; definition
canonical in design-web/references/design-inspiration.md, never restated here; binary
[distinguishable]/[indistinguishable], and an [indistinguishable] sends the page back
to the body sequence pick, never to a cosmetic tweak. On product it does not apply —
an app screen is supposed to share a silhouette with other app screens, Jakob's Law — and
the Domain-Specificity Floor (design-method/references/register/product.md §2) runs
in its slot instead, per design-webapp/SKILL.md). Full step-by-step:
references/review-procedure.md Part 2.
Bounded loop — maximum 2 fix cycles. The loop exits PASS only once the
register-applicable positive floors are actually met (not merely "0 flags"). Issues
(or an unmet floor) remaining after cycle 2 stop the loop and get reported, not
chased further. A plateau — cycle 2 repeating cycle 1's finding — stops immediately, even
at cycle 1 of 2. This is a hard cap, not a target to exceed when "almost there."
Findings — P0-P3, NO aggregate score, ever
Tag every finding with severity, never sum or average them into a total:
| Tier |
Meaning |
| P0 Blocking |
Prevents task completion / hard WCAG-A failure — fix immediately |
| P1 Major |
Significant difficulty or WCAG AA violation — fix before release |
| P2 Minor |
Annoyance, workaround exists — fix in next pass |
| P3 Polish |
Nice-to-fix, no real user impact — fix if time permits |
This maps onto references/audit-checklist.md's Critical/Major/Minor column
(Critical→P0, Major→P1, Minor→P2/P3 by impact) — but its "Scoring" section (letter grades
A-D) is not used here: it is superseded by this rule. No aggregate score, no health
score out of N, no letter grade — ever. Same Gate Semantics already enforced in
references/anti-ai-slop-audit.md and in design-method's critique.md/audit.md
moves: each finding stands PASS/FAIL or tier-tagged independently. An aggregated number
invites self-grading theater and has already failed once in this exact pipeline — don't
reintroduce it in the report format.
Challenger gate — mandatory, in-loop, not a trailing consultation
Before any "done" claim, design-expert invokes fuse-ai-pilot:challenger (it holds the
Task tool) to judge blind: PNG + a short brief, named elicitation lenses,
fresh-context — never this procedure's own reasoning fed in as the frame. A Block must be
resolved or owner-accepted before "done" (consultative verdict, not a veto — challenger
never overrides the owner). Fallback: only if Task/Agent is unavailable (agent at
max nesting depth 5) → report "not judged" / escalate to the owner, never a silent "done".
Full mechanics: references/review-procedure.md item 9.
Failure Handling
- All server ports 8899-8905 busy → stop, report the deliverable unreviewed, say so
explicitly — never report a validation that wasn't executed.
- Screenshot tool fails → retry once; on a second failure, stop and report the gap rather
than declaring the visual review passed.
Output
- Part 1 deterministic results, all Critical/Major resolved.
- Light/dark + 3-viewport screenshots (Part 2).
- Binary verdict per declared element/pattern, each cited with its
[corpus: …]/[sector: …]
tag; Signature Dominance for the signature element.
- Lookalike Test verdict (
brand), with the hero treatment and body sequence named — or
[n/a — product register; Domain-Specificity Floor run instead: {verdict}]. Never blank,
never "passed" by default.
- Motion Block/Approve verdict if applicable.
- Findings list, P0-P3, no aggregate score.
- Challenger verdict: resolved/owner-accepted, or "not judged" on tool-unavailable fallback.
- Any remaining Minor/P2-P3 issues after the 2-cycle cap, reported, not hidden.
Next → report to the owner. A P0/P1 unresolved or challenger-Blocked finding means
the deliverable is not "done" — say so plainly, don't soften it into "mostly ready."
References
| File |
Purpose |
references/review-procedure.md |
Canonical full procedure — Part 1/Part 2/challenger gate, step-by-step |
references/anti-ai-slop-audit.md |
Deterministic AI-slop detection, 15 entries, PASS/FAIL per entry (15 = generic body sequence) |
references/pre-flight-checklist.md |
Mechanical grep/count checks — last filter before audit-clean |
references/elicitation-visual.md |
Named visual techniques (Squint/Subtraction/Competitor/5-Second/Persona) |
references/audit-checklist.md |
Typography/color/spacing/motion/a11y checklist tables (ignore its Scoring section — superseded above) |
references/consistency-checks.md |
Cross-component border-radius/shadow/spacing coherence |
references/ux-wcag.md |
WCAG 2.2 AA beyond contrast (focus, touch targets, keyboard nav) |
references/ux-nielsen.md |
Nielsen's 10 usability heuristics |
references/ux-laws.md |
Laws of UX (Fitts, Hick, Miller) |
references/ux-patterns.md |
Form/validation/mobile UX implementation patterns |
references/motion-audit.md |
10 motion standards + delete-first remediation hierarchy |
references/motion-verdict.md |
Block/Approve verdict format for reviewed motion |
1---2name: design-review3description: "Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup."4when-to-use: "After design-motion (or directly after the mockup for design-ios/design-android) — the last step before reporting a design deliverable done. Also the target of design-method's critique.md and audit.md moves."5keywords: review, audit, critique, challenger, p0-p3, no-aggregate-score, wcag, anti-slop, contrast, lookalike-test, body-sequence, je-reproduis6priority: critical7related: design-method, design-motion, design-system, ux-copy8metadata:9 source: https://skillmd.com/skills/fusengine/design-review10---1112<objective>13The final quality gate before any design deliverable is reported done. Runs two assessments that must stay ISOLATED from each other — deterministic detection (grep/count/compute checks) is never performed in the same head as the subjective/visual read, because collapsing them into one pass is exactly how prior AI-slop clusters shipped through this audit undetected.1415Findings are tagged P0-P3 (Blocking / Major / Minor / Polish) and reported individually — there is NO aggregate score, health score, or letter grade, ever; an aggregated number invites self-grading theater.1617The visual review is a bounded loop, maximum 2 fix cycles: the loop exits PASS only once the register-applicable positive floors are actually met, and a plateau (cycle 2 repeating cycle 1's finding) stops immediately even at cycle 1 of 2.1819Before any "done" claim, a mandatory in-loop challenger gate judges the deliverable blind — fresh-context, off a rendered PNG only, never fed this procedure's own reasoning. A Block from the challenger must be resolved or owner-accepted before "done" is reported.20</objective>2122## Design Review — Final Quality Gate2324### When25After `design-motion` (web/webapp) or directly after the mockup (`design-ios`/26`design-android`). The last step before reporting any design deliverable done — never27skipped, never reported as passed if it wasn't actually run28(`references/review-procedure.md` Failure Handling).2930### Input31- The complete rendered artifact: components/mockup with animations (if any) and32 interactive states.33- `design-system.md` as the audit baseline (tokens, forbidden fonts, contrast floors).34- The `Je reproduis` line written by `design-web`/`design-webapp` — three declared35 elements, **two tagged `[corpus: {reference}/{tokens section}]`** (measured procedure,36 the craft) and **one tagged `[sector: {url} — register]`** (register signal only;37 `[sector: none — register from brief]` is valid, an empty slot is not). A missing or38 untagged line is a blocking Part 1 finding — the binary verdict has no input without it.39- **The corpus pages opened** (Gate 0 artefact 3): at least two40 `{reference}-recode/index.html`, named. The `[corpus: …]` tags prove the corpus was read,41 never that it was seen — and a page sourced from markdown alone clears every mechanical42 check and reads dead. Absent ⇒ blocking Part 1 finding.43- **The on-screen inventory** (Gate 0 artefact 4): what each section physically carries,44 plus the screen-holding-floor verdict. Blocking when `VISUAL_DENSITY` ≤ 3 or45 `DESIGN_VARIANCE` ≥ 6; reported otherwise.46- Any declared premium pattern(s); the signature element (`design-method` Step 2) instead47 gets a **Signature Dominance** verdict.48- The plan's two structural picks — hero treatment49 (`design-method/references/macrostructure-bank.md`) **and** body sequence50 (`design-method/references/body-sequence-bank.md`). A plan naming neither is itself a51 detector signal (anti-slop entry 15). `brand` register; a `product` deliverable carries52 neither.53- **The register** (`brand`/`product`, from `design-method` Gate 0) — an input, never54 inferred mid-review: check 14's floors, Part 2 item 8's floors and the Lookalike Test55 (item 8b) all branch on it.5657### The two assessments — ISOLATED, never in the same head58This is the structural rule the whole procedure hangs on: the mechanical read and the59subjective read must not anchor on each other.60611. **Deterministic detection** (`references/anti-ai-slop-audit.md` +62 `references/pre-flight-checklist.md`) — grep/count/compute, zero taste involved. Run63 by `design-expert` itself; there is nothing to isolate here because there is no64 judgment call to bias.652. **Subjective visual review** — screenshots, named elicitation techniques66 (`references/elicitation-visual.md`), Nielsen heuristics67 (`references/ux-nielsen.md`), UX laws (`references/ux-laws.md`). This pass is run by68 `design-expert`, so it is **not yet independent** — independence is delivered by the69 mandatory challenger gate below, which judges blind, fresh-context, off the rendered70 PNG only, never this procedure's own reasoning. Do not treat the elicitation-technique71 pass alone as "isolated" — it isn't; the challenger is the isolation.7273Never collapse these into one pass "to save a round" — that is exactly how the74cream/serif/terracotta cluster shipped through this audit once already (documented in75`anti-ai-slop-audit.md` Gate Semantics).7677### Part 1 — Deterministic Checks (mechanical, run first)78Full 15-item list is canonical in `references/review-procedure.md` Part 1 — contrast79(4.5:1 text / 3:1 UI, light+dark), forbidden fonts, OKLCH-only color format **in the80produced code** (corpus values arrive as hex/rgb — convert them, never drop them), em-dash81crutch (2+ occurrences), token adherence, the anti-AI-slop audit82(`references/anti-ai-slop-audit.md`, 15 detectors — including entry 15, the generic **body**83sequence: canonical order verbatim AND uniform vertical rhythm, a conjunction because the84canon *treated* is legitimate; clusters 9-11 are85FLAG-with-justification, not a block, if declared per `design-method` Step 2), the86mechanical pre-flight (`references/pre-flight-checklist.md`), WCAG beyond contrast87(`references/ux-wcag.md`), cross-component consistency (`references/consistency-checks.md`),88mobile nav functionality, doc↔code animation diff, integrity (no fabricated numbers/false89urgency), no-JS baseline, Type-Scale/Body-Size/Measure/Focal-Block floors, and90Dark-Elevation Direction. Any Critical/Major finding here is fixed before Part 2 runs.9192### Part 2 — Bounded Visual Review93Serve → screenshot per section + one full-page capture, light AND dark via94`colorScheme` → cross-viewport (mobile/tablet/desktop) → compare declared elements95(binary present/absent, no partial credit; signature element gets Signature Dominance) →96localized critique only (name the exact section/element, never "improve the style") →97motion verdict if any animation exists (`references/motion-verdict.md`, Before/After/Why98table + tiered impact + explicit Block/Approve) → cite at least **two** named techniques99from `references/elicitation-visual.md` (Squint / Subtraction / Competitor Line-up /1005-Second / Persona) → fix gaps → **Lookalike Test, `brand` only / `product` exempt** (item1018b — this procedure is the only executant of the test `design-web` declares; definition102canonical in `design-web/references/design-inspiration.md`, never restated here; binary103`[distinguishable]`/`[indistinguishable]`, and an `[indistinguishable]` sends the page back104to the **body sequence** pick, never to a cosmetic tweak. On `product` it does not apply —105an app screen is supposed to share a silhouette with other app screens, Jakob's Law — and106the **Domain-Specificity Floor** (`design-method/references/register/product.md` §2) runs107in its slot instead, per `design-webapp/SKILL.md`). Full step-by-step:108`references/review-procedure.md` Part 2.109110**Bounded loop — maximum 2 fix cycles.** The loop exits PASS only once the111register-applicable positive floors are actually **met** (not merely "0 flags"). Issues112(or an unmet floor) remaining after cycle 2 **stop the loop** and get reported, not113chased further. A plateau — cycle 2 repeating cycle 1's finding — stops immediately, even114at cycle 1 of 2. This is a hard cap, not a target to exceed when "almost there."115116### Findings — P0-P3, NO aggregate score, ever117Tag every finding with severity, never sum or average them into a total:118119| Tier | Meaning |120|---|---|121| **P0 Blocking** | Prevents task completion / hard WCAG-A failure — fix immediately |122| **P1 Major** | Significant difficulty or WCAG AA violation — fix before release |123| **P2 Minor** | Annoyance, workaround exists — fix in next pass |124| **P3 Polish** | Nice-to-fix, no real user impact — fix if time permits |125126This maps onto `references/audit-checklist.md`'s Critical/Major/Minor column127(Critical→P0, Major→P1, Minor→P2/P3 by impact) — but its "Scoring" section (letter grades128A-D) is **not used here**: it is superseded by this rule. **No aggregate score, no health129score out of N, no letter grade — ever.** Same Gate Semantics already enforced in130`references/anti-ai-slop-audit.md` and in `design-method`'s `critique.md`/`audit.md`131moves: each finding stands PASS/FAIL or tier-tagged independently. An aggregated number132invites self-grading theater and has already failed once in this exact pipeline — don't133reintroduce it in the report format.134135### Challenger gate — mandatory, in-loop, not a trailing consultation136Before any "done" claim, `design-expert` invokes `fuse-ai-pilot:challenger` (it holds the137`Task` tool) to judge **blind**: PNG + a short brief, named elicitation lenses,138fresh-context — never this procedure's own reasoning fed in as the frame. A Block must be139resolved or owner-accepted before "done" (consultative verdict, not a veto — challenger140never overrides the owner). **Fallback**: only if `Task`/`Agent` is unavailable (agent at141max nesting depth 5) → report "not judged" / escalate to the owner, never a silent "done".142Full mechanics: `references/review-procedure.md` item 9.143144### Failure Handling145- All server ports 8899-8905 busy → stop, report the deliverable unreviewed, say so146 explicitly — never report a validation that wasn't executed.147- Screenshot tool fails → retry once; on a second failure, stop and report the gap rather148 than declaring the visual review passed.149150### Output151- Part 1 deterministic results, all Critical/Major resolved.152- Light/dark + 3-viewport screenshots (Part 2).153- Binary verdict per declared element/pattern, each cited with its `[corpus: …]`/`[sector: …]`154 tag; Signature Dominance for the signature element.155- Lookalike Test verdict (`brand`), with the hero treatment and body sequence named — or156 `[n/a — product register; Domain-Specificity Floor run instead: {verdict}]`. Never blank,157 never "passed" by default.158- Motion Block/Approve verdict if applicable.159- Findings list, P0-P3, no aggregate score.160- Challenger verdict: resolved/owner-accepted, or "not judged" on tool-unavailable fallback.161- Any remaining Minor/P2-P3 issues after the 2-cycle cap, reported, not hidden.162163### Next → report to the owner. A P0/P1 unresolved or challenger-Blocked finding means164the deliverable is not "done" — say so plainly, don't soften it into "mostly ready."165166### References167| File | Purpose |168|------|---------|169| `references/review-procedure.md` | **Canonical full procedure — Part 1/Part 2/challenger gate, step-by-step** |170| `references/anti-ai-slop-audit.md` | Deterministic AI-slop detection, 15 entries, PASS/FAIL per entry (15 = generic body sequence) |171| `references/pre-flight-checklist.md` | **Mechanical grep/count checks — last filter before audit-clean** |172| `references/elicitation-visual.md` | Named visual techniques (Squint/Subtraction/Competitor/5-Second/Persona) |173| `references/audit-checklist.md` | Typography/color/spacing/motion/a11y checklist tables (ignore its Scoring section — superseded above) |174| `references/consistency-checks.md` | Cross-component border-radius/shadow/spacing coherence |175| `references/ux-wcag.md` | WCAG 2.2 AA beyond contrast (focus, touch targets, keyboard nav) |176| `references/ux-nielsen.md` | Nielsen's 10 usability heuristics |177| `references/ux-laws.md` | Laws of UX (Fitts, Hick, Miller) |178| `references/ux-patterns.md` | Form/validation/mobile UX implementation patterns |179| `references/motion-audit.md` | 10 motion standards + delete-first remediation hierarchy |180| `references/motion-verdict.md` | Block/Approve verdict format for reviewed motion |