critique

1# Critique Skill · 5 维度专家评审
2 
3Produce a single-file HTML "design review report" that scores any
4artifact across 5 dimensions and proposes actionable fixes. Inspired by
5the *huashu-design* expert-critique flow.
6 
7## When to use
8 
9- After the agent (or user) generates an artifact (deck / prototype /
10  landing page) and the user asks "what's wrong with this?" or
11  "review this"
12- As a self-check loop the agent can run on its own output **before**
13  emitting it
14- For comparing two variants of the same design
15 
16## What you produce
17 
18A single self-contained `<artifact type="text/html">` review report
19including:
20 
211. **Header** — what artifact was reviewed, date, reviewer ("OD ·
22   Critique skill"), 1-line verdict
232. **Radar chart** (inline SVG, no library) showing the 5 scores
243. **Five dimension cards**, each with:
25   - Score 0–10 (with band: 0–4 *Broken* · 5–6 *Functional* · 7–8 *Strong*
26     · 9–10 *Exceptional*)
27   - 1-paragraph evidence (cite specific elements / files / lines)
28   - One Keep / Fix / Quick-win bullet
294. **Combined action lists** at the bottom:
30   - **Keep** — what's working, don't touch
31   - **Fix** — P0 / P1 issues that are visually expensive
32   - **Quick wins** — 5–15 minute tweaks with disproportionate impact
33 
34## The 5 dimensions
35 
36> Each dimension is independent — a deck can be 9/10 on Innovation but
37> 4/10 on Hierarchy and the report should say so plainly. Don't average
38> away interesting failures.
39 
40### 1. Philosophy consistency · 哲学一致性
41…