Quick answer
How to verify an app built with Cursor
Cursor makes you faster in the editor, but the editor is exactly where launch problems hide: everything compiles, the diff looks right, and nobody has loaded the app the way a user will.
PromptUI picks up at the repository: import, render for real, verify what painted, fix with prompts, deploy — with a proof page recording what passed.
- 1
Push your project to GitHub
Whatever tool built it — Claude Code, Codex, Lovable, Bolt, Replit — get the code into a GitHub repository. Most AI builders have a GitHub sync or export; a plain git push works too.
- 2
Import it into PromptUI
Sign in, choose “Import my code”, connect GitHub, and pick the repository. PromptUI loads the project into a builder session with a live preview.
- 3
Let the verification checks run
PromptUI renders the app for real and runs its checks against the rendered result — not just the source. Anything flagged comes back as findings you can review.
- 4
Fix with prompts, then deploy
Describe fixes in plain language and review each change in the preview. When it looks right, deploy to a live URL from the same screen.
- 5
Launch it
After deploying, the launch page assembles posts, images, and video drafts about your app — every draft waits for your approval before anything publishes.
Bring your app to PromptUI
Import the repository, watch the verification run on the real rendered app, and go from repo to launched.
Import from GitHub →Already signed in? Open the import dialog
Common questions
- I already have tests — why this too?
- Unit tests exercise functions; this verifies the rendered app a user meets. For launch confidence you want both, and the rendered check is the one most codebases skip.
- Does PromptUI change my repository?
- Import only reads. Changes you make in PromptUI can sync back through GitHub when you choose.