One source, three platforms
A single YAML contract ships to React, Flutter, and Lit. Parity is gated in CI, so there is no port drift and no “the mobile version behaves differently.”
A field manual for building one product across web and Flutter — from a single design source.
Vol. 0 · Contract-first design
A component in The Wyrding Way is written a single time — a contract of surface, slots, events, states, tokens, and accessibility obligations. From that one document the system projects working React, Flutter, and Lit, with parity gated in continuous integration.
Interaction and geometry are identical across platforms by construction, not by convention. The system is young and honest about it: every capability carries an availability note, and the facts behind these pages are generated from the producing repositories, never hand-typed.
A single YAML contract ships to 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. The promise is enforced, not asserted.
A product’s identity is a DESIGN.md, compiled into W3C tokens. The system’s own brand never competes with yours; the same components re-skin per brand.
Contracts, tokens, and behavior are machine-readable. A human designer and an AI agent work the very same surfaces, with the same guarantees.
A product’s identity is a DESIGN.md compiled into tokens. Below, one Button is rendered under TWW’s own brand and three demonstration homages — the contract underneath never changes.
Presets are homages, clearly labelled — “inspired by,” never the trademarked names, and no third-party marks.
The site of a design system is the first component a skeptic inspects. Begin with the Button reference and judge for yourself.
Read the Button reference