β All tools
Code-first
Build your front end with Cursor
Open the template in Cursor and let its agent reskin it against the whole codebase.
Best for: Developers who live in an editor and want AI edits with full-repo context.
Open Cursor βThe prompt
Copy this, fill in the [bracketed] parts, and paste it into Cursor.
@codebase This is the BringTheFront template β a Next.js 15 App Router front end that talks to the Orgalized backend ONLY through lib/api (a server-side BFF proxy) with session-cookie auth in middleware.ts. Do not modify lib/api or middleware, and never add a browser-side call to the backend. Reskin it for my business: - Business: [YOUR BUSINESS] β [what you do]. Brand color [color]. Mobile-first. Tasks: (1) update site.config.ts; (2) rewrite copy in lib/content/* for my business; (3) restyle marketing pages + dashboard shell using only semantic tokens (content-*/surface-*/action-*), no hardcoded colors; (4) keep all data flowing through lib/api. Then run pnpm verify in the terminal and fix any failures.
How to do it
Fork + open in Cursor
Fork BringTheFront (Setup Guide) and open the folder in Cursor.
Run the agent
Open Composer/agent mode, paste the prompt (the @codebase gives it full context), and let it edit across files.
Accept selectively
Review each change. Accept the styling and copy edits; reject anything that touches lib/api or middleware.
Verify + deploy
Run pnpm verify in Cursor's terminal, fix flags, push, deploy on Vercel.
Watch out for
- Use @codebase (or add lib/api + middleware to context and tell it "read-only") so Cursor understands the boundary instead of guessing.
- Cursor sometimes "helpfully" adds a fetch to make a page dynamic. That is the one thing to reject β data comes through lib/api.
Ready to bring your front?
Create your backend first, then use Cursor to build the front that connects to it.