agentsclimarketplace
Sign in

Design critique

Skill Dragoon0x/taste-skills/skills/team-practice/design-critique

Run taste-informed design reviews using Observation > Principle > Question. Use when facilitating design critiques, improving feedback quality on a team, or building a shared vocabulary for quality.From its SKILL.md

Install
npx -y skills add Dragoon0x/taste-skills --skill design-critique

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 323 tokens by cl100k_base, as published. Nobody here has run it

Design Critique

Better critique structure. Better design output.

How to use

  • /design-critique Apply design critique constraints to feedback in this conversation.

Constraints

Critique Format

  • MUST use: Observation > Principle > Question for every piece of feedback
  • MUST start with intent: "What were you optimizing for?" before evaluating
  • MUST name tradeoffs, not flaws: "You chose density, which gives power users fast access but makes first-time experience overwhelming"
  • MUST separate craft feedback (alignment, consistency) from taste feedback (should this exist at all?)
  • NEVER give feedback as commands ("make the button blue"). Give direction ("the CTA needs more visual separation").

Running a Critique Session

  • 5 minutes: everyone silently writes 3 specific observations. No vague words.
  • 10 minutes: go around the room. Each person shares one observation. No repeats.
  • 10 minutes: discuss disagreements. Where two people see different things, learning happens.
  • 5 minutes: name the principle. One-sentence lesson from this review.

For Receiving Feedback

  • SHOULD ask "why" before reacting (genuinely, not defensively)
  • MUST distinguish between preference feedback and principle feedback
  • SHOULD write down feedback you disagree with. Review it a day later.

Anti-Patterns

  • Vague positives ("looks great!") that teach nothing
  • Prescriptive commands instead of directional questions
  • Mixing critique of concept with critique of execution in the same breath
  • The most senior person speaking first (anchors the room)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.