Codewords · interface cut

The interface had to teach itself before it could be useful.

Build a function
in minutes,
with words you know.
↑ candidate 1 of 50+ ↓ this is what landed
the centerpiece

The Architect — where the eight bets converged.

Codewords Architect interface
H5 · Defer to the human

The AI proposes the spec. The user accepts, edits, or asks for more. Confirmation required at every step — never assumed.

H6 · Draft state matters

The spec lives as an editable draft, not a frozen brief. Refinement is the primary action, not the exception.

H4 · Completeness over Simplicity

Detailed parameters, architect chat, and the spec link — all available at once. Density is intentional.

H8 · Users want it done

Generate is one click away even when the spec is rough. The output unlocks the conversation about how to refine it.

three surfaces, one logic

Landing. Architect. Run. Same grammar throughout.

Every screen earns its density. Every interaction respects the user's emotional state. The architect chat is the soul; landing and run are the front door and the proof.

Landing page
the front door

Landing

The public face. Every word tested against "would an engineer trust this?"

Architect
the soul

Architect

A conversational spec editor. The AI proposes; the user disposes. The interface is the onboarding.

Run / Function page
the proof

Run

A generated function, running. Inputs, outputs, logs — the whole runtime made legible.

← drag to scan →
final pick

"Write code with words."

— after 50+ candidates, the room landed here.

Want to see how we got here?

see the full case study → jump to the research cut →