Coding Prompts

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

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

Crimson Minimalism

A refined monochromatic editorial portrait featuring a woman standing motionless in a deep burgundy velvet gown inside a minimalist wine-red studio environment. The composition blends quiet luxury, symmetry, and cinematic restraint into a timeless high-fashion image.

Building something and need fake-but-realistic data? Describe the shape — get a clean sample dataset with believable values and the edge cases to test.

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

Get the data model right before it bites you. Describe your app — get tables, relationships, keys, and the design choices you'd regret skipping.

Teach programming concepts to beginners using clear explanations, step-by-step progression, and practical examples, advancing only when the learner is ready.

Generate concise, urgency-driven advertising headlines that push users toward a specific action, with controllable business context, audience intent, and conversion goal. Designed for booking, calling, signing up, or other high-intent responses.

Don't pick a stack you'll fight for years. Describe what you're building and your skills — get a real recommendation with trade-offs, not hype.

"Works on my machine" — famous last words. Describe your app — get a Dockerfile and setup that runs the same everywhere, explained so you understand it.

Say what you want in plain English, get clean SQL back — plus the gotchas (nulls, dupes, slow joins) you'd only find in production at 2am.

"fixed stuff" is not a commit message. Paste your diff or describe the change — get a clear commit message your future team will actually thank you for.

Got dropped into a framework you've never used? Name it and what you know — get the mental model, the core concepts, and the 20% you need to be productive today.

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

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

Describe what you want to match in plain words. Get the regex, every piece explained, and test cases — so you actually trust it before you ship it.

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.

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

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

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

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

Create clear, accurate technical documentation and API references structured for different audiences, with working examples, consistent terminology, and a balance between completeness and readability.

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

The code you'll forget in a month. Paste it — get comments that explain the WHY, not the obvious, so future-you (or your team) isn't lost.

Porting code to a new language or framework? Paste it — get the converted version plus the traps that don't translate one-to-one.

Dropped into unfamiliar code? Paste it. Get the map — what it does, how it flows, and where the bodies are buried — before you touch a thing.

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.

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

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.

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

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

Paste your code. It reviews like it's shipping to a million users tomorrow — bugs, security holes, the slow stuff — ranks every issue, and ends with ship or don't. No flattery.

Practice coding interviews the right way. Paste the problem — it nudges you toward the solution with hints, only revealing the answer once you've actually tried.

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

Find the holes before someone else does. Paste your code — it runs an OWASP-style security review and tells you what an attacker would try first.

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

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

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

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.

An algorithm or concept that won't click? Name it — get it explained with a plain analogy, a walkthrough, the complexity, and when you'd actually use it.

Your query's slow and the EXPLAIN output is gibberish. Paste it — get what's actually happening, the bottleneck, and the index or rewrite that fixes it.

Got the logic in plain steps but not the syntax? Write it out however you think — get clean, working code in your language, with the logic preserved.

You know you should. Paste the function — get the test cases that actually catch bugs, including the edge cases you'd forget at 6pm.

A config file full of settings you're scared to touch. Paste it — get what each part does, which knobs are safe to change, and which will break things.

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

Login and signup without losing a weekend to auth docs.

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

Got data in the wrong shape? Paste it and say what you need — CSV, JSON, SQL, a table — get it converted cleanly, with the structure handled right.

Cron syntax is write-once, understand-never. Describe the schedule you want (or paste the cryptic one) — get the exact expression and what it really runs.

Stop deploying by hand and praying. Tell it your stack and host — get a CI/CD setup that tests and ships automatically, with the config and the why.

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.

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

Shipped an update? Don't bury it in 'various bug fixes.' List what changed — get release notes / a changelog that's clear, scannable, and makes users care.

Designing an API and want it to not be a regret in six months? Describe what it does — get clean endpoints, naming, and the edge cases you'd forget.

It works but it's slow. Paste it — get where the real bottleneck is, the optimized version, and whether the speed-up is even worth the complexity.

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.

That boring task you do by hand every week. Describe it — get a script to automate it, with setup steps simple enough that a non-coder can run it.

The thing every dev skips. Tell it what your project does — get a README people can actually follow: what it is, how to run it, and why it exists.

Stuck between two technical approaches and second-guessing? Lay them out — get the real trade-offs for YOUR situation and a clear recommendation, not 'it depends.'

Generate a clear, implementation-ready brief that translates a website’s desired look, feel, structure, and behaviour into precise instructions a vibe coding tool can execute quickly and consistently.

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.