Debug This Error (Paste & Fix)

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.

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

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

Login and signup without losing a weekend to auth docs.

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

Clean up messy AI-generated code safely — one small change at a time.

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

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.

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

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

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

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

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

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

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

Paste the stack trace that means nothing to you. Get what actually broke, why, and the most likely fix — in plain English.

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

Stuck? Explain the problem to it out loud. It asks the questions that make you find your own bug — and only steps in when you're truly stuck.

Stop guessing. Give it the symptom and the code — it ranks the likely causes and tells you the one thing to test next. Diagnoses before it touches a fix.

Test's red and you don't know if it's the code or the test. Paste both — get whether the test is wrong, the code is wrong, and exactly what to fix.