reviewlisted

# Review **Run Claude Code's built-in reviewer first. Do not re-implement it here.** ``` /code-review ``` Pass an effort level when the user asked for one: `/code-review low` for a quick look, `/code-review high` or `max` for a thorough pass. `/code-review ultra` launches a multi-agent cloud review — it is user-triggered and billed, so suggest it rather than assuming it. That skill already covers correctness bugs, edge cases, error handling, unsafe casts, reuse and simplification, and it verifies its own findings before reporting. Everything below is the delta: things it cannot know because they are decisions this project made. ## Then check the project-specific delta **Read `.claude/project-rules.md` first if it exists** — it was measured from this codebase and outranks both the list below and the `standards` skill. A rule listed there as "Undecided" must not be flagged in either direction. If it does not exist, suggest `/autodev-init` once, then continue with the defaults below. Work through these against the changed files only. ### 1. prd.json alignment If a `prd.json` story covers this change, does the diff actually satisfy its acceptance criteria — or only the easy half? Flag partial completion explicitly rather than marking the story done. ### 2. Design tokens No hardcoded colors. Semantic tokens only (`text-foreground`, `bg-background`), with the one exception the `rule-design-system` skill documents for dynamic gradient surfaces. This is a project convention,