AGENT SKILL

design-critique

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).

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
design-critique
description
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).
disable-model-invocation
true

02 资源文件 3

03 SKILL.md 正文

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

04 同仓库更多 Skills

jorgesolerrr
jorgesolerrr/skills

explainroo

Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.

★ 0
jorgesolerrr
jorgesolerrr/skills

unslop

Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".

★ 0
jorgesolerrr
jorgesolerrr/skills

technical-writing

Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.

★ 0
jorgesolerrr
jorgesolerrr/skills

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

★ 0