Portable style contract for AI-built UI
Define taste once. Enforce it everywhere.
TasteKernel turns your tokens, component rules, motion rules, and copy rules into one portable contract you can lint locally, run in pull requests, and export into the tools that generate your UI.
Local-first. No source upload by default. Built for React, Next.js, and Tailwind.
TokensComponentsMotionCopyCI-readyExport-aware
Why TasteKernel
AI makes UI faster. It also makes drift cheaper.
The moment you start generating screens, small inconsistencies multiply. Raw colors sneak in. Shared components get bypassed. Motion gets louder. Copy loses tone. A few fast wins turn into a product that feels stitched together instead of designed.
- Hardcoded values where tokens should be
- Raw HTML where shared components should be
- Variant and size drift across the same component family
- Copy that sounds off-brand or uneven
- Pull requests that look fine until you zoom in
TasteKernel gives you one source of truth for how the product should feel, and one enforcement layer to keep it there.
How it works
A contract for taste, not a heavyweight design-system rollout.
One contract. Multiple surfaces. Minimal overhead.
Step 1
Define the contract
Start from a template or import what you already have. Put tokens, component rules, motion rules, and copy rules into one human-editable contract.
Step 2
Enforce the contract
Lint local changes, run checks in pull requests, and apply safe autofixes when the mapping is exact. Catch drift before it spreads.
Step 3
Export the contract
Generate reusable instruction packs and rules fragments for the tools that shape your UI, from v0 to Figma MCP to Cursor and Claude.
What you can enforce
Keep every layer of the interface aligned.
Token discipline
Catch raw colors, arbitrary Tailwind values, off-system spacing, radius drift, and typography shortcuts before they spread through the app.
Component correctness
Require the right import source, block deprecated components, and enforce allowed variants and sizes for the shared components that define your UI.
Motion guardrails
Keep transitions fast, intentional, and product-appropriate with duration, easing, and inline-animation rules.
Copy consistency
Flag banned phrases, suggest preferred replacements, and keep text aligned with the tone your product is supposed to carry.
Cloud run history
Track contract versions, run metadata, findings, and export artifacts without uploading your full repository by default.
AI-tool exports
Push the same contract into the tools that help generate your UI so prompts, components, and implementation rules stay aligned.
Exports
One contract. Multiple tool surfaces.
TasteKernel is built for the reality of modern UI workflows: hand-written code, generated code, design-to-code bridges, and assistant-driven edits all happening in the same product.
v0 instructions
Concise generation rules for token use, component use, motion, and copy.
v0 registry alignment
Structured token mappings, component inventory, required import paths, and naming conventions.
Figma MCP rules
Implementation rules for design-to-code flows, including token fidelity and hardcoded-value avoidance.
Cursor and Claude fragments
Portable context that keeps assistant edits aligned with the same contract you lint in your repo.
Dashboard
Publish contracts, inspect runs, and keep the system visible.
The dashboard gives you one place to edit and publish contract versions, inspect recent runs, review findings by file and rule, and download export files from the same source of truth.
- Active contract version and version history
- Recent runs with severity breakdowns
- Per-file findings and waived exceptions
- One-click export downloads
- API keys for CI ingestion
Trust
Built for teams that care about control.
TasteKernel is local-first by design. Your contract lives with the codebase. Cloud sync is optional. By default, the platform stores contract data, run metadata, findings, and artifacts, not your full source code.
- No full repo upload by default
- Snippet storage can stay off
- API keys hashed at rest
- Audit-friendly contract history
- Project-level control over active versions
Who it is for
Made for fast-moving teams that still care how the product feels.
- Founders shipping with AI and design intent
- Product teams using React, Next.js, and Tailwind
- Developers maintaining shared UI standards across multiple contributors
- Teams that want consistency without design-system bureaucracy
FAQ
Common questions
Is TasteKernel a design-system platform?
No. TasteKernel is a style contract and enforcement layer. It helps you define how the product should feel and keep generated and hand-written UI aligned to that contract.
Do I need to upload my repository?
No. The contract is local-first, and source upload is not required by default.
What stack does it support?
TasteKernel is built for React, Next.js, TypeScript or JavaScript, Tailwind CSS, CSS, PostCSS, and TSX or JSX in the current product scope.
Can it fix issues automatically?
It can apply safe autofixes when the mapping is exact, such as known token-class replacements, import-path corrections, and one-to-one copy replacements. Structural or ambiguous fixes stay manual.
Does it work in CI?
Yes. TasteKernel is designed for local CLI use, pull-request checks, markdown summaries, SARIF output, and cloud run history.
Taste is a system. Treat it like one.
Define the rules once. Keep every commit, pull request, and AI-generated screen aligned to the same product standard.
For modern web teams working in React, Next.js, and Tailwind.