Quickly navigate through the dashboard with your keyboard using the command menu.
Plain instructions, so it works in every AI that reads skills, even pasted into a ChatGPT project. Pick your AI below; we remember it on every skill.
Plain instructions: no scripts, nothing to install.
Security audits on skills.shYour AI reads this line to decide when the skill applies. You never have to call it by name.
“Turn a session's design corrections into rules, with their why, in DESIGN.md, a project skill, or a lint check.”
2 files of instructions.
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:
| Signal | Example | What it tells you |
|---|---|---|
| Explicit correction | "No, semi-transparent shadow, not a border" | The rule, often with the why |
| Silent edit | User changed duration: 400 to 200 in a file you wrote |
Your 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 added | What 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.
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:
| Level | Example | Verdict |
|---|---|---|
| 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.
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.
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.
| # | You said | Rule | Why | Where |
|---|---|---|---|---|
| 1 | "no, semi-transparent shadow, not a border" | Raised surfaces use shadow-raised, never a solid border |
Solid borders look flat and heavy; shadows adapt to both themes | DESIGN.md › Surfaces |
| 2 | Changed duration: 400 → 200 in Dropdown.tsx |
Dropdowns open in 200ms | inferred: 400ms felt sluggish on a surface opened many times a day | DESIGN.md › Motion |
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.
| Invocation | Behavior |
|---|---|
/learn-taste |
Current session, full workflow, stop at the report |
/learn-taste <sessions> |
Also read the named or most recent N session transcripts |
write all / write 1, 3 |
Write the approved items from the last report |
/learn-taste prune |
Read DESIGN.md and propose merges for duplicates, fixes for contradictions, and stricter wording for vague rules. Same propose-then-stop rule |
Stops the generic AI look. Pushes your AI to pick a bold visual direction and build production-grade pages with real typographic and colour choices.
A design partner for designing, critiquing, auditing and polishing a frontend, including writing a DESIGN.md for your project.
Anti-slop rules for company websites: one idea per screen, restrained type and spacing, the polish of top product sites.
Turns the design corrections you make in a session into lasting rules (with the why) in DESIGN.md, so your AI stops repeating the same mistakes.