Menu

Individual skill

opendesigner-review

Checks a built UI like a careful user would: every screen size and theme, scrolling, hover, keyboard, motion frames, and measured spacing, type, fonts and contrast. Reports findings with evidence.

skills/opendesigner-review/SKILL.md

Read pinned source

Source commit 54ae7ce6b6ae67f7460ad3fba2b66c4aac488e9b

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
80
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# OpenDesigner: review

Use this when a screen, page or app has been built and someone asks "does it look right?", "review this", "QA this" or "check my UI". Use it too, on your own work, before you say it is done. It works on what you built and on what anyone else built. With an OpenDesigner system in the project it checks against the tokens. Without one it checks the accessibility floors and whether the page is consistent with itself.

This reviews built screens. To review the design system's own decisions and coverage, the router's critique step (P7) and `opendesigner-extend` do that.

The idea: **a screenshot is one picture of one moment, and eyes cannot read numbers off pixels.** Agents that review UIs by looking at one screenshot miss what is below the fold, at other sizes, in dark mode, on hover, on Tab, in motion, and a 2 px error in spacing. So a review has three kinds of evidence, and every finding says which it rests on:
- **measured**: a number read from the page (`probe.js`): sizes, colors, contrast, fonts, overflow, labels that break across lines (a wrapped label overflows nothing, so only this catches it), animations.
- **operated**: you did something (pressed Tab, hovered, scrolled, switched a setting) and saw the result.
- **seen**: you looked at pixels. Use this for "is anything obviously broken?", not for numbers.

Output, in the person's repo: `opendesigner/review/` with the plan, probe results, screenshots, `findings.*.json` and `REPORT.md`. The verdict is never "looks good". It is **FAIL**, **INCOMPLETE**, or **NO ERRORS FOUND** in the cells that were checked, followed by what was not checked.

Talk plainly: one idea and one question per message, and recommend one option with its reason. First time a term appears, give its plain meaning plus "Designers: X · Code: Y" (`references/rules.md` in the opendesigner skill).