dragoon0x/everything-design-taste

design-critique-facilitation

Running effective design critiques, structured feedback sessions, and group review processes.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill design-critique-facilitation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,322 B
  • docs SUMMARY.md 129 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Design Critique Facilitation

Critique Format

Setup (2 min)

  • Designer presents context: goal, constraints, user, stage of work.
  • Type of feedback requested: "I need help with the navigation structure" (not "thoughts?").

Review (5-10 min)

  • Silent review first (1-2 min). Everyone looks, no talking.
  • Structured feedback: "I notice [observation], which might impact [outcome], because [reasoning]."
  • Facilitator keeps feedback on-topic.

Discussion (5-10 min)

  • Designer asks follow-up questions.
  • Group discusses highest-priority issues.
  • Avoid redesigning in the room.

Close (2 min)

  • Designer summarizes key takeaways.
  • No action items assigned in critique (designer decides what to act on).

Rules

  1. Critique the work, not the person.
  2. Be specific. "The hierarchy is unclear" → "The H2 and body text are too similar in weight."
  3. One person talks at a time.
  4. Opinions are valid when connected to principles or user needs.
  5. "I like it" is not feedback. Neither is "I don't like it."
  6. Seniority doesn't determine correctness.