Question 1

What AI agents does UIPrompt work with?

Accepted Answer

UIPrompt exports a structured JSON context that works with any AI coding agent — Claude Code, Cursor, GitHub Copilot, Gemini CLI, Windsurf, and Codex. If it accepts a prompt or context file, UIPrompt will make it better.

Question 2

Do I need design experience to use UIPrompt?

Accepted Answer

No. UIPrompt is built for developers, not designers. You describe what you want in plain language, pick a tech stack, and enable design rules. The canvas handles the structure, the AI handles the visuals.

Question 3

What's the difference between UIPrompt and Figma or v0?

Accepted Answer

Figma produces design files. v0 produces a single component from a single prompt. UIPrompt produces a structured AI context that describes your entire UI — every component, its purpose, the tech stack, and design constraints — so your AI agent can build a full, consistent interface instead of one isolated piece.

Question 4

Why does per-component prompting matter?

Accepted Answer

When you send one prompt for an entire page, the AI has to guess at structure, hierarchy, and intent. UIPrompt gives each component its own targeted prompt — the hero block gets one instruction, the CTA gets another, the nav gets another. The agent receives a blueprint, not a paragraph.

Question 5

Can I use UIPrompt with any tech stack?

Accepted Answer

Yes. You configure your framework (Next.js, React, Vue, SvelteKit…), styling (Tailwind CSS, CSS Modules…), and component library (shadcn/ui, MUI, Radix…). With Strict Stack mode on, the AI will only use what you listed — no hallucinated imports.

Question 6

How do I export to an AI agent?

Accepted Answer

Three ways. Copy the full brief from Agent context and paste it into your agent. Ship it to your repo with Publish → Pull request for your agent: UIPrompt opens a pull request (or commits straight to main) that adds .uiprompt/brief.md and points AGENTS.md at it, so Claude Code, Cursor or Codex picks it up without copy and paste. Or connect UIPrompt to your agent as a connector, and it pulls the brief itself with the get_agent_context tool.

Question 7

Can I use UIPrompt inside Claude, ChatGPT or Codex?

Accepted Answer

Yes. Add https://uiprompt.app/api/mcp as a custom connector: in Claude under Settings → Connectors, in ChatGPT with developer mode turned on, or in Codex with codex mcp add (Claude Code and Cursor work too). Sign in once with your UIPrompt account, and your agent can plan pages on your canvas and pull the finished brief to build from. Connectors are included in every plan, and you can disconnect any app from your projects page.

Question 8

Does UIPrompt work with my existing GitHub repo?

Accepted Answer

Yes. Create a project from any repo you give the UIPrompt GitHub app access to, private ones included. UIPrompt detects your pages, stack and design tokens, and every route becomes a page on the canvas. Page content is not imported: each page starts empty, ready for you to plan.

Question 9

Will UIPrompt change my code?

Accepted Answer

No. It only adds the .uiprompt/ folder and a small marked block in AGENTS.md, always through a pull request you can review (or a merge you choose). The public skeleton for GitHub Pages lives on its own gh-pages branch. Your application code is never touched.

Question 10

How do I know what my agent has built?

Accepted Answer

For imported projects, every page shows Built or Planned based on the routes in your repo, and routes added later can become pages in one click. When you publish the skeleton to GitHub Pages, the deployment status shows live in the editor.

Stop prompting blind.

One export. Your entire project context.

From repo to shipped UI.

Hallucination-proof
by design.

Works inside your agent.

Context+Prompt=Power

Works with your stack.

Start from a template.

Landing pages & conversion

Dashboards & product screens

Shopping & checkout flows

Why prompts need context.

Frequently asked
questions.