Builder Prompts Library

The backbone of most apps: a list, a form, and the ability to edit and delete, all scoped to the logged-in user. Works in Lovable and v0 for a quick version, or Cursor and Claude Code for a real database-backed one. Ownership scoping enforced on the server is the piece beginners miss, and it is what stops one user from editing another user's data.

Turns your app into a real SaaS with recurring revenue. Works in Cursor and Claude Code, and the plan-first structure also works well pasted into Lovable. The key instruction is that plan state only ever changes from a signature-verified webhook, which is the mistake most AI-generated Stripe code makes.

Makes any list of records actually usable once it grows past a screenful. Best in Cursor or Claude Code on your real list page. Two things set this apart from a naive version: syncing state to the URL so views are shareable and refresh-safe, and filtering in the database rather than loading every row into the browser.

Adds a proper dark mode instead of a toggle that flickers or forgets your choice. Works in Cursor, Claude Code, and v0. The two details that matter most are killing the flash of unstyled theme on load and centralizing colors as tokens, so define the palette once and every component follows.

Bridges the gap between a fuzzy idea and something an AI builder can actually execute. Run it in any chat tool, then paste the finished spec into Lovable, v0, Cursor, or Claude Code as your project brief. The forced Later list and out-of-scope section are what keep your first version small enough to actually ship.

Get a real safety net so AI-driven changes stop silently breaking things that used to work. Best in Cursor or Claude Code that can run the suite and confirm it passes. The read-and-explain-first step catches cases where the code is wrong, so you do not lock in a bug by writing a test that asserts the broken behavior.

This prompt was created by Income Stream Surfers on Youtube https://www.youtube.com/@Incomestreamsurfers

- Run: npx create-next-app@14.2.3 my-next-app
// the reason we are using an old next.js version is because Claude was likely trained on its documentation. You may choose to run @latest instead.
- Replace all test in the XML tags with text unique to your website
- Keep all XML tags (like <tag>content</tag>) exactly as they are

I tried this for a friends freight company and it worked quite well, I'd give it a 79/100. it cost around 6USD and i used 3.7 Sonnet with Cline. I still needed to prompt it to fix a few errors and set up the contact forms in via supabase.

This is a similar prompt I used with Roo and V0 to create this website. V0 gave me good ideas for styling on the frontend, whereas Roo with Gemini 2.5 Pro Exp implemented the core functionality.

I had to install sanity studio as per the instructions on their website first. I then provided the LLM with the location of Sanity Studio on my website and instructed it when to edit schemas.

Instructions:

Replace all text in {{DOUBLE_BRACES}} with your specific information
Keep all XML tags (like <tag>content</tag>) exactly as they are
Paste the prompt into chosen Ai Coding Agent.

Wire up any external API without leaking your key or writing brittle fetch calls all over the app. Best in Cursor or Claude Code, which can pull live docs. The check-the-docs-first step avoids code written against an outdated API version, and the server-side wrapper keeps your secret key out of the browser and your error handling in one place.

Validate demand before you build the whole product by collecting real emails from day one. Works great in Lovable and v0 for the page, and in Cursor or Claude Code to wire up storage like Supabase. Keeping it to one call to action and blocking duplicate signups are the details that make a waitlist actually useful.

Use this once a feature works on desktop but looks broken on a phone or fails accessibility basics. Best in Cursor or Claude Code that can see and edit your components. It audits before it edits, so you get a punch list first, and the explicit 44px tap target and WCAG AA contrast rules catch the issues generic requests miss.

For when a file has grown into a mess but you are scared to touch it. Best in Cursor or Claude Code. The plan-and-approve gate plus keeping the public interface identical means you get cleaner code without a surprise rewrite, and pairs well with writing tests first so you can prove nothing changed.

Gives you an internal tool to view metrics and manage records without touching the database directly. Best in Cursor or Claude Code where it can read your real schema. Tell it your actual table names so the stat cards and tables use real data, and note that the server-side admin check on every action is what keeps it secure.

Use this when you need real login and signup instead of a fake demo gate. Works in Cursor, Claude Code, Lovable, and v0. Swap in your framework and auth provider, and the two-step plan (packages plus env vars, then file list) stops the AI from silently assuming a setup you do not have.

Get a solid data model before you write a single query, which is far cheaper than fixing it after launch. Works in any AI tool but shines in Claude Code and Cursor where the SQL can be applied directly. The request for a relationship diagram and gotcha list catches design mistakes early, and the Supabase RLS ask saves a common security oversight.

Stops the AI from thrashing and rewriting half your file on a bug it does not understand. Paste the full error and stack trace, then it isolates the root cause before touching code. Ideal in Cursor and Claude Code, and the one-change-at-a-time rule keeps a small bug from turning into three new ones.

Covers the SEO basics most vibe-coded sites skip: per-page titles and descriptions, social preview cards, a sitemap, and valid JSON-LD schema. Best in Cursor or Claude Code on a Next.js or similar project. The instruction to build one reusable metadata helper keeps you from hand-writing tags on every page, and the no-fake-data rule keeps your structured data legit.

A starter prompt for spinning up a landing page fast. Replace [PRODUCT] with your product and iterate on the sections.

Works well in Lovable, v0, and Cursor.