emilyCSS Docs
Practical docs for shipping token-first utilities, manifest-powered tooling, and accessible CSS in mixed-stack projects.
Start with Getting started for the full workflow, then move into configuration and Utilities. Tooling pages cover manifest, IntelliSense, doctor, and migration commands without assuming features that are not yet shipped.
Getting started
Install, configure, and generate CSS with manifest and IntelliSense outputs.
Configuration
What each config key does, and how it changes generated CSS and tooling data.
Utilities
Searchable reference generated from the current manifest JSON.
Doctor and migrate
Use doctor checks and migration reports to de-risk utility and class changes.
How the docs are generated
Utilities reads from /generated/emily.manifest.json, which is regenerated before dev and build. That keeps the docs aligned with the classes produced by your current emily.config.json.
The same build also writes data/generated/emily.intellisense.json, used for editor integrations and machine-readable tooling.