system.css is a design engine, not a component library. You write
semantic HTML and a few composition classes, then set inherited custom
properties: --hue, --bg, --fg, --type, --lift, --gap. There
is no .btn-primary. A button is a button.
This site is generated from the same files an agent loads to work on a project built on the stack.
- How-to: start a project, the shell, a page, a form, a rocket, the server, migrations.
- Engine: the
system-cssskill, one page per section. - Components: the
datastar-componentsskill. - Land & stream: the
land-and-streamskill, the server half. - Charts: the
svg-chartsskill. - Advanced: the wash, the stack, canvas and rise, composing screens.
- Lab: every specimen, live.
- Demos: full pages on the engine.
- Skills: the four skill files, raw.
Laws
- One file, one spine. Layers decide the cascade. Specificity is zero.
- No new classes. Compose the primitives and the knobs. A gap is raised at the lab, not filled with a class.
- Knobs are steps, not lengths.
- Nothing shifts. A change of state or value does not move its neighbours.
- Navigation is the browser's. The server owns state. Signals are rare.
Start
Read Start a project. Keep the Engine open while you build. The Lab shows what correct looks like.
migrate runs the SQL migrations. The how-to shows the boot wiring.