Write Release Notes People Read

The tiny words in your app or site — buttons, errors, empty states — quietly make or break the experience. Describe the spot — get microcopy that's clear, human, on-brand.

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.

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.

Someone you care about lost someone, and you're afraid of saying the wrong thing. Tell it the situation — get words that are warm, real, and never hollow.

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.

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.

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.

Your content's fine — your first line is killing it. Paste the post and get 10 opening hooks that actually stop the scroll.

Your characters all sound the same and a bit robotic. Describe the scene — get dialogue that sounds like real, distinct people with something at stake.

Paste anything that reads like a robot wrote it. Get it back sounding like a human with an opinion — short sentences, no 'leverage,' no fluff.

Been ages, or they're going through something, and you don't know what to say? Tell it the situation — get a message that's warm and real, not awkward.

Nobody reads boilerplate. Give it the role and your background — get a cover letter that sounds like you actually want this job, not a template with the company name swapped in.

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

Your profile sounds like everyone else's. Tell it about you — get a bio that's specific, a little funny, and actually sounds like a real person worth meeting.

Your bio has one job and it's blowing it. Tell it who you are and who you want — get bios that say what you do and make people hit follow.

Time off your resume you're dreading explaining? Tell it the situation — get honest, confident language for the resume, cover letter, and the interview question.

Before you write 1,500 rambling words. Give it the topic — get a tight outline with an angle, the points in order, and what each section actually delivers.

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.

Wronged by a company and getting nowhere? Tell it what happened — get a complaint that's firm, factual, and hard to brush off, with exactly what you want.

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.

The About page is the hardest thing to write about yourself. Tell it your story — get one that's warm, credible, and doesn't read like a third-person robot.

Paste your product details. Get a description that makes someone want it — benefits over specs, no keyword soup, sounds like a brand not a spec sheet.