Manifest

The manifest is the source of truth for generated utility metadata used by docs, doctor checks, and migration tooling.

What it contains

Each utility entry includes class name, category, first CSS declaration, token reference (when present), and supported variants. The site Utilities page reads this file directly.

/generated/emily.manifest.json

How it is generated

Running emily-css build writes the manifest to the output path set in emily.config.json. In this site, npm run emily:sync runs automatically before dev, build, and generate.

{
  "manifest": {
    "enabled": true,
    "output": "data/generated/emily.manifest.json"
  }
}

Current generated shape

The manifest schema (schemaVersion: "1", manifestVersion: 1.1.0) has stayed stable across engine releases. The version field records the emily-css version that generated the file.

{
  "schemaVersion": "1",
  "package": "emily-css",
  "version": "2.0.1",
  "manifestVersion": "1.1.0",
  "generatedAt": "2026-07-05T...",
  "utilities": [
    {
      "class": "bg-brand-80",
      "category": "background",
      "property": "background-color",
      "value": "var(--color-brand-80)",
      "token": "--color-brand-80",
      "declarations": { "background-color": "var(--color-brand-80)" },
      "variants": ["hover", "focus", "focus-visible", "sm", "md"],
      "source": "generated-css"
    }
  ]
}

Two manifests, two jobs

The utility manifest above describes every generated CSS class and powers this site's Utilities page, IntelliSense data, and doctor checks. Separately, Emily Components keeps a component manifest of 303 UI pattern entries — atoms, molecules, organisms, templates, and pages — each tracked with an honest build status (built, needs-css, needs-js, needs-a11y-review, planned, or deferred). See component build status for the current numbers.

Next step

Next: IntelliSense output for editor-focused JSON.