Ask Claude for a design review

Complete Structural vs granular feedback first; run a review once the structure is settled, so Claude critiques the layout you're actually keeping, not one you're about to change.

Claude does not only build designs; it can also critique one, including its own. Asking for a review catches the problems your eye glides past, especially contrast, hierarchy, and accessibility. A critique is an honest assessment of what is and is not working. You ask for it in plain language, the same way you ask for a change.

This is a quiet superpower for a non-designer. You do not have to know the rules of good design to benefit from them, because you can ask the tool to apply them for you.

Three things worth asking about come up again and again, so it helps to name them:

- Contrast is how easily text stands out from its background. Low contrast (pale gray text on white) is pretty but hard to read. - Hierarchy is whether the most important thing looks the most important. A weak hierarchy makes everything shout at once, so the eye does not know where to land. - Accessibility (often shortened to a11y) is whether people with low vision, color blindness, or other needs can actually use the design. It is not a nice-to-have; it is part of the work.

Here is the before and after: Someone finishes a page, thinks it looks clean, and ships it. Real visitors squint at the pale headline and miss the button entirely. The fluent user asks first: "review this design for contrast, visual hierarchy, and accessibility, and list the three biggest problems with a fix for each." Claude points out the faint headline and the buried button before anyone else sees them.

Why ask the tool that built it to also judge it: a fresh, rule-based read catches what familiarity hides. You have been staring at the design for twenty minutes, so your eye has stopped seeing it. Claude has not. A good review prompt names what to check and asks for specific, fixable problems, not vague praise.

The move after the review is to fix the real issues, not all of them blindly. Claude's review is advice, not orders. You still decide what matters, but now you are deciding with the weak spots named out loud instead of hidden.

Before you call a design done, ask Claude to review it for contrast, hierarchy, and accessibility. You get a designer's checklist without being a designer.

I've built a design in Claude Design and I want a real critique before I call it finished. Help me run a design review on it.

My design is a [DESCRIBE IT, e.g. "landing page for a yoga studio" or "sales one-pager for a software product"].

Please act as a design reviewer and:
1. Check it for three things and explain each in plain language: contrast (can text be read easily), visual hierarchy (does the most important thing look most important), and accessibility (can people with low vision or color blindness use it).
2. List the 3 to 5 biggest problems you'd expect in a design like this, most serious first.
3. For each problem, give me the exact instruction I could paste back into Claude Design to fix it.
4. Tell me which one problem I should fix first if I only had time for one.

Here's your design review, for the yoga-studio page:

**1. The three checks, in plain words:**
- Contrast: can the text be read without squinting? Pale text on a pale photo usually can't.
- Hierarchy: does your eye land on the class booking first, or get lost?
- Accessibility: would this work for someone color-blind or with low vision?

**2. Likely problems, worst first:**
- The "Book a class" button blends into the hero photo, so the main action is hard to find.
- The headline is light gray on cream: low contrast, hard to read.
- Color alone signals the selected class time, which color-blind visitors may miss.
- The three section headings are nearly the same size as body text, so hierarchy is flat.

**3. Paste-back fixes:**
- "Give the 'Book a class' button a solid high-contrast background so it stands out from the photo."
- "Darken the headline text for stronger contrast against the cream background."
- "Add a checkmark or label, not just color, to show the selected class time."
- "Make section headings noticeably larger and bolder than body text."

**4. Fix first:** the hidden button. If people can't find the main action, nothing else matters.

What good looks like

• You can explain contrast, hierarchy, and accessibility in one plain sentence each
• You can write a review prompt that asks for specific, fixable problems instead of vague praise
• You can turn a review finding into a concrete instruction to fix it
• You understand the review is advice you judge, not orders you follow blindly