- name
Turn a session's design corrections into rules, with their why, in DESIGN.md, a project skill, or a lint check.
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill learn-taste -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill learn-taste -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill learn-taste -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add emilkowalski/skills --skill learn-taste -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/emilkowalski/skills/tree/HEAD/skills/learn-tasteFrom the publisher
Every correction a user makes is taste the agent didn't have. If it isn't written down, the next session makes the same mistake and the user corrects it again. This skill finds those corrections, turns each one into a rule with its reason, and writes it where the next agent will read it.
It does ONE thing: write rules. It never changes component code, and it never adds a rule the user didn't express.
Read the current conversation from the first turn. If the user names earlier sessions and you can read their transcripts (Claude Code stores them as JSONL under ~/.claude/projects/<project>/), read those too.
Explicit corrections are the minority. Look for all five signals:
For each one, capture the user's exact words (or the diff), what you had done, what they wanted instead, and any reason they gave.
Skip what isn't taste: functional bugs, content specific to one screen ("the headline should say Pricing"), and corrections to your understanding of the task.
Completion criterion: every turn has been read, and every correction is listed with its source quote or diff.
Walk every correction through this tree:
Would a fresh agent building a DIFFERENT component in this repo make the same mistake?
├── No (a one-off: this campaign's color, this page's layout) → Skipped
└── Yes
├── Does an existing rule cover it? Check DESIGN.md, CLAUDE.md / AGENTS.md, project skills.
│ ├── Yes, and it says the same thing → The rule failed. Rewrite it stricter
│ │ (a number, a token, "never") instead of adding a duplicate.
│ ├── Yes, and it contradicts → Conflict. Show both; the user picks.
│ └── No → continue
├── Can a violation be found by matching code? → Check candidate.
│ Keep a one-line rule too, so the why is recorded somewhere.
└── Did the user say it applies everywhere, not just here? → Ask where their global rules live.
Otherwise it's a project rule.
Completion criterion: every Phase 1 correction ends as Skipped, Rewrite, Conflict, Check candidate, or a rule to generalize.
Pick the narrowest level that would have prevented the mistake on the next, different component:
If the same correction came up on two or more different components, that's evidence for the class level. If two levels both seem right, ask.
Write the rule strictly: values and token names from this codebase, "always" or "never", no "prefer" or "try to". Use softer wording only when the user framed it as a preference.
Then the why. Use the user's reason, in their words, when they gave one. Otherwise write your best candidate, mark it inferred, and put it in the questions for the user.
Self-test before proposing: read only the rule and its why, then picture the original task. Would an agent that knows nothing else produce what the user wanted? If it could still produce the wrong version, the rule is too vague. Add the value, the token, or the exception.
Completion criterion: every kept rule has a level and a why marked as the user's or inferred.
Check candidate?
├── Yes → lint rule, token restriction, or test, plus a one-line rule in DESIGN.md
└── No
├── Is DESIGN.md's section for this aspect over ~40 lines, AND relevant to only some tasks
│ (motion rules don't matter when building a settings form)?
│ └── Yes → move the whole section into a project skill and leave a one-line pointer in DESIGN.md
└── Default → DESIGN.md at the repo root, under the matching section:
Surfaces · Color · Typography · Spacing & layout · Motion · Interaction · Copy
Create DESIGN.md or the section if it's missing.
Make sure it gets read. A DESIGN.md that no agent loads changes nothing. If neither CLAUDE.md nor AGENTS.md points to it, propose adding this line to whichever one the project uses: Before building or changing UI, read DESIGN.md.
Entry format:
## Surfaces
- **Raised surfaces (cards, popovers, menus) use `shadow-raised`, never a solid border.**
Why: a solid border makes a raised surface look flat and heavy; a semi-transparent shadow separates it from the background and adapts to both themes.
The comment holds the date and the user's words. When a later correction conflicts, it shows which rule is newer and what the user actually said.
Present the report below, then stop.
Write only the approved items. Show the resulting diff of DESIGN.md (and any skill or config file). For a check, implement it and run it across the codebase. If it flags existing code, report the count and ask whether to make it a warning or fix the violations. Never fix them without asking, because that changes component code.
Each inferred why, each ambiguous generalization level, and each global-or-project question. One line each, with your recommendation.
The existing rule, the new correction, and which one you'd keep.
Each check candidate with its exact implementation (the rule config or test), and what it would flag in the current codebase.
One line per skipped correction and why, so the user can override.
Close with: "Say write all or write 1, 3, and answer the questions above."
If the session had no taste corrections, say so in one line. That's a good result, not a failure.
© 2026 Skills Rack.
---name: learn-tastedescription: Turn a session's design corrections into rules, with their why, in DESIGN.md, a project skill, or a lint…---# skills/learn-taste/SKILL.mdFAQ
Download skills/learn-taste/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/emilkowalski/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.