DTCG token extensions
Documentation, usage, lifecycle, accessibility, search, and governance metadata authored under $extensions["recipes.designlasagna"].
Docs
Understand the source.
Use the output.
References for the optional metadata you author in existing standards and the generated manifests your tools consume.
Start here · schemas
Two layers, one system
Design Lasagna extends DTCG and CEM source files where they need more context, then generates dependable manifests for validation, automated documentation, and editor tooling.
Authoring extensions
Enrich existing standards
These optional, human-authored fields live inside the source files your team already maintains. They do not replace DTCG or CEM.
CEM extensions
Optional lifecycle status, deprecation details, and migration targets for Custom Elements Manifest declarations and members.
Generated manifests
Publish derived views
These references describe generated output files—not another source format for your team to maintain.
Resolved token manifest
Token identifiers, paths, resolved values, modes, and source-side metadata for documentation and tool consumers.
Utility manifest
Utility classes, categories, and the structured information needed for editor-aware CSS workflows.
Editor workflow
Looking for editor support?
The Design System Language Server reads published manifests to provide completions, hover information, diagnostics, and migration guidance where work happens.