learn-taste
Turn the design corrections a user made during a session into rules the next agent follows. Collects every correction (explicit ones, edits the user made to files you wrote, repeated nudges, reverts), generalizes each to the right level, confirms the why, and writes it as rule plus reason into the project's DESIGN.md, a project skill, or a lint check. Only runs when explicitly invoked.
Install
With your agent
Install OMGSkills skill "emilkowalski/skills:learn-taste" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/emilkowalski/skills /tmp/skills && ln -s /tmp/skills/skills/learn-taste ~/.claude/skills/learn-tasteFrom README
Learning Taste 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. Hard Rules Only the user's taste. Every rule traces back to something the user said, edited, or confirmed. Never add a rule because it seems like good practice. That's your taste, and your taste is what the user was correcting. Never invent a why. If the user gave no reason, propose one marked inferred and get it confirmed before writing. A wrong why is worse than none: the next agent extends the reasoning to cases it doesn't fit. Propose, then stop. Present every candidate and write only what the user approves.
More from this repo
animation-performance
Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when...
break-ui
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing...
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible...