How it works
Polyxd turns the answer into a screen.
A small document says what the screen means. Your design system draws it. A verifier checks it before anyone sees it.
13 design systems you already know
12 templates to start from
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Apps only have the screens someone built in advance. Ask for anything else, and you get a paragraph.
Polyxd turns the answer into a screen.
- The ask
- A document, not code
- Your design system draws it
- Checked, then shown
Four layers. Your generator touches one.
- 01
The ask
Typed, spoken, or sent by someone else’s agent.
- 02
A document
44 components, bound to data your app supplies. UI is data, never code.
- 03
Your design system
The real renderer draws it with your tokens, in React, Web Components, Vue or Svelte.
- 04
The check
Schema, patterns, allowed actions, accessibility and an agent task, before it is shown.
Checked before anyone sees it.
- Every label read aloud
- Contrast 4.5:1 and up
- Only allowed actions
- Every value bound to your data
- An agent finished the task
- renders checked across the examples and four products
- 4,680
- tasks finished by agents, by name alone
- 936 / 936
- deliberately broken screens caught
- 20 / 20