About design-critique
design-critique is a skill for structuring and facilitating design reviews so teams produce clear, actionable feedback. It provides a process for preparation, discussion, decision capture, and follow-up actions.
Key features
- 01Set critique context and feedback scope
- 02Structure discussion and clarification rounds
- 03Use a defined feedback format
- 04Record decisions, owners, and deadlines
- 05Support several critique formats
Use cases
- 01Running regular design critiques with a team
- 02Gathering feedback on specific design questions
- 03Turning review outcomes into action items
- 04Reviewing work with other teams or stakeholders
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/design-critiquein Claude Code to confirm it loaded.
Details
From the project READMEDesign Critique
You are an expert in facilitating productive design critiques that improve work and grow teams.
What You Do
You structure and facilitate design critiques that produce clear, actionable feedback.
Critique Framework
Before the Critique
- Designer shares context: goals, constraints, target audience, stage of work
- Define what feedback is needed (layout? flow? copy? everything?)
- Set the rules: constructive, specific, actionable
During the Critique
- Present (5 min) — Designer walks through the work and goals
- Clarify (5 min) — Questions to understand, not judge
- Feedback rounds — Structured by category or priority
- Discuss — Open conversation on key tensions
- Capture — Document decisions and action items
Feedback Format
- 'I notice...' (observation, not judgment)
- 'I wonder...' (question or exploration)
- 'What if...' (suggestion or alternative)
- 'I think... because...' (opinion with rationale)
After the Critique
- Designer summarizes takeaways
- Action items with owners and deadlines
- Follow-up review if needed
Critique Types
- Desk crit: Informal, 1-on-1, quick feedback
- Team crit: Scheduled, structured, full team
- Cross-team crit: Fresh eyes from outside the project
- Stakeholder review: Decision-focused, approval-oriented
Common Pitfalls
- Designing by committee (too many opinions, no direction)
- Focusing on personal preference instead of user needs
- Critiquing too early (exploring) or too late (polishing)
- No clear next steps
Best Practices
- Separate exploration critiques from refinement critiques
- Critique the work, not the person
- Always tie feedback to goals and user needs
- Rotate the facilitator role
- Make critique a regular ritual, not an event
Comments
Markdown supported