Contracts
Every addable object uses the shared registry envelope and returns RuleResult diagnostics.
A cleaner static-app v2 proof with real Tailwind output, reusable primitives, mock product data, design presets, and a style guide that shows full page variants.
The platform exposes one repeatable operation: register the building block, implement it with primitives, render realistic data, and run the gate.
Every addable object uses the shared registry envelope and returns RuleResult diagnostics.
Themes and color schemes are registered and previewable from the style guide.
Tailwind v4 compiles the CSS and the style-guide runtime is bundled with esbuild.
Pipeline
Agents should not invent a separate design method. They follow the same sequence for every primitive, block, effect, or template.
Use the registry and agent guide to see what already exists.
Compose registered primitives and blocks before adding anything new.
New blocks, effects, themes, and schemes all use the same manifest envelope.
Validation and page evals return deterministic failures with fix hints.
Mock data
This section reads from app/config/api-contract.json, the same easy mock-data pattern v1 uses for sourced blocks.
Healthcare
Commerce
Services
Contracts
These contracts are enough to prove the architecture without pretending visual taste can be fully automated.
Defines the root vocabulary for CSS and Tailwind v4 aliases.
The gate fails when required token dependencies are missing.
Owns reusable UI recipes and helper APIs.
Blocks fail when they copy managed primitive classes directly.
Owns tokenized motion and reduced-motion behavior.
The style guide activates registered effects through bundled JS.
Owns fixtures, matrices, screenshots, and human review paths.
The style guide renders primitives, states, schemes, and themes.
Proof
This page is intentionally contract-heavy: it should expose what is implemented and what still needs human design judgment.
10+
core contract records
3
design-pack page previews
1
esbuild-bundled runtime proof