For Cursor

The design context Cursor is missing.

Cursor writes the code. Aestheria, the design context layer, writes the system it codes against, so every screen it generates reads like the same product.

Cursor is fast. It is also improvising.

Cursor reads your repo and generates confident code. What it cannot read is your design reasoning: which token means what, how a card is composed, when to reach for a pattern instead of inventing one. So it guesses. The first screen looks fine. The tenth looks like a different company built it.

That drift is not a Cursor bug. It is missing context. The editor has no source of truth for how your product is supposed to look and behave, so it fills the gap with generic defaults every prompt.

Give Cursor a system it can actually read.

Aestheria drops into your project as machine-readable context: an AGENTS.md Cursor reads natively, plus tokens.css and components.css it codes against. Tokens, components, patterns, visualizations, templates, and the rules that govern them, structured to be read, not just looked at.

Point Cursor at the kit once. From then on it scaffolds from your tokens, reuses your components, and follows your patterns instead of reinventing them. The design system is the starter context; the real product is continuity across every generation.

What lands in the repo.

A complete starter system: 443 tokens across 3 themes in light and dark, a component library, 26+ visualizations, 21+ page templates, and 6 SKILL agents that carry the design rules. Own it, edit it, extend it down to the token. Cursor reads the same context your team does.

• 443 design tokens
• 3 themes, light and dark
• 26+ visualizations
• 21+ page templates
• 6 SKILL agents

Questions

Does Aestheria work with Cursor out of the box?

Yes. Aestheria ships an AGENTS.md file Cursor reads natively, plus tokens.css and components.css. Drop the kit in your project root and Cursor has the design context on the next prompt.

Why does Cursor ignore my design system?

Because a design system built for humans to read as documentation is not structured for an agent to consume. Aestheria is an AI-readable design system: the same tokens, components, and rules in machine-readable form, so Cursor can act on them instead of guessing.

Is this a Cursor extension?

No. Aestheria is a design context layer, not a plugin. It is a set of files and tokens that live in your project, so it works the same in Cursor, Claude Code, or any editor that reads your repo.