Tastes
Taste skills for AI coding agents.
A taste skill is a complete visual identity — tokens, components, layouts and motion — that your coding agent applies to every screen it builds. Not a style guide it may ignore, not one template it copies: a point of view it can hold across a whole product.
12 of 441 tastes · Blogs & publications · Handmade & organic · Light
In the studio · 12
Packaged. Covers are each package’s own exemplar page; a taste lists once it passes Taste QA twice.
ProScrapbook
Cut paper, tape and stickers on warm card stock
Caveat / Atkinson HyperlegiblePro
ProTypewriter
Typed index cards
Courier PrimePro
ProZine
Cut-and-paste photocopy slides
Anton / Cutive MonoPro
ProCrayon
Wax-crayon learning UI — soft primaries, big targets, gold stars that are earned
Grandstander / AndikaPro
ProUkiyo-e
Flat blocks of Prussian blue and vermilion on washi, every shape held by a sumi keyline
Kaisei Tokumin / Zen Kaku Gothic AntiquePro
ProLinocut
Carved black linework and one vermilion ink on rag paper, pulled by hand
Coustard / Familjen GroteskPro
ProPatchwork
A pieced quilt of prints and solids, stitched and bound, with every word on a solid patch
Calistoga / Inclusive SansPro
ProWash
A watercolour film: washes bloom wet-on-wet, dry to hard edges, words sit on clean paper
Spectral / MulishPro
ProMixtape
The home-made cassette: J-cards, ruled track lists and one red marker
Sedgwick Ave Display / Archivo NarrowPro
ProEndpaper
A marbling film: ink drops spread, a comb pulls them into feathers, titles sit on bound books
IM Fell English / Crimson ProPro
ProMixtape Card
Cassette J-card cards: a drawn tape, a marker title, a ruled track list and one red stroke
Sedgwick Ave Display / Chakra PetchPro
ProPinboard Card
A cork board with a pinned index card, sticky notes and red string between pins
Kalam / SenPro
By use
What are you building?
How to install a taste- Landing pages380 tastesEditorial, Swiss, Brutalist…
- Web apps & dashboards227 tastesEditorial, Swiss, Terminal…
- Online stores169 tastesSoft Depth, Playful Pop, Quiet Luxury…
- Portfolios47 tastesEditorial, Brutalist, Quiet Luxury…
- Blogs & publications78 tastesEditorial, Swiss, Risograph…
- Docs & developer tools49 tastesBrutalist, Terminal, Midnight…
- Launch videos119 tastesGlow UI, Kinetic Type, Terminal…
- Social images & OG cards98 tastesSignal Card, Quote Card, Infographic…
- Pitch decks & slides88 tastesStatement, Sketchnote, Keynote Dark…
- All tastes441 tastesSearch by style, tone or keyword
Questions
Questions, answered.
- What is a taste skill?
- A folder your coding agent reads before it designs anything: a manifesto, design tokens, component and layout rules, motion, and do/don’t examples. Install it once and every page or screen the agent builds follows that identity instead of framework defaults.
- Which agents does it work with?
- Claude Code, Cursor, Codex, Gemini CLI and any agent that reads Agent Skills (a SKILL.md folder). The install guide covers each one.
- Does it work with my framework?
- Yes. Tokens ship as CSS variables, Tailwind v3 and v4 config and neutral JSON, and the rules are written for plain HTML/CSS, so React, Next.js, Vue, Svelte or static sites all work.
- How do I know it actually works?
- A taste goes on sale only after it passes Taste QA twice: a fresh agent builds the same standard brief with the skill installed, and the result is graded against a written checklist. The before/after on each skill page comes from a run of that brief.