---
name: design-critique-framework
description: "Structures design feedback around whether the design achieves its goal, split into what works, what confused you, and what is a risk, matched to the stage the design is at. Use when a reviewer must give design feedback that is about whether the work achieves its goal, not about personal taste. Do not use for a heuristic accessibility audit, a usability test plan, or redesigning the work. Related topics: Design, Communication, Product."
---

# Design Critique Framework

Structures design feedback around whether the design achieves its goal, split into what works, what confused you, and what is a risk, matched to the stage the design is at.

## When to use

Use this skill when a reviewer must give design feedback that is about whether the work achieves its goal, not about personal taste. Do not use it for a heuristic accessibility audit, a usability test plan, or redesigning the work.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the goal from the user and business sides and judge the design only against that.
3. Sort observations into what works, what confused you, and what is a risk, with the screen or element for each.
4. Match the depth of the notes to the stage, leaving out visual polish on early concepts.
5. Phrase each point as an observation or a question and adjust the framing to the reviewer's relationship with the designer.
6. Choose the one point to open the conversation with and say why.

## Inputs

- **The design** (longer free text)
- **What it is meant to achieve** (longer free text)
- **Stage** (choose one: Rough concept, Wireframe, Visual design, Near final, Already shipped)
- **Constraints the designer was working under** (longer free text)
- **My relationship to them** (choose one: Peer, Their manager, Their client, More junior than them)

## Output

A critique with three sections (works, confusing, risks), each point framed as an observation or a question, and a single opening line to say first.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Design Critique Framework

I need to critique a design and I want to stay off personal preference.

- The design: {{The design}}
- What it is meant to achieve: {{What it is meant to achieve}}
- Stage: {{Stage}}
- Constraints the designer was working under: {{Constraints the designer was working under}}
- My relationship to them: {{My relationship to them}}

Structure the critique around whether the design achieves its stated goal. Split it into what works, what confused me, and what is a risk.

Match the depth to the stage, since detailed visual notes on a wireframe waste everyone's afternoon. Phrase each point as an observation or a question rather than an instruction, and adjust the framing to my relationship to the designer. Respect the constraints and do not criticise choices they forced.

Give me the one thing to say first.

## Pitfalls

- Giving visual polish notes on a wireframe, which distracts from structure.
- Writing instructions like change this to blue instead of observations the designer can solve.
- Criticising a choice that came from a stated constraint.
