Instinct
Next.js demo where Jev picks real shadcn/ui components and settings from a fixed catalog to render a described UI.
Overview
Instinct is a UI generator demo built as a content piece for a post about System One models. You describe a case in free text, such as a customer table with name, status and plan, and Jev never writes code or copy. It only answers typed Choice, Noul and Score questions over bounded sets of real shadcn/ui components, page blocks, fields and styles, and the app renders whatever it picked, configured the way it decided.
The point is to show that typed decisions over a real catalog are enough to produce a correctly typed, on-brand React component, with no generated text anywhere except the user's own input. It runs on Next.js 16 with Hono, Tailwind v4, zustand and the TypeSafe SDK. For public deployments, each visitor gets five generations on the shared key, then is asked for their own key, which stays in localStorage and gets a fresh SDK client per request. The README notes the cookie-based counter is a cost cap, not a security boundary.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which shadcn/ui component or page block best fits this description?(inferred) | — |
| Yes / no | Should this field or feature be included?(inferred) | yes · no |
| Score | How should a style property be set along a described scale?(inferred) | — |
How it works
- User describes the UI they need in free text
- Jev answers Choice, Noul and Score questions over the component catalog
- App assembles the chosen real components and configuration
- Rendered component is shown with no generated code
Strengths
- Output is always valid, on-brand components from a known catalog
- No hallucinated code or copy on the decision path
- Bring-your-own-key flow caps the host's costs
Caveats
- Demo for a blog post; working name pending brand sign-off
- Limited to what the fixed catalog contains
- Quota counter is easily reset by clearing cookies
Getting started
`pnpm install`, copy .env.example to .env.local with TYPESAFE_API_KEY, then `pnpm dev` and open http://localhost:3000.At a glance
- Type
- App
- Status
- prototype
- Language
- TypeScript
- Runtime
- Next.js web app
- Has code
- yes
Use cases and integrations
How curated lists describe it
Turns UI descriptions into selections from existing shadcn/ui components, fields and styles.
logicrw/awesome-jev-projectsInstinct: describe a case in free text and Jev picks the UI from a fixed catalog without generating a line of code or copy.
hellogumbo/awesome-jev
Frequently asked questions
What does Instinct decide?
Which real UI components, fields and styles to use for a described case, via typed questions.
Does it generate any code?
No. It only selects and configures components from a fixed shadcn/ui catalog.
Who pays for API calls on a public deploy?
The host's key covers five generations per visitor; after that visitors supply their own key.
Related projects
React components that use Jev judgments to choose which component renders, how lists are ordered and whether affordances show.
ProjectbetaTypeScriptPrompt-first music studio where Jev makes every compositional choice, from plan to each bar pattern, rendered as editable MIDI.
ProjectbetaTypeScriptVercel Labs' generative UI framework with an experimental compose path where Jev picks which catalog components and actions to render.
ServicebetaTypeScriptCommunity shadcn-style React components and interactive lab for building TypeSafe AI interfaces.
ProjectbetaTypeScriptweb4kit starter site whose home page is planned per visitor by a System One model (Jev or local LAYA), with calibrated fallback to rules.
ProjectbetaTypeScriptEmoji autocomplete that asks Jev eight parallel questions per typing pause: emoji choice, emotion, mood, urgency, sarcasm and more.
ServiceprototypeTypeScript