Get started
Start with the contract
Choose the component or pattern first, then use its stable platform alias instead of creating a local look-alike.
For designers
Apply the Pasture or Atlantic token set, use canonical HE component names and annotate data freshness separately from health severity.
For developers
Load generated tokens and component CSS on web, or use HeTheme and exported widgets in Flutter. Preserve native semantics before adding ARIA.
Workflow
Requirement → existing pattern → component contracts → token expression → accessibility review → test evidence → governed release.