mcpField
T
teaching-taste

teaching-taste

github.com/dragoon0xDesign & UI680 installsUpdated 35w ago
Repository

About teaching-taste

teaching-taste is a design education skill for helping learners develop judgment without imposing a mentor’s personal style. It emphasizes guided analysis, constrained exercises, precise vocabulary, and tracking growth in independent decision-making.

Key features

  1. 01Teach principles rather than preferences
  2. 02Use questions to guide analysis
  3. 03Practice through constraints
  4. 04Build precise design vocabulary
  5. 05Track independent judgment

Use cases

  1. 01Mentor designers during critique
  2. 02Structure design learning exercises
  3. 03Give actionable feedback on a design
  4. 04Assess a learner’s growth in judgment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dragoon0x/taste-skills --skill teaching-taste

After installing, type/teaching-tastein Claude Code to confirm it loaded.

Details

From the project README

Teaching Taste

Teach judgment, not your personal style.

How to use

  • /teaching-taste Apply teaching constraints to mentoring and education in this conversation.

Constraints

Teaching Methods That Work
  • Guided deconstruction: Look at a design together. Ask questions until they see the principle.
  • Constrained practice: Exercises where the constraint forces taste to the surface.
  • Vocabulary building: Give precise words for what they're already intuiting.
  • MUST let the student reach the observation themselves through questions, not statements.
Teaching Methods That Don't
  • Rules without reasoning ("always use an 8px grid" teaches compliance, not judgment)
  • Exposure without analysis ("look at these great designs" creates appreciation, not skill)
  • Feedback without vocabulary ("this doesn't feel right" teaches nothing actionable)
Avoiding Style Imposition
  • MUST teach principles, not preferences. "Hierarchy should match content priority" is a principle. "I prefer tighter spacing" is a preference.
  • MUST celebrate diverse expressions of the same principle. Two designers can solve the same hierarchy problem completely differently and both be right.
  • NEVER measure a mentee's progress by how much their work looks like yours.
Tracking Growth
  • Specificity of feedback (are reviews getting more precise?)
  • Speed of identification (do they spot issues faster?)
  • Range of reference (are they pulling from wider sources?)
  • Quality of first drafts (are early explorations starting closer to final?)
  • Independence of judgment (can they defend a decision without appealing to authority?)
Anti-Patterns
  • Making every critique about your preferences
  • Gatekeeping ("you just don't have the eye for it")
  • Confusing speed with taste (a slow correct answer is still correct)

Comments

Markdown supported