Most AI productivity advice stays abstract. "Use AI to write better code." Great. How? Here are 8 specific, copy-paste-ready patterns I actually used this past week — each one self-contained, each one with a real return on time.
1. Pre-meeting context dumps
Before any technical sync, I paste the relevant PR diff or ticket description and ask: "Summarize the open questions and likely points of contention in this change." Takes 30 seconds. Means I'm never the person staring blankly when someone asks about edge cases.
2. Rubber-duck debugging with a forcing function
Instead of describing the bug, I describe what I expect to happen and what's actually happening — then ask the model to list every assumption I'm making that could be wrong. This forces me to be precise, which often surfaces the bug before the response even arrives.
3. Generating the test matrix I'd skip writing myself
After writing a function, I paste it and ask:
Given this function, list every test case worth covering — including edge cases,
boundary conditions, and failure modes. Format as a numbered list.
No code yet, just the cases.
I probably write 2–3 tests. This surfaces 7–10. I pick the ones that matter.
4. Turning code review comments into patterns
When I leave a review comment I've left more than twice, I paste it into the model and ask: "Turn this into a reusable code review heuristic I can document for my team." Slowly building a team-specific style guide without scheduling a meeting about it.
5. Translating dense documentation into working examples
When I hit library docs that are technically correct but practically useless, I paste the relevant section and ask:
I'm using [library] to do [specific thing]. Here's the relevant docs section:
[paste]
Give me a minimal, working code example that does exactly [X]. Use real values,
not placeholders. Point out any gotchas the docs don't mention.
This works especially well for authentication flows, SDK quirks, and anything involving async behavior.
6. First-draft commit messages from diffs
I paste the staged diff and ask for a conventional-commit-format message with a one-line summary and a 3-bullet body. I edit it, but starting from something beats starting from a blinking cursor every time.
7. Pressure-testing architecture decisions before you write them up
Before I write a design doc section, I describe the approach and ask: "What are the strongest objections a skeptical senior engineer would raise against this?" The model is good at steelmanning. I'd rather get the objections here than in the doc review.
This pattern is one of the ones I've packaged into The AI Leverage Playbook: 50 Prompts & Workflows for Engineers — but the version below is enough to get value on its own.
Here's the full prompt I use:
I'm proposing the following architecture decision: [describe it in 2-4 sentences].
Play the role of a skeptical senior engineer who cares about operational complexity,
maintainability, and failure modes. List your top 5 objections, ranked by severity.
Be specific, not generic.
The output gives me a sharper doc and surfaces assumptions worth defending explicitly.
8. End-of-day knowledge capture
The one that took me longest to build into a habit: before I close my editor, I spend 3 minutes asking the model to help me summarize what I learned or decided. I paste any relevant context and use:
"Based on this work, what are 2–3 things worth writing down so I don't have to re-derive them next time?"
These go into a running notes file. Six months from now, that file is worth more than any tutorial.
The common thread
None of these replace judgment. They all reduce the cost of applying judgment — less friction between "I should do this thing" and actually doing it. That's the lever worth pulling.
The patterns that stick aren't the flashy ones. They're the ones that fit inside work you're already doing, take under a minute to set up, and make the next hour measurably less annoying.
I break down one workflow like this every week in The AI Leverage Weekly — practical, no fluff, free. Subscribe: https://theaileverageweekly.beehiiv.com/subscribe?utm_source=devto&utm_medium=article&utm_campaign=long_w4
Top comments (0)