SkillHub

Skills anthropics knowledge-work-plugins

design-critique

Use it when:
You want feedback on a mockup, screen or flow, at any stage from early exploration to final polish.
It checks:
The two-second first impression, usability, visual hierarchy, consistency with your design system, and accessibility such as contrast and touch targets.
You get:
A Markdown critique: overall impression, tables of findings with severity and fixes, what works well, and three priority recommendations.
With connectors:
It pulls the design from Figma to inspect components, tokens and layers, and cross-checks it against recent user feedback.
Runs:
As /design-critique with a Figma URL, screenshot or description.
Part of:
The design plugin of Anthropic's knowledge-work plugins.

TL;DR

A design review command. You share the design as a Figma link, a screenshot, a file or a description, with what it is, who it's for and what stage it's at, and optionally a focus such as mobile or one flow. It reviews the design through five lenses. First impression asks what draws the eye in two seconds, whether that's right, and whether the purpose is clear. Usability asks whether users can reach their goal, whether navigation and interactive elements are obvious, and whether any steps are unnecessary. Visual hierarchy covers reading order, emphasis, whitespace and typography. Consistency checks spacing, color, typography and behavior against the design system. Accessibility covers color contrast, touch target size, text readability and alt text. Feedback is meant to be specific, explain why, propose an alternative, say what works and fit the stage. The critique rates usability findings critical, moderate or minor and ends with three priority recommendations; with Figma connected it also compares the design against your existing design system.

Summarizes the skill at ab4cb1c.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill design-critique

skills.sh pageSource on GitHubAll skills from anthropics/knowledge-work-plugins

Total Downloads
5,800 on skills.sh, Nov 9, 2026
Repo stars
35,234 anthropics/knowledge-work-plugins
First seen
Feb 24, 2026 on skills.sh
Weekly Downloads
284
+71% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21166
Sep 28110
Oct 594
Oct 12120
Oct 19172
Oct 26152
Nov 2200
Nov 9284
Category
category:designcategory:software-engineering

Taste for interfaces that don't look generated: direction, motion and accessibility.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type
type:workflow

A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:official

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics
designaccessibility

SKILL.md

From anthropics/knowledge-work-plugins at ab4cb1c. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: 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

  1. Share the context — "This is a checkout flow for a B2B SaaS" helps me give relevant feedback.
  2. Specify your stage — Early exploration gets different feedback than final polish.
  3. Ask me to focus — "Just look at the navigation" gives you more depth on one area.