Questions, mostly answered
If you don't find what you're looking for here, ping us in the community channel. We answer fast.
Is LSD a design system or a framework? +
Neither, exactly. LSD is a design substrate — a layer beneath both. It produces the tokens, surfaces, and behaviours that any framework (or none) can consume via the .lsd package.
Do I need to use the bundled builder? +
No. The builder is one consumer of the runtime. The same primitives can be hand-authored or generated by an agent against the same public contract.
Does it work with my existing stack? +
If your stack reads CSS variables and runs JavaScript, yes. We currently ship adapters for React, Svelte, Astro, and vanilla HTML. The .lsd package is framework-agnostic by design.
How does Aurora differ from a typical tween library? +
Aurora treats your page like a DAW track. You author named beats and envelopes on a timeline; the timeline is the source of truth, not a config object. Scroll-tied regions and click-tied regions sit on the same ruler.
Can I export just the design tokens? +
Yes. Every .lsd package can be exploded into CSS variables, JSON, Tailwind config, or Figma tokens via the CLI. Tokens are first-class citizens of the package, not by-products.
Is there a free tier? +
The framework itself is MIT. The hosted builder has a generous free tier — unlimited personal projects, three commercial seats, full CLI access. Paid plans unlock team collaboration and the AI co-authoring layer.
How does the AI co-author work? +
An MCP-aware agent reads the same .lsd package you do. It can compose surfaces, wire behaviours, and propose component variants — but it always commits diffs you can review and revert.
What about accessibility? +
The Orion contrast law is enforced at the surface layer — your palette physically cannot produce inaccessible text/background pairs in the named tiers. Motion respects prefers-reduced-motion in every primitive we ship.