Skip to content

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

design-critique

Verified

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.

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)
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall