Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

A user enters a style brief for a logistics dashboard. Jev first recognizes properties of the brief, then two staged requests choose values from authored design options. The generator applies the resolved configuration to the component system; optional critique adds one bounded request.

What Jev decides

Illustrative brief recognitionExample answers · not a recorded Jev response · Source ↗
Question 1 · namesAProduct
YOUR APP
INSTRUCTION

Does the brief name a specific real product or software interface?

STATE

The user’s style brief, without added product context.

JEV · NOUL
YesNo
Question 2 · appearanceKnown
YOUR APP
INSTRUCTION

Is the named product’s visual appearance widely described?

STATE

The user’s style brief, without added product context.

JEV · NOUL
YesNo

App workflow

  1. Submit a brief

    The dashboard panel sends the user’s style description to the generation route.

  2. Recognize the brief

    Jev judges whether it names a known product and other visual properties.

  3. Select design values

    Two staged Jev requests choose typed values from the authored design catalog, with later state including earlier choices.

  4. Apply the configuration

    The design engine maps the selected values onto dashboard components; optional critique adds a bounded final call.

Why it is interesting

The typed output governs the whole interface, so one brief changes a coherent set of palette, shape, type and component decisions without letting the model invent arbitrary CSS values.