the developer's door
Developers
Everything the library holds, and how it is built. Pieces are plain web platform code that you copy into your project and own.
The shelf
Components 61
Behaviour that is boringly correct, with a skin for each register on top. Each has a demo, docs, a conformance table and its prompt.
Recipes 17
Components put together for a real piece of work. Take one whole and change it.
Templates 1
Whole starter sites: one command makes the folder, with the pieces copied in beside it.
Scenes 33
Drawings that do a job, in <sg-scene>, poster first and resting off screen.
Foundations 32
Tokens, the engine, sound and narration, the type tier, the three.js tier and the kernels.
The pencil box 24
The handful of techniques that do nearly all the drawing, each with the scenes that use it.
Tools
- The CLI create a site from a template, or add pieces with everything they stand on. create reaches npm with version 0.2.0; until then, run it from a clone.
- For AI agents SKILL.md for your agent, and an MCP server that searches and adds pieces itself.
- shadcn the pieces served for the shadcn CLI at /r/ (every one but the template).
- llms.txt the whole shelf in one file an agent can read; llms-full.txt has every doc inline.
- custom-elements.json the custom elements manifest, for editors and frameworks.
- GitHub the code, the prompts and the drawings, MIT licensed.
Accessibility and browsers
- Accessibility WCAG 2.2 AA, conformance tables for the components, and the gaps named.
- Browsers the whole suite in Chromium, WebKit and Firefox, and what each still lacks. Not yet on a real phone.
- Handoff what a new team needs on its first day with the library.
Three ideas
-
One component, three registers
Every piece has a quiet, warm and playful register, set for the whole page the way colour mode is. The same progress bar is a pencil hairline for an ERP buyer, a kolam that closes for a homestay, and a string of bunting that fills up for a festival. The register switch is in the View control at the top of this page. The whole page changes, not just the drawings.
-
Every component ships with its prompt
Next to the code sits the prompt you could give an AI agent to make it, and a map from the words in that prompt to the techniques in the code. The library teaches as it serves. Each scene's page carries its prompt on a blue inland letter you can copy, with the map folded away just after it.
-
Behaviour and skin are separate
Keyboard, focus and screen reader support live in a headless core that is boringly correct. The theatre is a skin on top. The quiet skin has to pass an accessibility audit without a single flourish, and every drawing also says what it shows in text.