design-critique

Review UI screens and flows to produce prioritized design feedback with severity-ranked fixes.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill design-critique-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-critique
Source: https://github.com/nabitllc/todero/tree/main/packages/skills-catalog/catalog/optional/product/design-critique
Command: npx skills add https://github.com/nabitllc/todero --skill design-critique-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design feedback is often vague, subjective, or buried in unstructured opinions, making it hard for designers and engineers to know what to change first. This Skill turns a screen, flow, or component review into a structured, prioritized critique that teams can act on immediately. ## Core Features & Use Cases - Structured nine-pass review: Evaluates user job clarity, visual hierarchy, affordances, states, forms, accessibility, consistency, copy, and edge cases in a fixed order. - Severity-ranked output: Groups findings into must-fix, should-fix, and nice-to-fix buckets, each with a concrete suggested change, plus a strengths-to-keep section. - Context-first discipline: Requires user role, job, success criteria, and flow position before critiquing, preventing taste-based feedback. - Use Case: Before shipping a new onboarding flow, a product engineer pastes screenshots and asks for a critique; the result is a ship-blocking list of accessibility and empty-state issues ordered by severity. ## Quick Start Ask the AI to critique a specific screen or flow, providing who the user is, what job they are doing, and what success looks like, then request the findings grouped by severity.

Frequently Asked Questions about design-critique

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get structured feedback on a UI design?

Provide the screen or flow along with who the user is, what job they are doing, and what success looks like. The critique runs through nine ordered passes covering hierarchy, affordances, states, forms, accessibility, consistency, copy, and edge cases, then returns findings grouped by severity.

What does a design critique cover before shipping a feature?

It covers clarity of the user job, visual hierarchy, affordance and signifiers, empty/loading/error/success states, form validation behavior, WCAG accessibility, pattern consistency, copy quality, and edge cases like long content or offline behavior.

When should I not use a design critique?

Skip it when you want a full redesign, when no concrete artifact exists yet, or when you lack context on the user and their job. In those cases, start a design project or gather user context first, since critique without context becomes opinion.

How is design critique output organized?

Findings are grouped into must-fix, should-fix, and nice-to-fix sections, each with a one-line issue and a one-line suggested change. A strengths-to-keep section is always included so designers know what not to change in the next round.

Does a design critique count as design approval?

No. A critique is feedback, not sign-off. Approval must be stated explicitly when requested; otherwise the output is a prioritized list of recommended changes, not an endorsement to ship.