Docs Philosophy
Compared with shadcn-svelte
shadcn-svelte distributes source-owned components, Svelte Lean is a native-first runtime with optional source-owned styles, and the two can coexist in one application.
Markdown version of this page, for assistants (Markdown for AI)
On this page
Two layers
| Concern | shadcn-svelte | Svelte Lean |
|---|---|---|
| What it is | A distribution model for components | A runtime architecture |
| What you own | The whole component, look and behavior, copied into the application | The styles, optionally (Owned styles) |
| Behavior code | Copied components built on Bits UI | A maintained package, updated through npm |
| Design system | Included | Tokens and per-primitive stylesheets |
Where the line is
- Styles and recipes may be copied and edited; the behavior engine is not, so a focus or keyboard fix reaches every project through npm (ADR 0005, a decision about behavior code only).
- The
slean addcommand is not built; copying a stylesheet is a file operation today.
Coexistence
- Copied components and protocol markup can share a page without doubled listeners: Svelte Lean
behaviors respond only to roots marked
data-slean. - One widget is either a copied component or protocol markup, not both.
What this page does not claim
Nothing about shadcn-svelte's behavior, styling output or accessibility; its documentation is the source. Its interactive components are built on Bits UI, so their behavior JavaScript is the cost measured on Compared with Bits UI; copied files and styles are not measured.