Taste

Taste is cultivated judgment about what to build, how to build it well, and which choices matter. It is not subjective preference — it is reasoned judgment that can be articulated and defended. Good taste makes things feel inevitable in hindsight.

When to Trigger

Always trigger: The user references engineering taste directly: "taste", "品味", "/taste", "quality judgment" — in the context of code, design, or engineering quality. Non-engineering uses of the word "taste" (food, colloquial "I don't have the taste for debugging") do not trigger.

Trigger: The user asks for holistic quality judgment with no specific fix target:

• "is this good", "feels off", "feels wrong", "something is off", "overengineered", "amateur"
• The key test: the user hasn't specified what to fix — they're asking about overall quality

Trigger only with explicit taste language: A functional request paired with the word "taste" or an unambiguous quality-judgment goal: "build X with good taste", "review the design quality of Y". Generic modifiers like "polished", "clean", "better" in a functional request ("make this more polished", "which approach is better for caching") do NOT trigger — those are normal implementation requests with a preference, not taste judgment requests. Standalone "which is better" without taste/quality language is a functional comparison, not a taste request.