(a) THE MOVE

Stop making users hunt for the action.

Ask for the intent. Pop the one micro UI built for exactly that action. They finish in a tap — and it's saved.

Powered by Jev · a System One model
›
one field · the manifest decides what can happen

(b) THE PROBLEM

Menu-hunting is hard to design away.

A user who already knows their intent still has to climb nested screens to find the button. One field and one panel instead.

Before · nested menus

Settings
Reminders
Follow-ups
New follow-up

4 taps · 3 screens

After · one field

› schedule a follow-up
[ Follow-up panel ]

1 intent · 1 panel · 1 save

(c) THE MANIFEST

Define every intent once.

The developer writes a ledger of intents. That's the whole authoring surface.

intents.manifest
schedule a follow-up→ follow_up · tasks.db
log a work session→ session · log.db
capture a quick note→ note · notes.db
set a focus timer→ timer · tasks.db

(d) THE BUILD LOOP

The LLM runs once. Then it's a controller.

One LLM pass generates each micro UI and wires it to its persistence layer. After that, Jev is the controller — instant intent-to-action.

1Define every intent in the manifest
2LLM generates the micro UI + persistence, once
3Jev routes each intent → matching micro UI → data persists

(e) THE FLIP

Define the intents you want. The rest is done.

No component trees, no wiring. Tell MicroUI what your people do, and it builds the fast path into every action. Vibe-friendly, for non-developers.

Get the build →