record_taste_decision
Capture design taste decisions as they happen, including chosen option, rejected alternatives, and rationale, to refine future taste interviews.
Instructions
The Taste Engine's learning loop — record a taste, direction, or design decision the MOMENT it is made during real work (an accent chosen, a nav pattern rejected, a name direction picked, a type pairing approved), not just at interview time. Each record carries the project, a short dimension name (a standard one like color/navigation or a new category like iconography/sound), what was chosen in the user's words, the alternatives rejected, why, and a source: 'user-directed' (the user asked for it), 'user-approved' (the user accepted a proposal), or 'user-corrected' (the user overrode a generated choice — the highest-signal record). Recorded decisions evolve every future get_taste_interview kickoff: recurring choices return as suggested defaults on their dimension's question, and decision categories no standard question covers become NEW interview questions. Record liberally — every committed decision is calibration data.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| why | No | The stated reason, if the user gave one. | |
| source | No | How the decision was made — defaults to 'user-directed'. 'user-corrected' (user overrode a generated choice) is the highest-signal record. | |
| profile | Yes | Taste profile name (see list_taste_profiles). | |
| project | Yes | Project the decision was made on. | |
| decision | Yes | What was chosen, in the user's words — e.g. 'amber-phosphor accent, period-accurate not decorative'. | |
| rejected | No | Alternatives considered and passed over. | |
| dimension | Yes | Short lowercase dimension name — a standard one (typography, spacing, color, layout, motion, imagery, entrance, loading, navigation, aesthetic, libraries) or a new category the standard set doesn't cover (iconography, sound, naming, …). New categories become new interview questions. |