3 Prompts That
Deploy Code.

I'm a non-developer building [describe your project in 1-2 sentences]. Before you write any code, I need you to follow these rules for our entire session: 1. EXPLAIN before you code. Tell me in plain English what you're about to do and why. Use analogies if helpful. 2. GO SLOW. Only do one thing at a time. After each step, wait for me to confirm it worked before moving on. 3. TELL ME EXACTLY WHERE. If I need to put code somewhere, tell me the exact file name and where in the file (top, bottom, after a specific line). 4. WHEN SOMETHING BREAKS. Don't assume — ask me to share the exact error message. Then explain what it means before trying to fix it. 5. NO JARGON. If you must use a technical term, define it immediately in parentheses. 6. CHECK IN. After every major step, ask me: "Does this look right?" and "Should we move on to [next step]?" Do you understand these rules? If yes, tell me what we're building and ask me what you'd like to know before we start.

Before we write any code, I want you to help me define exactly what we're building. Act as a product manager interviewing me about my project. Ask me the following questions ONE AT A TIME, waiting for my answer before asking the next: 1. What problem does this solve? Who has this problem? 2. Who are the users? What will they do in the app? 3. What does success look like? What's the simplest version that would be useful? 4. What pages or screens does the app need? 5. What information does the app need to store? 6. Are there any actions that need to happen automatically (emails, reminders, etc.)? 7. What does the app NOT need to do? (setting scope) 8. Is there a website or app that does something similar I could show you? After I answer all 8 questions, summarize what we're building in a "Project Specification" document with these sections: - What it is (1 paragraph) - Who it's for (1 sentence) - Core features (bulleted list) - Pages/screens (bulleted list) - What we're NOT building (bulleted list) Then ask me: "Does this match what you have in mind? What would you change?" Start with question 1 now.

I want to build [describe the specific feature or screen you're working on]. Before writing any code: 1. Explain your plan in plain English — what you'll build and in what order 2. Tell me how many steps this will take 3. Ask if the plan makes sense before starting Then build it ONE STEP AT A TIME using this pattern for each step: STEP [number] of [total]: What I'm doing: [plain English explanation] Why: [why this step is needed] The code: [only the code for this step] Where it goes: [exact file name and location] How to test it: [one specific thing I can do to verify it worked] After each step, STOP and wait for me to either: - Say "it worked" (then move to next step) - Share an error message (then help me fix it before proceeding) Do not move to the next step until I confirm the current one works. Ready? Start with your plan.