---
name: design-review-scorecard
description: "Scores one screen on hierarchy, consistency, copy, states, and accessibility, then lists the fixes in the order they pay off. Use when a designer or product owner wants a numeric critique of one screen covering hierarchy, copy, states, and accessibility before release. Do not use for designing a screen from scratch or running a user research study. Related topics: design, product."
---

# Design Review Scorecard

Scores one screen on hierarchy, consistency, copy, states, and accessibility, then lists the fixes in the order they pay off.

## When to use

Use this skill when a designer or product owner wants a numeric critique of one screen covering hierarchy, copy, states, and accessibility before release. Do not use it for designing a screen from scratch or running a user research study.

## 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. Identify the primary user goal and the element that should dominate the screen.
3. Score hierarchy, consistency, copy, states, and accessibility from 1 to 5 with one-line reasons.
4. Cite the exact element behind each score below 4.
5. Build a fix table with effort and impact, ordered with high impact and small effort first.
6. Name the one change that best serves the primary goal.

## Inputs

- **Screen description or link** (longer free text)
- **Platform** (choose one: Web desktop, Web mobile, iOS, Android)
- **Primary user goal** (free text, e.g. "The one thing a user comes to do")
- **Design system in use** (free text, e.g. "Name or none")
- **Known complaints** (longer free text)
- **Review depth** (choose one: Quick pass, Standard, Thorough)

## Output

A scorecard of five scored areas with reasons and a total, a sorted fix table with effort and impact, and one closing recommendation.

## Prompt template

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

### Design Review Scorecard

Score this screen and tell me what to fix.

- Screen description or link: {{Screen description or link}}
- Platform: {{Platform}}
- Primary user goal: {{Primary user goal}}
- Design system in use: {{Design system in use}}
- Known complaints: {{Known complaints}}
- Review depth: {{Review depth}}

Score each area from 1 to 5 with a one-line reason: visual hierarchy (is the primary action the loudest element), consistency (spacing, type, colour, component reuse), copy (clear labels, no jargon, useful errors), states (empty, loading, error, success, disabled), and accessibility (contrast, touch targets, focus order, text alternatives). Cite the specific element behind every score below 4. Total the scores, then list fixes as a table with columns for issue, fix, effort (S, M, L), and impact (low, medium, high), sorted so high impact and small effort come first. Close with the single change that would most improve the primary user goal.

## Pitfalls

- Giving scores without naming the element, which leaves designers unable to find the problem.
- Rating on taste instead of the user goal.
- Forgetting empty, loading, and error states because the mockup shows only the filled screen.