design-review

Evaluates UI page structure and information hierarchy to produce a written design critique artifact.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill design-review-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/pnewsam/skills/tree/main/archive/design-review
Command: npx skills add https://github.com/pnewsam/skills --skill design-review-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pages accumulate features over time and their structure stops making sense: unclear hierarchy, misplaced controls, confusing navigation. This Skill provides a systematic, lens-based critique of a page or flow at the structural level, producing a written artifact with prioritized findings and recommendations. Note: this is a deprecated legacy workflow kept only for users who explicitly request the old critique artifact. ## Core Features & Use Cases - Five evaluation lenses: information hierarchy, page structure and composition, navigation and wayfinding, content and data presentation, and interaction consistency. - Classified findings: each issue is tagged with lens, impact, effort level, and a concrete recommendation, split into quick fixes versus deeper structural work. - Critique artifact: writes a structured Markdown report to docs/tmp/design-review-{target}.md covering context, strengths, key findings, and recommended actions. - Use Case: A settings page has grown to seven flat sections. Run the critique to identify grouping opportunities, misplaced page-level controls, and inconsistent save patterns, then get a prioritized action list. ## Quick Start Ask the assistant to run the legacy design-review critique on a specific page or route, optionally providing a screenshot, and have it write the critique artifact to docs/tmp.

Frequently Asked Questions about design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a structural design critique on a UI page?▼

Specify the page, route, or flow to critique and optionally provide a screenshot. The workflow reads the relevant code, evaluates the page through five lenses, and writes a classified critique artifact to docs/tmp/design-review-{target}.md.

What is the difference between design-review and design-polish?▼

design-review evaluates page-level structure such as hierarchy, navigation, and section composition, while design-polish handles component-level visual details like spacing, alignment, typography, and color. Structural findings go here; pixel issues are deferred to design-polish.

Is the design-review skill deprecated?▼

Yes. It is a legacy critique workflow parked while the design skill taxonomy is reorganized around design-expert and focused design-* reference skills. Use it only when the old critique artifact workflow is explicitly requested.

Can a design critique work without a screenshot?▼

Yes. Without a screenshot, the workflow infers structure from the component tree, conditional rendering paths, and data flow in the code. A screenshot helps anchor the visual assessment of layout and hierarchy but is not required.

When should I not use a structural design critique?▼

Skip it when the issue is purely visual polish, when the page is intentionally unconventional but works, or when the structure is already sound. The workflow explicitly avoids manufacturing findings and recommends design-polish for component-level issues.