Aider Prompts for Developers
Developers mostly need help reading unfamiliar code, writing and debugging functions, and drafting tests and docs inside an existing codebase with its own conventions. These Aider prompts start from that: fill in your situation once and reuse it. The worked example below is a bug fix task, one of the most common for developers.
I'm a developer and need help with [task, e.g. writing and debugging code]. What I have: - [the material involved: code, draft, notes or data] What a good result looks like: - [the outcome and its format] Ask me one clarifying question if something important is missing, then give the result. About my work - Language, framework and versions: [e.g. TypeScript 5, Next.js 15, Node 20] - Relevant files or functions: [e.g. lib/billing.ts, the createInvoice function] - Conventions to follow: [e.g. no classes, Zod for validation, Vitest for tests] Context - Files involved: [list the files, or reference them in the chat] - How I build and test: [e.g. npm test]
How to use this prompt
- 1
Open Aider
Start aider in your repository and paste the prompt at the aider prompt.
- 2
Give it context
Add the files it should edit with /add before you send the prompt. Aider only edits files you have added.
- 3
Review and iterate
Aider commits each change to git, so review with git diff and use /undo if a change is wrong.
Working in Aider
- •Only /add the files that need changes. Extra files cost context and invite unrelated edits.
- •Because every change is a git commit, you can keep requests small and roll back cheaply.
- •Paste test output or error messages directly; aider works well in a fix, run, paste-error loop.
Example task: Bug Fix
What you give it
Expected: average([]) returns 0.
Actual: ZeroDivisionError: division by zero
Language: Python 3.12
def average(nums):
total = 0
for n in nums:
total += n
return total / len(nums)
Already ruled out: nums is always a list, never None. It only fails when a user has no orders yet.What a good answer looks like (shortened)
1. Root cause: when nums is empty, len(nums) is 0, so the return line divides by zero.
2. Fixed code:
def average(nums):
if not nums:
return 0
return sum(nums) / len(nums)
3. Why it works: the guard returns before any division happens. sum() replaces the manual loop and gives the same result for non-empty lists.
4. Check:
assert average([]) == 0
assert average([2, 4]) == 3.0Tips for better results
- •Paste the actual error output and the exact versions you run. Most wrong answers come from the AI assuming a different version of a library or framework.
- •Add the files it should edit with /add before you send the prompt. Aider only edits files you have added.
- •Check this before you use the output: check that every function, method and package the AI uses actually exists in your installed versions, and run the tests before you commit.
Check before you use it: Check that every function, method and package the AI uses actually exists in your installed versions, and run the tests before you commit.
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.
Variations
Task
Bug Fix: Replace the first line with: I have a bug I need fixed. Find the root cause before you suggest any change.
Fix with a regression test
Add this line under Output format: 5. A unit test that fails on the old code and passes on the fixed code.
Second task
Change the task line to: [Building features].
Save it as a Retext snippet
Retext is a free text expander for Mac. Save this prompt once, then type ;developer-aider in any app (ChatGPT, Claude, your editor, a browser tab) and the full prompt is pasted in.
- Click Add to Retext. The prompt installs as a snippet with the trigger ;developer-aider.
- Change the trigger in Retext if you prefer a different one.
- Type the trigger wherever you want the prompt, then fill in the brackets.
Frequently asked questions
How do developers keep AI-generated code consistent with their codebase?
Include one or two existing files as examples of your style and state your conventions in the prompt. Ask for changes as small diffs to existing code rather than whole new files.
Why didn't aider change the file I meant?
Aider edits only files added to the chat. Run /add with that file, then resend the prompt.
How do I undo a bad edit?
Use /undo in aider to revert its last commit, or use git as usual, since each change is committed.
How do I reuse this prompt without copying it every time?
Click Add to Retext to save it as a snippet. Then type ;developer-aider in any Mac app, including your AI tool, and the full prompt is pasted in.
Related Templates
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.