critique
Best for design reviewsWorks with GitHubLow risk
⌘source
- author
@nexu-io- language
- TypeScript
★3.7kstars
455forks
Apr 29, 2026
✦overview.md
Key Features
- ·5-dimension scoring (0-10)
- ·Radar chart visualization
- ·Keep / Fix / Quick-wins lists
- ·Evidence-backed scores
- ·Self-contained HTML output
Use Cases
- →Review a generated deck or landing page design
- →Get structured feedback on prototype before sharing
- →Assess design quality across philosophy, hierarchy, detail, functionality, innovation
Best for
- ✓design reviews
- ✓prototype evaluation
- ✓self-check loops
Not ideal for
- !code reviews
- !non-visual artifacts
FAQs
name
critique
description
Run a 5-dimension expert design review on any HTML artifact in the
project — Philosophy / Visual hierarchy / Detail / Functionality /
Innovation, each scored 0–10. Outputs a single self-contained HTML
report with a radar chart, evidence-backed scores, and three lists:
Keep / Fix / Quick-wins. Use when the brief asks for a "design
review", "design critique", "5 维度评审", "design audit", or "what's
wrong with my design".
triggers:["critique","design review","design audit","5 维度评审","5-dim review","audit my design","review my deck","review my landing page","评审","复盘"]
od:{"mode":"prototype","platform":"desktop","scenario":"design","upstream":"https://github.com/alchaincyf/huashu-design","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false},"example_prompt":"Run a 5-dimension critique on the magazine-web-ppt deck I just generated — score philosophy / hierarchy / detail / function / innovation, give me Keep / Fix / Quick-wins."}
Critique Skill · 5 维度专家评审
Produce a single-file HTML "design review report" that scores any artifact across 5 dimensions and proposes actionable fixes. Inspired by the huashu-design expert-critique flow.
When to use
- After the agent (or user) generates an artifact (deck / prototype / landing page) and the user asks "what's wrong with this?" or "review this"
- As a self-check loop the agent can run on its own output before emitting it
- For comparing two variants of the same design
What you produce
A single self-contained <artifact type="text/html"> review report
including:
- Header — what artifact was reviewed, date, reviewer ("OD · Critique skill"), 1-line verdict
- Radar chart (inline SVG, no library) showing the 5 scores
- Five dimension cards, each with:
- Score 0–10 (with band: 0–4 Broken · 5–6 Functional · 7–8 Strong · 9–10 Exceptional)
- 1-paragraph evidence (cite specific elements / files / lines)
- One Keep / Fix / Quick-win bullet
- Combined action lists at the bottom:
- Keep — what's working, don't touch
- Fix — P0 / P1 issues that are visually expensive
$install
1-click copynpx skills add nexu-io/open-design --skill critiqueSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.