Action–State Reference Suite

Four reference apps (autos, funnel, sudoku, tinker) implemented across multiple frameworks to validate that action–state is a genuinely framework-agnostic pattern. Framework port counts differ by app — autos 7, funnel 8, tinker 8, sudoku 10 (8 core + 2 Custom Element variants). The frameworks used across the suite are React, Stencil, Lit, uCE, Svelte, Solid, Preact, and Vue; not every app has every port (e.g. autos has no uCE build). The hypothesis held: nearly identical behavior and output with a shared Tailwind plugin and the same component structure.

The suite got an unplanned stress test on 18 November 2026, when all four Solid builds were ported from Solid 1.9 to 2.0. That release changed how stores work: createStore moved into the core package, autos-sld had to give up createMutable, and a write is no longer visible to reads until the next flush. Code that wrote a value and then read it back, such as saving state or restoring a saved pick, quietly read the old value. In every app the fix stayed in src/utils/store.ts. Each action now works out its next values first and writes them together in a single draft setter. The action interface the components call did not change, so components needed only small framework fixes: onMount became onSettled, an effect was split, and an aria-checked value was corrected. A breaking change to the framework's own reactivity landed on the state layer and stopped there, which is the separation the pattern is meant to provide.

This directly informed the architectural foundation for MCP-driven UI — if action–state works the same everywhere, agents can drive any implementation through the same contract.

The suite predates the YAML platform by years — it was independent exploratory work, not a deliberate stepping stone. When the spec-driven platform idea eventually surfaced, the empirical proof was already in place. Each framework implementation was effectively a manual exporter: the "component patterns" and "action-state pattern" were an informal spec; the implementation work was translating that spec into each framework's idiom. The platform later automated exactly what was being done by hand.

See projects for the deployed apps.