One source, three platforms
One YAML contract — surface, slots, events, states, tokens, accessibility — projects into working React, Flutter, and Lit. Parity is gated in CI, so there is no port drift and no “the mobile version behaves differently.”
§ Contract-first design system · SemVer 0
Author a component once as a YAML contract — surface, slots, events, states, tokens, accessibility. The Wyrding Way projects it into working React, Flutter, and Lit, with parity gated in continuous integration. Interaction and geometry are identical by construction, not by convention.
Four guarantees, strongest first.
One YAML contract — surface, slots, events, states, tokens, accessibility — projects into working React, Flutter, and Lit. Parity is gated in CI, so there is no port drift and no “the mobile version behaves differently.”
Accessibility scans, localization stress fixtures, WCAG contrast, and cross-stack visual parity fail the build — not the audit. If the pipeline is green, the guarantee held.
A product’s identity is a DESIGN.md compiled into W3C tokens. The same components re-skin per brand; the system’s own brand never competes with yours.
Contracts, tokens, and behavior are machine-readable. A human designer and an AI agent work the very same surfaces, under the very same guarantees.
The scale, the rhythm, and the palette are not decoration — they are the source. Here they are, rendered from their own values.
Raw gold ships dark-native; on light grounds interaction uses the deepened accent.
A product’s identity is a DESIGN.md compiled into tokens. One Button re-skins across presets — TWW plus three demonstration homages — with no change to the contract.
Presets are homages, clearly labelled — “inspired by,” never the trademarked names, and no third-party marks. Each is a real DESIGN.md through the real pipeline.
The site of a design system is the first component a skeptic inspects. Begin with the Button reference and judge the contract for yourself.
Read the Button reference