Write My README

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.

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.

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.

Quiet Passage Portrait

Generate a cinematic environmental portrait of a solitary figure standing within a tall, moss-covered ravine, using soft natural light, deep greens, and strong vertical framing to convey calm, scale, and quiet reverence.

Textbooks teach you to sound stiff. Give it a phrase — get how people actually say it, the slang, and the thing you should never say.

Turn rows of data into a dashboard that shows what matters at a glance.