The three steps
- Agents. Choose one or more of the 11 supported agents. Nothing is set up for an agent you don't choose.
- Tools. Choose from the catalog's tools, or start from a template and change it. You need at least one agent before this step, and one tool before the next.
- Review and download. See exactly what will be set up for each agent, then copy it or download it.
Templates
A template is a ready-made set of tools for a common way of working. It only fills in your choices, so you can add or remove tools afterwards.
| Template | For | Tools |
|---|---|---|
| Paper to code | Design on the Paper canvas, build with shadcn/ui components and check the result in a real browser. | Paper, shadcn/ui, Playwright MCP |
| Figma to code | Read frames and variables from Figma, turn them into shadcn/ui components and compare the build with the design. | Figma (remote MCP), shadcn/ui, Playwright MCP |
| Penpot to code | Design in open-source Penpot, build with shadcn/ui, document the result in Storybook and check it in a real browser. | Penpot, shadcn/ui, Storybook, Playwright MCP |
| Design-system team | Keep Figma, the Storybook docs and shadcn/ui components in step, and ship each change as a GitHub pull request. | Figma (remote MCP), Storybook, shadcn/ui, GitHub MCP |
| Motion-rich site | Smooth scrolling with Lenis, timelines with GSAP and UI motion with Motion on a shadcn/ui base, with screenshots to review each pass. | shadcn/ui, Playwright MCP, Lenis, GSAP, Motion |
| Review and QA | Open the built UI, take screenshots at each breakpoint and run the shadcn/ui audit checklist. | Playwright MCP, shadcn/ui |
What you get
For each agent, the review step lists what to do, in the form that agent understands:
- Commands to run in a terminal, one per tool.
- Config files with their path. When several tools write to the same file, their entries are merged into one file.
- Install links, for agents that can add a server with one click.
- Notes for anything a tool needs first, such as an account or a running app.
- Install commands for libraries, which aren't servers and need no connection.
You can copy any command or file, download a single file, or download everything as exonui-setup.zip.
Replace placeholders locally
Secrets never appear in the output. Where an agent can read a value from an environment variable, the setup refers to the variable's name; where it can't, you'll see a YOUR_… placeholder. Put real values in your own environment and never commit them.
When a tool isn't available for an agent
Some vendors only let certain apps connect. Figma's remote server is one example: it accepts only clients on its list. For an agent a tool can't be used with, the wizard says so and suggests alternatives, rather than writing a configuration that wouldn't work.
Share a setup
Your choices live in the address, so the back button moves between steps and a link restores a setup exactly. On the review step, Copy a link to this setup copies it. The format is:
/setup?step=review&agents=claude-code,cursor&tools=paper,shadcnagents and tools are comma-separated ids from the catalog. Ids the wizard doesn't know are ignored.