For Cursor
Aestheria for Cursor.
Cursor writes your code. Aestheria writes the system it codes against. Drop the kit in your project root and Cursor generates on-system UI from the first prompt.
The problem
Cursor reads your codebase, not your design system. Without structured context it guesses: it invents tokens, restyles components, and drifts from your brand a little more every session.
What Aestheria gives Cursor
A machine-readable design context layer Cursor reads natively. Tokens with usage rules, a component library, patterns, and an AGENTS.md that tells Cursor where to look. The same source of truth your team browses in Studio.
Questions
Does Aestheria work with Cursor?
Yes. The kit drops into your project root and Cursor reads it like any other context in your repo. No plugin required.
How does Cursor read my design tokens?
Tokens ship as machine-readable CSS and JSON with usage descriptions, so Cursor knows which token belongs where, not only its value.
Will generated UI stay on-brand across prompts?
That is the point. Aestheria preserves design context across sessions, so the next screen feels like the same product as the last.
Drop the kit in project root. Done.
Get the kit