critique
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".
Profile →npx skills add nexu-io/open-design --skill critique --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. **Header** — what artifact was reviewed, date, reviewer ("OD · Critique skill"), 1-line verdict 2. **Radar chart** (inline SVG, no library) showing the 5 scores 3. **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 4. **Combined action lists** at the bottom: - **Keep** — what's working, don't touch - **Fix** — P0 / P1 issues that are visually expensive - **Quick wins** — 5–15 minute tweaks with disproportionate impac
- When to use
- What you produce
- The 5 dimensions
- 1. Philosophy consistency · 哲学一致性
- 2. Visual hierarchy · 视觉层级
- 3. Detail execution · 细节执行
- 4. Functionality · 功能性
- 5. Innovation · 创新性
- Scoring discipline (read before you score)
- Workflow
- Step 1 — Acquire the artifact
- Step 2 — Read enough to score
- Step 3 — Score with evidence
- Step 4 — Build the action lists
What does the critique skill do?
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".
How do I install it?
Run `npx skills add nexu-io/open-design --skill critique --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.