Owl-ListenerInstall Design Critique
Pick your agent. Every command is ready to paste.
npx skills add Owl-Listener/designer-skills --skill design-critiqueThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads design-critique when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the design-critique skill”. In Codex, type $design-critique.
Design 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
Tips for Design Critique
- • Start a fresh session after installing so your agent picks up the new skill.
- • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Design Critique
What does the Design Critique skill do?
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 do I install Design Critique?
Run "npx skills add Owl-Listener/designer-skills --skill design-critique" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Design Critique work in Cursor and Codex?
Yes. Design Critique uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Design Critique free?
Design Critique is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Design Critique?
Design Critique is published by Owl-Listener in the Owl-Listener/designer-skills repository, together with 29 other skills.
