Explain This Query Plan

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

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.

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.

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.

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.

"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.

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.

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.

Did B actually win, or are you fooling yourself? Give it the numbers — get whether it's real, how confident, and what to do next. No false positives.

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.

Tracking everything means tracking nothing. Tell it your business — get the handful of numbers that actually matter and how to lay them out.

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

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.

"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.

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.

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.

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.

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.

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

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.

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.

Paste your numbers. Get the one chart that tells the story — and the headline a busy boss will actually remember.

Paste your numbers over time — get a straight-talk projection of where they're heading, what could throw it off, and how much to trust it.

Paste your data. Get the story behind it, the one surprising thing, and three decisions to make this week. No "it depends."