Design bay
UI critique
PromptStableby @julian2026-05-27
Copies
—
loading…
Views
—
loading…
Spice
A bit of context helps. Read the notes.
paste into Claude, or drop the file into a Claude Code skills dir
What it does
Gives a structured critique of a UI screen or flow, numbered, specific, and actionable. Not a vibe, not a compliment sandwich.
When to use
- Before presenting designs to a client
- As a self-check before a design review
- When reviewing a teammate's work
The skill
I'm going to describe a UI (or share a screenshot). Give me a structured critique.
Work through these lenses in order:
- Visual hierarchy. Is it clear where to look first? What's competing for attention?
- Clarity of purpose. Can a new user tell what this screen is for in under 5 seconds?
- Copy and labels. Are labels precise? Is any copy ambiguous, redundant, or doing too much?
- Consistency. What's inconsistent with itself or with conventions the user would expect?
- Accessibility. Any obvious contrast, sizing, or structure concerns?
- One thing to fix first. If you could only fix one thing, what would have the most impact?
Number each point. Be specific, name the element, not just the category. Skip praise unless it's directly relevant to a contrast.
Here's what I'm working with:
[paste description or share screenshot]
Comments & reactions
Comments arrive once we point Giscus at the repo. Threads in GitHub Discussions. Reactions count as votes. No new logins.