design-critique
Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.
Install / Use
npx skills add anthropics/knowledge-work-plugins --skill design-critiqueInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Our assessment of design-critique
design-critique scores 93/100 on our quality scale, 41st of 260 Design skills we index (top 16%).
Its SKILL.md is 3.8 KB long, well organised into 21 sections with 2 code examples: a solid amount of guidance for an agent.
With 25,526 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so design-critique is actively maintained.
- Our last check on 2026-10-03 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
design-critique compared with similar skills
All 4 of these similar skills score higher than design-critique; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| design-critique (this skill)by anthropics | 93 | 25.5k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install design-critique?
- Run
npx skills add anthropics/knowledge-work-plugins --skill design-critique. The install tabs above show the steps for each supported agent. - Which AI agents does design-critique work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is design-critique safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is design-critique still maintained?
- The repository was last updated about 2 months ago, so design-critique is actively maintained.
Skill content
View source on GitHubname: design-critique description: Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish. argument-hint: "<Figma URL, screenshot, or description>"
/design-critique
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Get structured design feedback across multiple dimensions.
Usage
/design-critique $ARGUMENTS
Review the design: @$1
If a Figma URL is provided, pull the design from Figma. If a file is referenced, read it. Otherwise, ask the user to describe or share their design.
What I Need From You
- The design: Figma URL, screenshot, or detailed description
- Context: What is this? Who is it for? What stage (exploration, refinement, final)?
- Focus (optional): "Focus on mobile" or "Focus on the onboarding flow"
Critique Framework
1. First Impression (2 seconds)
- What draws the eye first? Is that correct?
- What's the emotional reaction?
- Is the purpose immediately clear?
2. Usability
- Can the user accomplish their goal?
- Is the navigation intuitive?
- Are interactive elements obvious?
- Are there unnecessary steps?
3. Visual Hierarchy
- Is there a clear reading order?
- Are the right elements emphasized?
- Is whitespace used effectively?
- Is typography creating the right hierarchy?
4. Consistency
- Does it follow the design system?
- Are spacing, colors, and typography consistent?
- Do similar elements behave similarly?
5. Accessibility
- Color contrast ratios
- Touch target sizes
- Text readability
- Alternative text for images
How to Give Feedback
- Be specific: "The CTA competes with the navigation" not "the layout is confusing"
- Explain why: Connect feedback to design principles or user needs
- Suggest alternatives: Don't just identify problems, propose solutions
- Acknowledge what works: Good feedback includes positive observations
- Match the stage: Early exploration gets different feedback than final polish
Output
## Design Critique: [Design Name]
### Overall Impression
[1-2 sentence first reaction — what works, what's the biggest opportunity]
### Usability
| Finding | Severity | Recommendation |
|---------|----------|----------------|
| [Issue] | 🔴 Critical / 🟡 Moderate / 🟢 Minor | [Fix] |
### Visual Hierarchy
- **What draws the eye first**: [Element] — [Is this correct?]
- **Reading flow**: [How does the eye move through the layout?]
- **Emphasis**: [Are the right things emphasized?]
### Consistency
| Element | Issue | Recommendation |
|---------|-------|----------------|
| [Typography/spacing/color] | [Inconsistency] | [Fix] |
### Accessibility
- **Color contrast**: [Pass/fail for key text]
- **Touch targets**: [Adequate size?]
- **Text readability**: [Font size, line height]
### What Works Well
- [Positive observation 1]
- [Positive observation 2]
### Priority Recommendations
1. **[Most impactful change]** — [Why and how]
2. **[Second priority]** — [Why and how]
3. **[Third priority]** — [Why and how]
If Connectors Available
If ~~design tool is connected:
- Pull the design directly from Figma and inspect components, tokens, and layers
- Compare against the existing design system for consistency
If ~~user feedback is connected:
- Cross-reference design decisions with recent user feedback and support tickets
Tips
- Share the context — "This is a checkout flow for a B2B SaaS" helps me give relevant feedback.
- Specify your stage — Early exploration gets different feedback than final polish.
- Ask me to focus — "Just look at the navigation" gives you more depth on one area.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
