Built on the standards · DS4AI
The parts a demo does not show, built right.
The Design Suite for AI is the design counterpart to the precision tools, a sibling to PT4AI and PC4AI. It is a family of small, dependency-free web primitives, one for each thing a shipped page owes a reader that a look-at-it review cannot see and that fast, AI-assisted building drops. You adopt one at a time or compose the set.
What is actually new here
The correctness a demo does not show, named and checkable.
None of these things are exotic: readable color, operable controls, honest states, a hardened surface, findable metadata, stable delivery. They have been missing from a great deal of the web for a long time, and AI-assisted building makes them missing more often, for the same reason at greater scale: a model optimizes for what the demo shows, and these are exactly the parts a demo does not show.
The standard beneath the suite is MISSING, the model of those six gaps. Each primitive closes one, and a surface that closes all six is MISSING Conformant. The suite carries the same discipline as the standards above it: it describes what a check found rather than asserting a verdict, and it never calls a hardened site secure.
What is in the suite
Six axes, one primitive each, composed by a standard.
Each is zero-dependency and native-first, themed together through TEMPER, and each audits against the standard from the served HTML rather than asking to be taken on trust.
Perceivable · TEMPER
A semantic color system: five appearance modes on one token schema, every color solved to a contrast floor by the engine rather than chosen by eye. It themes the whole suite, and it is what themes this site.
Operable · GRASP
Accessible interaction components across the WAI-ARIA common working set, reachable by any input or assistive technology, built native-first on the real element wherever one exists rather than a div dressed up as a control.
Off the happy path · LUCID and GRACE
LUCID is reader-sovereign progressive disclosure, a term opened at three depths, a gloss to follow, an explainer to use, and detail with a path to source to check. GRACE renders the honest states a happy-path build skips: loading, empty, error, and not-found.
Hardened · HASP
The client-surface security posture a page declares to the browser, across three altitudes: response headers, markup integrity, and secrets. It audits declared hardening for effect rather than mere presence, and never calls a site secure.
Findable · BEACON
The head metadata, social cards, structured data, and site files that let a page represent itself correctly to search engines, shares, and agents, emitted into the server-returned HTML where the non-JS scrapers that matter can read it.
Fast and stable · FLEET
The markup and resource hints that make a page load fast and stable against Core Web Vitals, with a runnable audit, and honest about the boundary a frontend primitive cannot cross: it cannot encode a pixel, bundle a module, or set a header.
Where it sits
A standard, a manifest, and an auditor, so a build can check itself.
MISSING ships the machine-readable manifest of the family and a conformance auditor that reads a shipped surface across all six axes and declares the ones a static check cannot reach rather than reporting them clean. The color tool is the suite's live front door for TEMPER. Every piece is Apache-2.0, dependency-free, and calls nothing home.