"I am on my first real vibe-coding session.
Project: [describe project]
Current goal: [describe one small feature]
Before changing code:
1. explain the safest approach in plain English
2. list the files you expect to change
3. tell me if this request is still too big
Then implement only that one small feature.
Afterward:
4. tell me exactly what changed
5. tell me how to test it in under two minutes
6. stop so I can review before the next step
Do not add auth, deployment, payments, or unrelated cleanup."Your First Agent Session
How to run a first real AI-assisted build session without letting it spiral into a mystery code dump.
Prompt FAQ
Questions to answer before you paste it
When should I use the Your First Agent Session prompt?
How to run a first real AI-assisted build session without letting it spiral into a mystery code dump. Use it when you need a safer starting point than a blank prompt and you want the agent to stay inside explicit constraints.
Should I paste this prompt exactly as written?
No. Treat it as a safe starter. Replace the task, files, constraints, and verification details with your actual context before you run it.
What should I do after the agent answers?
Read the diff, run the checks, and stop after one reviewable step. If you need deeper context, open the lesson that explains the reasoning behind the prompt.
Related prompts worth copying next
Choose a Tiny First Win
How to pick a first project that teaches the workflow without dragging you into complex product and engineering problems.
Open prompt pageDon't Lose Your Work — Folders, Git, and Checkpoints
The minimum safe setup for total beginners: a real project folder, a Git repo, a remote backup, and repeatable checkpoints.
Open prompt pageWhat You're Actually Doing When You Build With AI
A plain-English explanation of the job: AI writes fast, you still choose scope, inspect output, and own the result.
Open prompt page