tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble links and wants the app to look like them, or whenever the user complains the AI-generated UI looks generic, boring, cookie-cutter, or "like every other AI app." Make sure to trigger this even if the user doesn't say "design" explicitly — phrases like "make this look good", "build t
npx skills add codeswithroh/tastemaker --skill tastemaker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Tastemaker ## The problem this solves Ask an LLM to build a UI and it defaults to the same handful of patterns: indigo-to-purple gradients, the same rounded card with a soft shadow, the same generic hero layout. This isn't a prompting failure — it's what happens when a model has to invent visual taste from scratch, from a text description, with no grounding and no memory of what the person asking actually likes. Most "design skill" approaches try to fix this by handing the model a bigger catalog of canned styles and palettes to pick from. That helps a little, but it's still generic — a library of canned options, not *your* taste, and it forgets everything the moment the session ends. Tastemaker works differently, on three ideas: 1. **Ground in real pixels, not descriptions.** If the user gives you references (images, screenshots, URLs), extract tokens from the actual reference — deterministically, with a script — instead of writing a text summary of the vibe and generating from that summary. Text-mediated style transfer is lossy; that's most of why AI UI looks generic even when the prompt describes something specific. 2. **Remember, don't re-derive.** Once a project's style is es
- The problem this solves
- Modes
- Aesthetic modes (optional add-ons, not part of the default skill)
- Workflow
- Step 0 — Load memory, don't start cold
- Step 1 — Figure out what you're actually building
- Step 1.25 — Build the reference field
- Step 2 — Establish the style, grounded in something real
- Step 2.5 — Pick the structure, and diversify against project memory
- Step 4 — Build the actual screens
- Step 5 — Close the loop: store taste, then reuse it
- Reference files
- Scripts
- Assets
python3 scripts/anti_slop_scan.py <changed-ui-paths> python3 scripts/audit_motion.py <changed-ui-paths>
What does the tastemaker skill do?
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble links and wants the app to look like them, or whenever the user complains the AI-generated UI looks generic, boring, cookie-cutter, or "like every other AI app." Make sure to trigger this even if the user doesn't say "design" explicitly — phrases like "make this look good", "build t
How do I install it?
Run `npx skills add codeswithroh/tastemaker --skill tastemaker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From codeswithroh/tastemaker, a repository with 75 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.