Design critique
Critique a design direction, mock, or live page against site composition hard rules and DIRECTION — before or beside code. Use when reviewing look-and-feel, mocks, or asking if the design holds up.From its SKILL.md
npx -y skills add Alfred-Lau/skills --skill design-critiqueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Design Critique
Design review without requiring a code diff. Axis: hard rules + stated direction — not personal taste.
Process
1. Load intent
DIRECTION.md, BRAND.md, IA.md / page-spec if relevant, docs/agents/design-rules.md. Never critique against an unspoken aesthetic.
Read the ## Rule exceptions table in DIRECTION.md. Deviations listed there are accepted; report
them as such. Deviations justified only by direction prose are still findings.
2. Gather subject
Mocks, screenshots, live page, or prose in DIRECTION.md itself. If images are available, read them.
3. Critique
Walk rubric.md. For each miss:
- Expected (cite rule or direction line)
- Observed
- Severity: blocker / major / nit
- Move: concrete change (still design-language — not necessarily a file path)
Prefer positive targets ("hero should be one full-bleed plane with brand-level name") over ban-lists.
4. Outcome
- Direction still fluid → feed fixes into
/visual-directionor/ui-prototype - Spec exists →
/page-specupdates then/implement-ui - Live UI → pair with
/visual-qafor evidence grading
Completion criterion: rubric covered; every blocker has a move; no free-floating "make it pop".