AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Design Critique

skill-dragoon0x-taste-skills-design-critique · by Dragoon0x

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.

↗ Repository
— No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-dragoon0x-taste-skills-design-critique

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Design Critique? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills