Early preview · spec v0.1

Interfaces that show up when you need them.

Ask for something. A real, accessible interface is drawn for that moment, in your design system. When the task is done, it goes.

Meaning, not pixels

Four layers. The model touches one.

It chooses the intent, the pattern and the components. Your design system supplies every token. The verifier signs the top.

Any design system

Taken apart. Rebuilt in yours.

The same document, drawn again from thirteen design systems' real tokens. No retraining.

People and agents

One tree. Every kind of user.

Screen readers read exactly what agents press. If an agent can't finish by name alone, the surface fails.

Recognition, not recall

Gone when it's done. Familiar when it's back.

Same pattern, same order, same labels, same controls, the next time you ask.

Verified

Checked before anyone sees it.

Accessibility, layout, your team's rules, and whether an agent can complete the task.

  1. Ask
  2. Mean
  3. Build
  4. Use
  5. Return
  6. Verify
Polyxd Studio · for design and product teams

Your taste, enforced. Your product, measured.

Designers set the direction: voice, rules, patterns, how much freedom the model gets. Product managers register what the product can do and what done looks like. Studio shows every surface the model made, why it came out that way, and how it performed.

Already built

24 scenarios, rendered by the real renderer.

Every example in the spec, each in a different design system. Nothing here is a picture.

Open the gallery to try them at every width, in every pack →

semantic components, one vocabulary
24
verified renders, zero accessibility violations
1248
agent tasks completed by name alone
936/936
injected defects caught by the verifier
20/20

Open spec. Any model. Your design system.

Spec, renderer, design-system packs and verifier are Apache-2.0. They work with any model that writes JSON. Studio is where your team directs it.