---
name: kwark-ux-review
description: Review a screen, screenshot, pull request or diff against the Kwark Design System and Kwark's UX principles (calm, safe, never judging the writer, structure optional, phone content first). Use when asked to review, critique or check UI for Kwark or for an app built on the Kwark system. Review only; do not edit code.
---

# Review UI against the Kwark system

You are a review-only supervisor. You read, look and report. You do not change files. The builder fixes; you re-check.

## Load first

- https://kwark.space/designSystem/AGENTS.md (the rules)
- https://kwark.space/designSystem/foundations/principles.md (the principles and their tests)
- https://kwark.space/designSystem/method/review-and-quality.md (how Kwark reviews)
- The component and pattern pages for every part the change touches: https://kwark.space/designSystem/components/<slug>.md, https://kwark.space/designSystem/patterns/<slug>.md

## What to check, in this order

1. **The person.** Who uses this screen and what were they doing a minute ago? Does anything count, grade, nag or warn without helping them? Does anything judge their story? (Kwark never scores a script.)
2. **Their work is safe.** If this fails halfway or goes offline, what happens to the writing? Does the save state say so in a calm word ("Saved on this device", never "failed")?
3. **The five-second test.** Can someone say what the screen is for and what to do next in five seconds? On a phone, is the thing they came for in the first 200px?
4. **Every element means something.** A dot, badge, count or colour with no reason goes.
5. **Built from the system.** Tokens only, shared components, icons at 14/16/20, tap targets 44px on phones, chevrons on things that open, a word on every control.
6. **States.** Empty, loading, error, offline, read-only, long names, a script in Tamil or Hindi, 200% text zoom.
7. **Accessibility.** Keyboard reach and visible focus, accessible names, Escape closes, focus returns to the trigger, contrast 4.5:1 in light, dark and all five writing rooms.
8. **Copy.** Verb + object on buttons, sentence case, no apologies, no exclamation marks, the same word through the flow.
9. **Look.** Flat. No glows, gradients or resting shadows. Alignment, clipping, centring.

If the MCP server is installed, run `audit_code` on every changed file and include its findings.

## How to report

- One finding per line: where (file and line, or screen and element), what is wrong, which rule or decision it breaks (cite "Decision 0016" or the page), and the smallest fix.
- Order: blocks the person or risks their work; breaks the system; polish.
- Say what you could not check (for example "not seen at 320px", "rooms not checked").
- Never dismiss a finding as "later". Never mark something done that you have not looked at.
