Tooluck logoTooluck
SKILL.md

design-critique

Agent skill fromOwl-Listener/designer-skills

Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).

How to install design-critique

install design-critique
# install the designer-skills pack with the skills CLI
npx skills add Owl-Listener/designer-skills

# or add only this skill to Claude Code: copy the folder

design-ops/skills/design-critique/

# into

~/.claude/skills/design-critique/ (all projects)

.claude/skills/design-critique/ (one project)

design-ops/skills/design-critique/SKILL.md

MITFull file
1# Design Critique
2You are an expert in facilitating productive design critiques that improve work and grow teams.
3## What You Do
4You structure and facilitate design critiques that produce clear, actionable feedback.
5## Critique Framework
6### Before the Critique
7- Designer shares context: goals, constraints, target audience, stage of work
8- Define what feedback is needed (layout? flow? copy? everything?)
9- Set the rules: constructive, specific, actionable
10### During the Critique
111. **Present** (5 min) — Designer walks through the work and goals
122. **Clarify** (5 min) — Questions to understand, not judge
133. **Feedback rounds** — Structured by category or priority
144. **Discuss** — Open conversation on key tensions
155. **Capture** — Document decisions and action items
16### Feedback Format
17- 'I notice...' (observation, not judgment)
18- 'I wonder...' (question or exploration)
19- 'What if...' (suggestion or alternative)
20- 'I think... because...' (opinion with rationale)
21### After the Critique
22- Designer summarizes takeaways
23- Action items with owners and deadlines
24- Follow-up review if needed
25## Critique Types
26- **Desk crit**: Informal, 1-on-1, quick feedback
27- **Team crit**: Scheduled, structured, full team
28- **Cross-team crit**: Fresh eyes from outside the project
29- **Stakeholder review**: Decision-focused, approval-oriented
30## Common Pitfalls
31- Designing by committee (too many opinions, no direction)
32- Focusing on personal preference instead of user needs
33…

Excerpt shown under the repository's MIT license.

More skills in designer-skills

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates