learn-taste

作者: emilkowalski

Turn a session's design corrections into rules, with their why, in DESIGN.md, a project skill, or a lint check.

npx skills add https://github.com/emilkowalski/skills --skill learn-taste

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

  1. 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.
  2. 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.
  3. Propose, then stop. Present every candidate and write only what the user approves. A wrong rule repeats in every future session, exactly like the mistake would have.
  4. A check beats a sentence. If a violation can be found by matching code (a banned value, a raw hex instead of a token, a forbidden property), propose a lint rule, a token restriction, or a test. A check runs every time. A sentence in a long file gets skipped when the agent's context is full.
  5. Write for an agent that wasn't here. No "like we discussed" or "the card from earlier". Name the class of component, the value, the token, the file.

Workflow

Phase 1: Collect corrections

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:

SignalExampleWhat it tells you
Explicit correction"No, semi-transparent shadow, not a border"The rule, often with the why
Silent editUser changed duration: 400 to 200 in a file you wroteYour default was wrong and their value is the rule. Find these through notices that a file changed outside your edits, or by diffing a file against what you last wrote
Repeated nudge"Smaller." → "Still too big." → "Ok"Your default was off by the total distance. Record where they landed, not the steps
Revert or rejection"Undo that", picking variant B over A, deleting something you addedWhat not to do. The why is usually missing, so it goes to Phase 3's questions
Confirmed non-obvious choice"Yes, keep the icon outside the button"A choice a fresh agent might not repeat. Record it only if a fresh agent would plausibly do otherwise

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.

Phase 2: Filter

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.

Phase 3: Generalize and find the why

Pick the narrowest level that would have prevented the mistake on the next, different component:

LevelExampleVerdict
Instance"The pricing card gets a shadow, not a border"Too narrow: it only protects this card
Class"Raised surfaces (cards, popovers, menus) separate from the background with shadow-raised, never a solid border"Write this
Universal"Never use borders"Too broad: breaks inputs, dividers, tables

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.

Phase 4: Decide where it goes

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.
  <!-- 2026-11-12: "no, semi-transparent shadow, not a border" -->

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.

Phase 5: Report and stop

Present the report below, then stop.

Phase 6: Write on approval

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.

Required Output Format

Rules to add

#You saidRuleWhyWhere
1"no, semi-transparent shadow, not a border"Raised surfaces use shadow-raised, never a solid borderSolid borders look flat and heavy; shadows adapt to both themesDESIGN.md › Surfaces
2Changed duration: 400 → 200 in Dropdown.tsxDropdowns open in 200msinferred: 400ms felt sluggish on a surface opened many times a dayDESIGN.md › Motion

Needs your answer

Each inferred why, each ambiguous generalization level, and each global-or-project question. One line each, with your recommendation.

Conflicts

The existing rule, the new correction, and which one you'd keep.

Make it a check

Each check candidate with its exact implementation (the rule config or test), and what it would flag in the current codebase.

Skipped

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.

Invocation Variants

InvocationBehavior
/learn-tasteCurrent session, full workflow, stop at the report
/learn-taste <sessions>Also read the named or most recent N session transcripts
write all / write 1, 3Write the approved items from the last report
/learn-taste pruneRead DESIGN.md and propose merges for duplicates, fixes for contradictions, and stricter wording for vague rules. Same propose-then-stop rule

來自 emilkowalski 的更多技能

animate
emilkowalski
從零開始建立動畫,依序做出決定,以判斷整體是否自然流暢——是否該有動畫、目的為何、選用哪種工具、哪些屬性、哪條曲線與時長、如何打斷、如何結束。並撰寫實作內容。當被要求為某個東西加上動畫、增添動態感、讓元件更有生命力,或建立轉場效果時使用。若要評論現有動態效果,請使用 review-animations;若要審查整個程式碼庫,請使用 improve-animations。
animate-expo
emilkowalski
在 React Native 和 Expo 中製作動畫,依照決定動畫是否自然的順序做出選擇——是否要動畫、在哪個執行緒執行、使用哪些屬性、採用彈簧還是定時動畫、手勢如何交接,以及如何降級。使用 Reanimated、Gesture Handler、Expo Router 和 expo-haptics 撰寫實作。適用於在 Expo app 中製作任何動畫、加入手勢、底部面板、畫面轉場、按壓回饋或觸覺回饋,或修復裝置上卡頓的動態效果。適用於……
developmentdesign
animation-performance
emilkowalski
Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Use when an animation is janky, choppy, stutters, or drops frames; when choosing which property to animate; when deciding between CSS and JS animation on performance grounds; or when reaching for `will-change` or GPU layers. For choosing easing, duration, or whether to animate at all use animate; for...
developmentdesign
animation-vocabulary
emilkowalski
反向查詢詞彙表,將模糊描述的網頁動畫或動態效果轉換為精確術語(例如:「彈出視窗開啟時的彈跳效果」→ Pop in;「iOS橡皮筋滾動」→ Rubber-banding)。適用於使用者詢問「那個叫什麼…」或描述某個動態效果卻不知其名稱,並希望獲得正確詞彙以提示AI或設計師時使用。此功能僅用於命名效果,而非設計或實作。
researchdesigncreative
apple-design
emilkowalski
Apple 的介面設計與流暢、物理動態方法,專為網頁轉譯。適用於建構或審查手勢驅動的 UI、彈性動畫、拖曳/滑動/面板互動、動量與可中斷轉場、半透明材質與深度、字體排印(光學尺寸、字距、行距)、減少動態效果,或 Apple 風格介面背後的設計基礎(回饋、空間一致性、克制)。
ask-emil
emilkowalski
Ask which skill or flow fits your situation. A router over the skills in this repo.
developmentproductivity
ask-sonner
emilkowalski
Sonner(React toast 函式庫)使用指南——安裝並接上 Toaster、選用正確的 toast() 呼叫、promise 與 loading toast、更新、關閉及持久化 toast、樣式、主題與圖示、定位與多個 toaster。適用於使用 Sonner 或排解其問題時——例如 toast 未出現、出現兩次、失去樣式、忽略 Tailwind 類別、位於 modal 後方,或未跟隨深色模式。
break-ui
emilkowalski
透過輸入最糟情況的資料來嘗試破壞 UI 元件——長名稱、無法換行的電子郵件、單字母名稱、缺少欄位、超大數量、零個項目、長標籤、非拉丁文字、表情符號、極端數字——接著在「Demo data / Worst case」切換開關後方呈現,並回報所有出問題的地方及各自的修正方式。當使用者要求對元件或畫面進行壓力測試、找出問題或邊界情況,或「試試最糟情況」時使用。若要進行視覺設計評論,請使用 emil-design-eng;若要處理動態效果……
testingdesigndevelopment