SynthesisUI
One system · every screen

Nineteen simple prompts, the kind anyone types. A site and its dashboard that speak the same language.

Claude Opus 5.5 built Lumen Bikes piece by piece - the home page, a booking page and a six-screen workshop dashboard - with SynthesisUI and the Moss design system installed. Nothing here was retouched. Click through it.

Start free →From your own code, from scratch, or from a system like Moss - you choose after signing up.or try it on your project first, no account
model claude-opus-5-5design system Mossbuilt Oct 6, 202619 simple prompts · 49.2 min

Click through the screen itself - every link in it works, like on the real site.

What the person typed7 prompts
  1. create a header for the lumen bikes site with the green color. the links go to the sections of the home page
  2. create the hero of the home page: a title, a short text, a button to book a test ride and a picture of a bike
  3. add a section with the bikes: city, cargo and folding, each with a picture, the range and the price
  4. put a filter on the bikes section, by type and by price
  5. add a how it works section with 3 steps
  6. add a section with what riders say, 3 quotes with name and neighborhood
  7. add a final call to book a test ride and a footer with address, hours and whatsapp
Homelumenbikes.example/
How it got there

What happened behind those 19 prompts

Every number below is read from the project's own record (_synthesisui/ledger.jsonl) and the agent's conversation - nothing estimated.

You "put a filter on the bikes" Claude Opus 5.5 the agent, in Claude Code prompt SYNTHESISUI - EVERYTHING THE AGENT DOES GOES THROUGH HERE asks · writes answers · checks 1 · Moss arrives 85 names in your theme the guide · the agent wired 2 · Session opens on the latest Moss? yes - v1, same rules ✓ 3 · Agent asks decision · structure · recipe card blueprint arrives 4 · Every write checked against Moss named by the system ✓ 5 · System learns what the project needed reaches Moss's owner → v2 next session: the new version arrives on its own Your design system Moss in this example - or one built from your own code Tokens & rules 85 names · type scale · rules Blueprints button · card · chip · phone menu… Knowledge decisions · structure · requests installs reads grows it Complex inside. Simple for you: you type a plain sentence, and what lands is consistent.
You talk to the agent, the agent talks to SynthesisUI, and SynthesisUI always answers from your design system - its tokens and rules, its blueprints, and the knowledge it keeps for your project. Every step in the middle happens on its own; the consistency is ours to guarantee, not yours to remember.
2 · The session opens · 19×

On the latest Moss?

  • a session exists, for the host the system came from
  • one system governs this repo - Moss
  • Moss v1 installed is the version published
  • its CSS and its rules match what the platform serves
3 · The agent asks · 41×

What does the system already know?

  • recall ×8 - Moss's memory: the dashboard header wears the primary
  • preferences ×7 - how a page and a dashboard are built
  • describe_component ×11 - the recipe before the code
  • 9 blueprints and the phone menu, brought from Moss into src/components/
4 · Every write · 100×

Did it write the system?

  • checked on its own, in 60 files
  • 0 names that do not exist in Moss
  • 100% proportion & type - 679 spacing values and 325 text sizes on Moss's scale
  • 100% token coverage in the screens' code
5 · The system learns

Where does what it needed go?

  • what the agent needed and Moss did not have is filed, not invented
  • the record goes to the system's owner
  • a yes from the owner becomes the next version
  • every project on Moss gets it at its next session

Every value above came from a system the agent could ask. Yours can start from your own code, from scratch, or from one of ours.

Start free →