Academyacademy / vibe-102 / prompt-rescue-sheet
Prompt Rescue Sheet
What this is
Prompt Rescue Sheet is the emergency page for Vibe 102.
Use it when something breaks and the learner needs one small fix, not a full rebuild.
Why it matters
Beginners often lose time by saying "it does not work" or asking AI to rebuild everything.
A rescue prompt gives the AI evidence, a clear expected result, and a strict limit.
What to do
Use this base rescue prompt whenever the app gets stuck:
Copy prompt
CONTEXT:
I am building a Vibe 102 React + Vite + Tailwind mini app.
WHAT HAPPENED:
[short description]
EXPECTED:
[what should happen]
ACTUAL:
[what happened]
EVIDENCE:
[paste the exact error, screenshot text, or current code summary]
TASK:
Fix only this problem.
Rules:
- explain it simply
- do not add new features
- do not rewrite the whole app
- give me one test to confirm the fixFor setup stuck:
Copy prompt
CONTEXT:
I am setting up my Vibe 102 React + Vite + Tailwind mini app.
COMMAND I RAN:
[paste command]
ERROR:
[paste exact error]
TASK:
Explain the problem in simple words and give me the smallest next fix.
Rules:
- fix setup only
- do not build any app features yet
- do not add extra libraries unless required for setup
- give one command or action at a timeFor localhost not opening:
Copy prompt
CONTEXT:
I am setting up my Vibe 102 Vite app.
COMMAND I RAN:
[paste command]
TERMINAL OUTPUT:
[paste output]
BROWSER RESULT:
[what the browser shows]
TASK:
Diagnose why localhost is not opening and give me the smallest setup fix.
Rules:
- do not build app features yet
- check folder, install, terminal, and port issues first
- give the smallest next fix
- tell me what I should see when it worksFor a blank page:
Copy prompt
CONTEXT:
My Vibe 102 app should show the layout in the browser.
EXPECTED:
I should see the app layout.
ACTUAL:
The page is blank.
EVIDENCE:
[paste browser console error or terminal error]
TASK:
Find the smallest fix.
Rules:
- explain which file changed
- do not add new features
- do not redesign the UI
- give one browser check after the fixFor a button that does nothing:
Copy prompt
CONTEXT:
I am building one Vibe 102 mini app behavior.
EXPECTED:
[what the button should do]
ACTUAL:
[what happens now]
CURRENT CODE:
[paste the relevant component or describe the file]
TASK:
Fix only this button behavior.
Rules:
- explain the state change simply
- do not add unrelated features
- do not rewrite the whole component unless required
- give one click test after the fixFor localStorage not saving:
Copy prompt
CONTEXT:
My Vibe 102 mini app already has add, update, and delete behavior.
EXPECTED:
Items should stay after refresh.
ACTUAL:
Items disappear.
CURRENT CODE:
[paste the localStorage/useEffect part]
TASK:
Fix only the save/load logic.
Rules:
- explain JSON.stringify and JSON.parse simply
- do not add a backend or database
- do not change the app idea
- give one refresh test after the fixFor AI overbuilding:
Copy prompt
CONTEXT:
My Vibe 102 mini app became too complicated.
TARGET SCOPE:
- one list of items
- add item
- update or mark item
- delete item
- save with localStorage
TASK:
Bring it back to the Vibe 102 scope.
Rules:
- remove or ignore extra features for now
- do not add new features
- explain the simplest next step
- tell me which parts to keep, cut, and maybe do laterFor code explanation:
Copy prompt
CONTEXT:
I am learning from my Vibe 102 mini app.
TASK:
Explain this app like I am a beginner.
OUTPUT:
1. where the data lives
2. what changes when I click the button
3. which file I should read first
4. one thing I should test next
Rules:
- do not add new code
- use simple words
- use one analogy if helpful
- keep coding terms in EnglishFor demo practice:
Copy prompt
CONTEXT:
I am preparing a short Vibe 102 class demo.
APP:
[app name]
GOAL:
[goal]
WORKING BEHAVIOR:
[add/update/delete/save behavior]
TASK:
Write a simple 30-second demo script for class.
Rules:
- keep it honest
- mention what I tested
- do not exaggerate the app
- use beginner-friendly languageCommon mistakes
- Asking AI to fix five problems at once.
- Pasting only "error" instead of the real message.
- Letting AI rewrite the project when one button is broken.
- Debugging localStorage before add/update/delete works.
Vibe 102 / Current checkpoint
Prompt Rescue
Ready to stamp - Saved in this browser only.
0 of 15 checkpoints complete
0 of 15 checkpoints complete.