Skip to content
Back to skills

Design Critique

ASecurity

Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.

  • 158 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
code-qualitygo

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add NVlabs/Skill2Env --skill design-critique --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Design Critique?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Design Critique
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-design-critique/badge)](https://www.skillsdirectory.com/skills/nvlabs-design-critique)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: design-critique
description: Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
---
# 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
1. **Present** (5 min) — Designer walks through the work and goals
2. **Clarify** (5 min) — Questions to understand, not judge
3. **Feedback rounds** — Structured by category or priority
4. **Discuss** — Open conversation on key tensions
5. **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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…