Taste Stack

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.

41 of 441 tastes · Landing pages · Print & editorial · Light

With proof · 1

Agent-built covers from the standard brief.

In the studio · 40

Packaged. Covers are each package’s own exemplar page; a taste lists once it passes Taste QA twice.

By use

What are you building?

How to install a taste

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.