Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
owl-listener avatar

Design Critique

  • 993 installs
  • 1.9k repo stars
  • Updated June 14, 2026
  • owl-listener/designer-skills

design-critique is an agent skill that facilitates structured, bias-reduced design critiques producing specific actionable feedback through a timed five-step framework.

About

design-critique is an Owl-Listener designer-skills module that structures design review sessions so feedback stays constructive, specific, and tied to user goals instead of personal taste. Before critique, the skill sets context on goals, constraints, audience, and the feedback scope—layout, flow, copy, or everything. During critique it runs a five-step agenda: Present (5 min), Clarify (5 min), structured feedback rounds, open discussion on key tensions, and Capture of decisions and action items. Feedback uses four formats—I notice, I wonder, What if, and I think because—to separate observation from judgment. The skill documents four critique types—desk, team, cross-team, and stakeholder review—and pitfalls like designing by committee or critiquing at the wrong fidelity. Reach for design-critique when a team needs facilitated review of mocks, prototypes, or shipped UI rather than ad-hoc opinion threads.

  • 5-step critique ritual: Present, Clarify, Feedback rounds, Discuss, Capture
  • Standardized feedback language: 'I notice…', 'I wonder…', 'What if…', 'I think… because…'
  • Supports four critique types: desk crit, team crit, cross-team crit, stakeholder review
  • Pre-critique context and rule-setting to keep sessions productive
  • Post-critique action items with owners, deadlines, and follow-up plan

Design Critique by the numbers

  • 993 all-time installs (skills.sh)
  • +48 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #395 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill design-critique

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs993
repo stars1.9k
Security audit3 / 3 scanners passed
Last updatedJune 14, 2026
Repositoryowl-listener/designer-skills

How do you run a structured design critique session?

Run structured, bias-free design critiques that turn vague opinions into specific, actionable improvements.

Who is it for?

Designers and engineers who need a repeatable critique ritual that converts subjective reactions into goal-aligned UI and UX improvements.

Skip if: Automated visual regression testing or solo developers who only want pixel-perfect code generation without a review process.

When should I use this skill?

The user asks to critique a design, run a design review, structure team feedback on mocks, or facilitate a stakeholder design session.

What you get

Critique agenda, categorized feedback notes, documented decisions, and action items with owners and deadlines.

  • Critique agenda
  • Feedback notes
  • Action item list

By the numbers

  • Five-step During the Critique agenda with 5-minute Present and Clarify slots
  • Four structured feedback phrasing formats
  • Documents four critique types: desk, team, cross-team, and stakeholder

Files

SKILL.mdMarkdownGitHub ↗

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

Related skills

How it compares

Pick design-critique for facilitated human review sessions; use swiftui-design-principles when an agent must directly polish generated SwiftUI code.

FAQ

What is the design-critique session structure?

design-critique runs five timed steps—Present (5 min), Clarify (5 min), structured feedback rounds by category, open discussion on tensions, and Capture of decisions plus action items with owners.

What feedback format does design-critique use?

design-critique promotes four phrasing patterns: I notice for observations, I wonder for questions, What if for alternatives, and I think because for opinions with rationale tied to user goals.

What critique types does design-critique support?

design-critique covers four formats—informal desk crits, scheduled team crits, cross-team crits for fresh eyes, and stakeholder reviews focused on approval decisions.

Is Design Critique safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.