Pick interface blocks from your component catalogue
Describe a screen or product and let Jev choose which components and layouts from your own catalogue fit, without generating free-form code.
The use case
Product teams and agencies want to draft landing pages or app screens quickly but do not want a model writing arbitrary code. In these builds the components come from your own catalogue, and Jev only chooses: which hero layout, which pricing block, which form fits the description. The framework renders the chosen spec. A designer reviews the result and writes or edits the copy, since Jev does not write text, and engineers check accessibility before anything ships. Keeping the catalogue small and well described matters more than the prompt.
Example workflow
- Catalogue components with short descriptions in json-render or shadcn/ui
- Collect a short description of the page or screen
- Ask Jev Choice questions for each section
- Render the chosen spec
- A designer edits copy and layout before shipping
Tools
- Jev (TypeSafe AI)
- json-render
- shadcn/ui
- Next.js
Risks and guardrails
- A thin catalogue makes every page look alike
- Picked layouts may not suit the content
- Accessibility depends on the components themselves
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- json-render by Vercel Labs on Made with Jev: madewithjev.com/builds/json-render
- json-render: original post or repo by Vercel Labs: github.com/vercel-labs/json-render
- Jev Pages by sagapranav on Made with Jev: madewithjev.com/builds/jev-pages
- Jev Pages: original post or repo by sagapranav: github.com/sagapranav/jev-pages
- jev-design-test by bhaiG-de on Made with Jev: madewithjev.com/builds/jev-design-test
- jev-design-test: original post or repo by bhaiG-de: github.com/bhaiG-de/jev-design-test