Refactor Without Breaking Anything

The prompt that makes Cursor add a feature cleanly instead of rewriting half your app.

Get your data model right before you build on top of it.

The first prompt to paste into Lovable or v0 so you get something real, not a toy.

Most AI-built apps turn into spaghetti. Get the structure right up front.

Stuck on an error you don't understand? This gets you unstuck without the lecture.

The audit nobody does after vibecoding. Find what'll break or get exploited before users do.

Inherited code you didn't write? Get the map before you touch anything.

Login and signup without losing a weekend to auth docs.

Before you ship AI-generated code, have it checked by something that won't sugarcoat it.

A landing page that converts, generated clean and ready to tweak.

Before you build anything with AI, get the spec right. This writes the PRD for you.

The scariest bug: one user seeing another's data. Check your auth before someone else does.

It works with you clicking around. Will it survive 1,000 real users and a bad day?

Good logs save you at 2am. Bad ones leak data and tell you nothing. Get this right.

Protect user data properly — before a leak makes the decision for you.

The #1 vibecoding mistake: API keys sitting in your code or git history. Hunt them down.

That app you built pulls in hundreds of packages you've never read. Find the risky ones.

Before you let real users in: the checklist that catches what vibecoding skips.

The standard checklist real engineers use. Run your app through it in plain English.

Paste the function you're embarrassed by. Get it cleaner and readable with the exact same behavior — plus a note on what was wrong so you stop doing it.

See a UI you like? Describe it and rebuild it instead of starting from a blank page.

Naming things is half of programming and you're stuck. Paste the code or describe it — get clear, consistent names that make the code read itself.

A mock interviewer that runs you through a real system design round, interrupts like the real thing, and scores you at the end. Brutal on purpose.

Building against an API that isn't ready? Describe the endpoint — get realistic mock JSON (success and error cases) so you can build the front end now.