> Source URL: /resources/prompting-cheat-sheet.guide # Prompting Cheat Sheet How to talk to AI tools so they actually help you learn and build. This covers Cursor's agent, ChatGPT, vibe coding platforms (Lovable, Bolt, v0, Replit), and any other AI tool you use in this course. The same ideas apply everywhere. --- ## The golden rule **You're the driver, AI is the navigator.** The AI can suggest directions, but you decide where to go. If you don't understand what it did, stop and ask before moving on. Code you can't explain is code you can't fix. --- ## Learning mode Use these when you want to understand something, not just get an answer. ``` Explain this like I'm a beginner. No jargon. ``` ``` What does this code do, line by line? ``` ``` Why did you write it that way? What are the alternatives? ``` ``` Don't give me the answer yet. Give me a hint and let me try first. ``` ``` Quiz me on what I just built. Ask 3 questions. ``` ``` I don't understand [concept]. Explain it using [something I'm interested in] as an example. ``` The last one works especially well if you tell the AI about your interests. "Explain variables using a music playlist as an example" is a lot more memorable than a generic textbook explanation. --- ## Prototyping mode Use these when you're building a rough first version with a vibe coding tool (Lovable, Bolt, v0, Replit). ``` You are my MVP build coach. I am a high school student and a beginner programmer. Use plain language. Define technical words in one sentence. Project idea: [paste your elevator pitch] Target user: [who this is for] Build me the smallest working MVP with only 3-5 must-have features. Give: 1) feature list, 2) build order, 3) publish steps, 4) test checklist. Do not add extra features yet. ``` ``` What's broken or confusing in what you just built? Walk me through it. ``` ``` I want to change [specific thing]. What's the simplest way? ``` ``` What should I test before I publish this? ``` The goal of prototyping is speed, not perfection. Get something working, show it to someone, figure out what's missing. --- ## Building mode Use these when you're developing for real in Cursor. **Before the agent touches anything:** ``` Plan first. Tell me what you're going to do before you edit any files. ``` ``` Don't edit files until I say "yes." ``` **Keep changes small:** ``` Change one small thing, then stop so I can check it. ``` ``` Only change 5-10 lines (or one function), then wait. ``` **After a change:** ``` What did you change, and why? ``` ``` Show me the exact lines you changed (before and after). ``` **When you're stuck:** ``` Here's what I'm trying to do: [describe it]. Here's what's happening instead: [describe it]. Help me figure out why. ``` ``` I got this error: [paste the error]. Explain what it means and give me one thing to try. ``` **When things get complicated:** ``` This is getting confusing. Can we start over on just this one part? ``` ``` I don't understand what you just did. Explain it before we keep going. ``` --- ## Git and GitHub mode Use these when you need help with version control. ``` Help me commit and push my changes to GitHub. Walk me through it step by step. ``` ``` I made changes but nothing shows up in Source Control. What did I do wrong? ``` ``` How do I pull the latest version of my project from GitHub? ``` ``` I'm getting a merge conflict. Help me understand what happened and how to fix it. ``` ``` I think I broke something. How do I undo my last change? ``` --- ## Rules of thumb 1. **Be specific.** "This button doesn't work" is harder to help with than "When I click the Submit button, nothing happens and I expected it to save the form data." 2. **Ask for a plan before code.** It's much easier to course-correct a plan than to undo a bunch of code changes you don't understand. 3. **Work in small steps.** One feature at a time. One change at a time. Test after every change. 4. **Run your code constantly.** Don't write 50 lines and then test. Write 5 lines, save, run, check. 5. **If something breaks, describe what you expected.** "I expected the page to show a list of songs, but it shows a blank page" gives the AI everything it needs to help. 6. **It's okay to say "I don't understand."** That's the most useful prompt there is. The AI will try a different explanation. 7. **You can always say "undo that" or "let's try a different approach."** You're in charge. --- ## Prompts that keep you learning (not just copy-pasting) If you find yourself just accepting everything the AI suggests without reading it, try these: ``` Before you write any code, teach me the concept I need to understand. ``` ``` After each step, ask me to predict what will happen before I run it. ``` ``` Give me the structure but leave the key parts blank for me to fill in. ``` ``` I want to write this myself. Just tell me what to Google or look up. ``` The point of this class is for you to learn, not for the AI to build your project while you watch. Use AI to go faster, not to skip the work. --- ## Backlinks The following sources link to this document: - [Prompting Cheat Sheet](/resources/index.resources.llm.md) - [Prompting Cheat Sheet](/users/annie-h/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/charlie-m/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/emily-kate-s/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/josiah-c/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/john-p/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/jake-f/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/elizabeth-b/week-5.path.llm.md) - [Prompting Cheat Sheet](/users/annie-h/week-4.path.llm.md) - [Prompting Cheat Sheet](/users/charlie-m/week-4.path.llm.md) - [Prompting Cheat Sheet](/users/elizabeth-b/week-4.path.llm.md) - [Prompting Cheat Sheet](/users/josiah-c/week-4.path.llm.md) - [Prompting Cheat Sheet](/users/emily-kate-s/week-4.path.llm.md) - [Prompting Cheat Sheet](/users/john-p/week-4.path.llm.md) - [Prompting Cheat Sheet](/users/jake-f/week-4.path.llm.md)