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.
19 of 441 tastes · Docs & developer tools · Technical & digital · Light
In the studio · 19
Packaged. Covers are each package’s own exemplar page; a taste lists once it passes Taste QA twice.
ProEnterprise
Calm, dense, accessible admin UI
InterPro
ProRaw
Exposed frames, heavy claims
Bricolage GrotesquePro
ProCells
Dense grids for power users
ArchivoPro
ProClassic
One-bit 1984 desktop UI
Pixelify Sans / Atkinson Hyperlegible NextPro
ProDocs
Developer docs done right
Rethink SansPro
ProInstrument
Hardware panels, knobs and readouts
Krona One / Encode SansPro
ProGraph
Graph paper, graphite and one blue ink — every number shows its working
B612Pro
ProGraph Deck
Engineering-notebook slides on graph paper, working shown in blue ink
B612Pro
ProRetro OS
The 1990s desktop as a real interface: bevels, title bars, dialogs and pixel icons
Jersey 15 / PT SansPro
ProBevel
A launch film on a 1990s desktop: windows pop, a pixel cursor drags and clicks
DotGothic16Pro
ProRetro OS Deck
Nineties-desktop slides with bevelled windows, dialog boxes and progress-bar metrics
Pixelify Sans / Atkinson HyperlegiblePro
ProOne Bit
Pure black on white, every tone dithered, every rule one pixel
Micro 5 / ChivoPro
ProDither
A 1-bit film: black and white, every tone dithered, windows that redraw frame by frame
Jersey 15Pro
ProOne Bit Deck
Pure 1-bit slides: black and white only, dithered charts, bitmap type and pixel icons
Jersey 10 / DotGothic16Pro
ProMission
1960s mission control — orange fields, navy screens, a patch for every flight
Hubot Sans / Public SansPro
ProLiftoff
A mission-control film: the clock hits zero, telemetry ticks, the arc draws into orbit
Michroma / IBM Plex Sans CondensedPro
ProMission Deck
Mission-control slides that count down from T−2 to the go you are asking for
Michroma / IBM Plex Sans CondensedPro
ProRetro OS Card
A bevelled 90s window on a teal desktop: navy title bar, dialog buttons, pixel icons
Jersey 15 / PT SansPro
ProOne Bit Card
Pure black and white: dithered tones, a bitmap display plate, 1px rules, pixel icons
Micro 5 / ChivoPro
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.