Reckon

8 screens in the ClaimsDesk demo, generated from a single data fixture

A rules layer for design agents building the software nobody demos: every figure traces to real data, every action fits the record it sits on, every state is drawn before a user finds it.

Design systemUI AgentsCopywriting

Visit the site Talk about a similar project

Client: Internal project
Type: Website + design system
Role: Design, copy and build
Timeline: 3 weeks
Status: Open source

getreckon.vercel.app — the whole page, one scroll.

Work details

TypeWebsite + design system

IndustryAI agents · UI generation

ClientInternal project

RoleDesign, copy and build

Year2026

Timeline3 weeks, blank file to live

StatusOpen source · in progress

DeliverablesRulebook, site, 8-screen demo

Fonts

NewsreaderInstrument Sans

Colours

Built with

Claude

ChatGPT

Next.js

TypeScript

Vercel

Written alongside Claude, shipped on Next.js and Vercel. The rules themselves are plain text, so any agent can load them.

Visit the site ↗

What it needed

Screens that look finished and fall apart on contact.

Agents generate UI fast. A dashboard appears, the numbers look plausible, and none of them reconcile. Empty, loading and error states are missing. Actions sit on records that cannot take them. The demo dies the first time a real user clicks. Reckon gives that generation a rulebook — one an agent can follow and a designer can argue with.

What I did

Brief

One page, one promise: ship the screen, not the guesswork. Everything that was not that got cut — no roadmap, no manifesto, no waitlist.

Structure

The page argues in order: the failure everyone recognises, the rules that prevent it, the proof they hold, then the price — free.

Design

Near-black stage, a single ember accent, Newsreader for the arguments and Instrument Sans for everything else. Screenshots are the illustrations; nothing is drawn that the product does not do.

Build

Next.js on Vercel. The rulebook ships as plain markdown so an agent can drop it straight into its context, and the site is the documentation.

Handover

Open source. Fork the rules, keep what works, argue with the rest — that is the point of writing them down.