The Vibe Code Starter Pack is 33 detailed, fill-in-the-blank prompts for Cursor, Claude, Claude Code, ChatGPT, Lovable, Bolt, Replit and other AI coding tools. They're sorted by the problem you're stuck on, and each one says what it's useful for and when to use it.
AI coding tools are powerful, but vague prompts get vague results: half-built features, broken logins, mystery errors, and code the AI rewrote without asking. Most beginners don't know what details to give the AI or what to ask for.
Each prompt in this pack is a complete brief. It tells the AI its role, asks for your specifics in [BRACKETS IN CAPS], and asks for small, checkable steps and plain-English explanations.
What's inside the pack?
9 sections, 33 prompts, plus a quick-start guide and a "magic phrases" cheat sheet.
Section 1
Starting a New Project
Turn an idea into a build plan, set up the project, write a rules file, and add features without breaking things.
Idea to Build Plan
Project Setup, Step by Step
Project Brief and Rules File
Add One Feature Safely
Section 2
Building UI & Landing Pages
Describe a screen and get it built, make a landing page, turn screenshots into code, fix mobile layouts.
Build a Screen from a Description
High-Converting Landing Page
Turn a Screenshot into Code
Make My UI Responsive
Section 3
Adding Login & Auth
Add sign up and login, protect pages and user data (including Supabase Row Level Security), fix broken login.
Add Sign Up and Login
Protect Pages and User Data
Fix My Broken Login
Section 4
Databases & Saving Data
Design a database, connect it (CRUD), save data without a backend, add search and filters.
Design My Database
Connect My App to the Database
Save Data Without a Backend
Add Search, Filters, and Sorting
Section 5
Fixing Bugs & Errors
Fix error messages, wrong behavior, code the AI broke, and understand unfamiliar code.
Fix This Error
It Runs, But Does the Wrong Thing
The AI Broke My Code: Recover and Untangle
Explain This Code to Me
Section 6
Deploying & Going Live
Deploy step by step, fix failed deploys, run a launch checklist.
Deploy My App, Step by Step
Fix My Failed Deploy
Launch Readiness Checklist
Section 7
Making It Look Polished
Design glow-up, microinteractions and animations, empty/loading/error states.
Design Glow-Up
Microinteractions and Animations
Empty, Loading, and Error States
Section 8
Adding AI Features & Agents
Add AI chat, build a tool-using agent, chat with documents (RAG), generate structured content.
Add an AI Chat Feature
Build an AI Agent That Uses Tools
Chat with My Documents (Simple RAG)
Generate Content with AI (Structured Output)
Section 9
Simple Browser Games
Build a complete game, add features, make it feel juicy, make it work on phones.
Use this when you have an idea but don't know where to start or which tools to use. It's for turning a rough idea into a clear, step-by-step build plan with a recommended tech stack.
Fill in: [APP IDEA], [TARGET USER], [PROBLEM IT SOLVES], [SKILL LEVEL], [AI TOOL] (e.g. Cursor / Claude / ChatGPT), [WEB APP / MOBILE / DESKTOP / "NOT SURE"], [BUDGET FOR HOSTING AND SERVICES] (e.g. "free only" / "up to $10/month"), [TECH STACK].
I want to build an app. Act as a senior developer and a patient mentor helping me plan it.
My app idea: [APP IDEA]
Who it's for: [TARGET USER]
The main problem it solves: [PROBLEM IT SOLVES]
My coding experience: [SKILL LEVEL]
The AI tool I'm building with: [AI TOOL]
Where I want it to run: [WEB APP / MOBILE / DESKTOP / "NOT SURE"]
Budget for hosting and services: [BUDGET FOR HOSTING AND SERVICES]
Please give me:
1. A one-paragraph summary of the app in plain English.
2. The MVP (minimum viable product): the smallest version worth building, with a list of 3-6 must-have features. Put "nice to have later" features in a separate list.
3. A recommended tech stack that's beginner-friendly and free or cheap to start. Explain each choice in one sentence. If [TECH STACK] is filled in, use it unless there's a strong reason not to: [TECH STACK]
4. The main screens or pages, with one line describing each.
5. The data the app needs to store (e.g. users, posts, scores), described simply.
6. A numbered build order of small steps, where each step ends in something I can see working.
7. The 3 biggest risks or tricky parts for a beginner, and how to handle each one.
Keep the language simple and don't write any code yet. At the end, ask me up to 3 questions that would most improve the plan.
Tips to customize: Add "I want to launch in [TIMEFRAME]" to get a plan scoped to your deadline. If you're building a game, mention the genre and the feel you want.
5.1 Fix This Error
Use this when you see a red error in your terminal, browser console, or on screen. It's for diagnosing and fixing an error message, and learning what caused it.
Fill in: [SKILL LEVEL], [TECH STACK], [ACTION] (e.g. "run npm run dev" / "click the save button"), [ERROR MESSAGE], [TERMINAL / BROWSER CONSOLE / ON THE PAGE / DEPLOY LOGS], [RECENT CHANGES, OR "NOT SURE"], [PASTE CODE OR TAG FILES] (e.g. FILE NAME and line number from the error).
I'm getting an error and need help fixing it. Please explain things simply, because I'm a [SKILL LEVEL].
Tech stack: [TECH STACK]
What I was trying to do: [ACTION]
The full error message (copied exactly):
[ERROR MESSAGE]
Where it appears: [TERMINAL / BROWSER CONSOLE / ON THE PAGE / DEPLOY LOGS]
What I changed right before it started: [RECENT CHANGES, OR "NOT SURE"]
Relevant code:
[PASTE CODE OR TAG FILES]
Please:
1. Explain what this error means in plain English (1-3 sentences).
2. Tell me the most likely cause in MY code, pointing to the exact file and line.
3. Give me the fix, showing just the code that changes, with before/after.
4. If you're not sure, list the top 3 possible causes and how to check each one, instead of guessing.
5. Tell me how to confirm it's fixed.
6. Give me one tip to avoid this kind of error in the future.
Don't rewrite unrelated parts of my code.
Tips to customize: If the first fix doesn't work, reply with "That didn't work. Here's the new error/behavior: [NEW ERROR]. What else could it be?" Don't just say "still broken".
A 37-page PDF with 33 detailed, fill-in-the-blank prompts for building apps and games with AI coding tools. The prompts are organized into 9 sections by the problem they solve.
Who is it for?
Beginners and hobbyists who build software by prompting AI tools (vibe coding), and anyone into AI, agents, or making simple browser games. No coding experience is required.
Which AI tools does it work with?
Any chat or coding assistant that accepts text prompts, including Cursor, Claude, Claude Code, ChatGPT, Windsurf, and app builders like Lovable, Bolt and Replit. Several prompts also include Supabase options, such as Row Level Security for protecting user data.
How much does it cost?
$9 at the launch price (regular price $12), a one-time payment. You get the PDF to download and keep.
What format is it?
A PDF you download after purchase. Each prompt sits in a code box you can copy and paste.
How is each prompt laid out?
Every prompt has a title, a short "Use this when..." note that says what it's for, a "Fill in:" line listing what to replace, the prompt itself with [BRACKETS IN CAPS] to fill in, and tips to customize it.
Can I try it before buying?
Yes. Three full prompts are free on the sample prompts page.
Do I need to know how to code?
No. The prompts ask the AI to explain things in plain English and to work in small steps you can check.
