Vertical packs cover industry workflows. Eng skills cover how code gets written. Taste protocols cover what makes design good — for your brand, on every AI agent you use.
Free to try · No signup needed for conversion · GitHub OAuth to publish
The AI agent stack, today
Industry-specific workflows — investment banking, legal, healthcare. Bundle of named agents + MCP connectors per vertical.
Anthropic + enterprise partners. Big-co territory.
Industrializing fast
Generic engineering skills — TDD, debugging, ship workflows, code review. Tools an agent reaches for, not domain knowledge.
Indie engineers + big-co. MIT-license abundance.
Industrializing fast
Real-world design pattern reference — "how do shipped apps handle KYC / paywall / onboarding?" Industry-wide pattern average.
Mobbin + similar reference catalogs. Proprietary MCP behind paywalls.
Just launched
Color, type, spacing, motion, brand voice — encoded as portable skills any AI agent can read. Your taste, on every tool.
Open category. No incumbent yet.
Still being named.
The first three layers are filling up fast — workflows, code, and now patterns. The fourth one — the layer that decides whether the output is on-brand, not just average — is mostly empty. That's the one we're building.
Why now
Vertical packs know how KYC runs. Eng skills know how to write a passing test. Neither of them knows whether a button color is right, or whether a spacing rhythm makes the brand feel cheap. When generation gets free, judgment is the bottleneck — and judgment lives in taste.
An investment-bank financial report doesn't look like a DTC brand site doesn't look like a family memory app. Taste belongs to the designer or founder, not the industry. Bundle it into a vertical and you get a thousand products that look the same.
Engineering skills are verifiable — the test passes or it doesn't. Taste is evaluable — it looks right or it doesn't. Two different evaluation mechanisms, two different review surfaces. Mixing them into the same skill registry pollutes both. Taste deserves its own protocol, its own evaluators, its own community.
Already on the protocol
Six to twelve months until the big tools roll their own design layer. Until then, the taste protocol is a public good — and the people defining it now will have shaped the category they're using.
Built by designers, used by anyone who cares about taste.
— A protocol layer for taste · Open spec · Free to publish
One command connects all your AI agents to the full skill registry.
$ npx design-skills-hub
Copied!