The Chess Face-Off
The question
Two agents get the identical brief — build real-time online chess for two players — and are told only that they are competing. One carries the full DreamKid stack: project memory, design enforcement, and the house UX doctrine. The other builds bare. Does the stack show up in the product?
How it ran
- Identical written brief, undisclosed judging criteria, separate working directories and ports.
- Both builds verified with scripted two-player games through checkmate: real-time sync, illegal-move rejection, mid-game refresh recovery, and console-error sweeps.
- Blind scoring by two judges — the owner on real hardware, the orchestrating agent on sealed notes written before the owner's verdict — across visual appeal, desktop experience, mobile experience, and stability.
Owner scorecard 32–14 · Agent scorecard 35–31, both for the equipped build
What the evidence showed
- Both builds played legal chess and passed every functional probe — the gap was never correctness.
- The equipped build held up on a real phone, where products actually get judged. The bare build passed emulated checks but lost decisively in hands-on scoring on looks and mobile feel.
- Design enforcement drew from the house design library, giving the winner a consistent, production-grade finish — and when a project calls for a brand-new identity instead, that goes in the brief.
- Judging on real hardware caught details emulation can't, like how iOS handles small inputs — which is why every test here ends on a real device.
The stack didn't make the agent smarter at chess — it made the product hold up where products actually get used.
Both builds are live. Create a game, send the link to a friend, and judge them yourself.



