---
name: nudgekit-review
description: Review UI code or a running page against the NudgeKit UI rules (ui.nudgekit.app) and report what breaks them, with file and line. Use when the user asks to review, audit, check or polish UI built with NudgeKit UI or @nudgekit components, asks "does this follow the nudgekit style", or before shipping a page in a NudgeKit product. Pairs with the nudgekit skill, which is for building.
---

# NudgeKit UI review

Check work against the NudgeKit UI rules and report what breaks them. Do not restyle anything while reviewing; list the findings, then fix them only if the user asks.

## 1. Search the code

Run these over the changed files (adjust the path). Each hit is a finding unless the note says otherwise.

```bash
# Drop shadows. NudgeKit has none.
grep -rnE "shadow-(xs|sm|md|lg|xl|2xl)|drop-shadow|box-shadow:" src/ app/ components/

# Hover lift. Nothing moves up on hover.
grep -rnE "hover:-translate-y|hover:scale-|translateY\(-" src/ app/ components/

# Light greys used for text. Use text-muted-foreground or text-faint.
grep -rnE "text-(gray|slate|zinc|neutral)-(300|400)|opacity-(40|50|60)" src/ app/ components/

# Raw hex colours in components. Use tokens (bg-surface, text-brand-ink...).
grep -rnE "(bg|text|border)-\[#" src/ app/ components/

# Heavy headline weights. Headlines use the headline utility (weight 500).
grep -rnE "<h[12][^>]*font-(semibold|bold|extrabold)" src/ app/ components/

# Em dashes and exclamation marks in copy.
grep -rn "$(printf '\342\200\224')" src/ app/ components/

# All-caps eyebrows.
grep -rnE "uppercase|tracking-widest" src/ app/ components/
```

## 2. Read for what a search cannot catch

- **One primary button per screen.** Count `variant="primary"` (or Buttons with no variant) visible at once. More than one is a finding.
- **Purple only for action.** Purple headings, paragraphs, card fills or icons used as decoration are findings.
- **Two-tone headlines.** h1 and h2 use `headline`; a second phrase sits in `<Tone>`. Two Tones in one heading, or a Tone before a full first sentence, is a finding.
- **Status as text.** Filled coloured pills for status, coloured card borders, or coloured alert backgrounds are findings. Use `<Status>` and `<Alert>`.
- **One viewfinder,** around the hero media only.
- **Corners.** Buttons and inputs 4px, panels 12px, cards 16px.
- **Copy.** Sentence case, plain, no hype words ("seamless", "unlock", "supercharge").
- **Accessibility.** Icon-only buttons have `aria-label`; inputs sit in `<Field>` or have a label; focus is visible; motion respects `prefers-reduced-motion`; text contrast passes AA.
- **Prefer the registry.** A hand-written navbar, hero, card, pricing table or dialog that duplicates an `@nudgekit/*` item is a finding: name the item to install instead.

## 3. Report

List findings grouped by rule, most visible first, each as `path:line - what is wrong - the fix`. End with a one-line verdict: ready to ship, or the number of findings to fix.
