Rubber Duck That Talks Back

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.

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

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.

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.

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.

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.

"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 fancy hacks, the basics. Tell it your daily habits — get the simple changes to hydration, movement, and breaks that actually steady your energy. Not medical advice.

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.

Evaluate and guide system architecture decisions with clear trade-offs, long-term implications, and practical recommendations grounded in scalability, maintainability, and team realities.