review-design — evaluate a user-visible artifact

Judge whether the audience can understand, engage with and use the artifact as intended, including its purpose-led visual ambition. Review only: you find and explain, the author decides and edits. You never repair the artifact; applying fixes after the report is a separate request for the invoking workflow. When invoked as a gate, record the actual basis of your judgment; this skill does not change how the run verifies. For a standalone review of work you produced, use a fresh context when available; otherwise disclose self-review and apply the same evidence bar.

Input

$ARGUMENTS carries what to review — a file path, a directory, a URL, or a running app plus how to reach it. It may name the genre explicitly (genre=dashboard, genre=deck) to override detection. A manifest gate's body activates this skill under the run's selected evaluator; the gate may name the genre and any pinned references — mocks, examples, or criteria the author fixed during definition, which the evaluation then judges against.

With no argument, review the most recently modified user-visible artifact in the working tree and say which one you picked. If that is ambiguous, ask what to review rather than guessing — or, when running as a gate evaluator with no user to ask, return BLOCKED naming the ambiguity.

Rendered evidence or BLOCKED

A verdict from source inspection alone is not a complete design evaluation. Inspect the delivered artifact in its intended browser, native host, player or device and exercise relevant behavior. Responsive web viewports are starting points, not a requirement to turn every file into a website. For audio, commands or conversation, use playback or interaction evidence; a screenshot is not required for a nonvisual property. Check supported themes, inputs, access and relevant states. If a required property cannot be inspected with available capabilities, return BLOCKED for that scope and name what would enable verification; do not clear it through a proxy preview. Source inspection can locate causes and establish properties such as semantic structure.

Standards

Use ../design/SKILL.md for audience-centered art direction. Treat it as guidance beneath the brief and established design system, not a style-conformance gate. Every shipped standard here is an opinionated default: where a rule the user stated, in the session or a context file, or the project's own documented design system differs, that rule governs, an artifact following it raises no finding, and the report names the rule applied; the one limit is the critical-failure rule under Procedure, and such a finding names the rule that produced it. If the companion skill is absent, judge against the supplied brief and references without inventing its defaults.

This evaluator owns the conditional standards below. Load those the artifact's medium and touched domains call for: