VIBE_CODE.md

STEP 1. REFRAME HOW YOU CODE

Congratulations, you’ve just been promoted! You are now a Project Manager, and have been assigned your first Junior Developer- Claude AI. Actually, wait… you still have to do your Senior Developer job. You are BOTH a Senior Dev AND Project Manager, ANDDD you need to manage Claude AI’s work

This is the mindset you should adopt. So let that sink in for a minute…

1. Senior Dev (YOU)
2. Project Manager (YOU)
3. Junior Dev #1 (AI)

That's three "people" on your team now. Try giving them identities and personas to help your flow. Stand up and walk around your chair to switch roles.

STEP 2. STOP USING ONE-OFF PROMPTS

Treat your AI like a junior dev. You wouldn’t tell a junior engineer to “Make a function that does x” and then walk away. He NEEDS CONSTANT COACHING AND SUPPORT FROM YOU. Sending him small messages will never get good results.

STEP 3. CREATE AN ACTION PLAN

“But I don’t want to be constantly hand-holding my AI!”

Good, then let’s use AI to solve this problem (pretty meta, right?)

Once you get this step dialed in, you will be on your way to become the coolest “Vibes Coder” among your friends.

First, create a document called ACTION_PLAN.md

Open GitHub copilot and add this document to the context. I don’t use Cursor, the free version of copilot is all you need.

This document will be the memory and context for your “AI work session”

Your goal is to keep refining this until the document is good enough to hand to a junior dev. It should answer all the major questions. It should answer all the specific questions.

Ok, got it?

Now make it better. Keep re-reading this document and telling CoPilot to improve the sections that suck.

Your document should be a couple hundred lines. This is what you should be using to “prompt”. No more single sentences, except when backing it up with this document. “Implement phase 1”, “can we move on to phase 2 in the action plan?”

This is how to vibe code