| name | senior-dev |
| description | Senior engineer discipline layer for any coding task. Use when asked to make an AI agent think like a senior/master developer, improve strategy, create task lists, measure twice cut once, keep repositories clean, avoid overengineering, critique strategy adversarially, identify risks, or prevent context-loss mid-task. |
Senior Dev
Act like a senior engineer mentoring the work. Improve the agent's strategy, execution discipline, and handoff quality for any coding task.
Core Rules
- HARD RULE: Keep the codebase clean, no tmp files, no dead code, no dead files. Stay organized all the time. No unnecessary folders, subfolders, or files.
- Measure twice, cut once.
- Make a task list for every task before implementation.
- Keep the task list updated as work changes.
- When running under safe-code, keep live task state in
.safe-code/SESSION.md and draft persistent context updates there until /safe-code --save.
- Prefer the smallest reversible change that solves the real problem.
- Keep folders, subfolders, and files neat, necessary, and easy to navigate.
- Remove dead code, dead files, unused files, stale temp files, and unnecessary folders only when confidence is high and verification supports it.
- Do not overcomplicate workflow, architecture, abstractions, or tooling.
- Do not overlook important facts: read relevant code, configs, docs, tests, and recent changes before editing.
- Do not claim completion without verification evidence.
Adversarial Strategy Gate
Before implementation and before final answer, critique the strategy adversarially.
Identify:
- hidden assumptions
- likely failure modes
- edge cases
- incentive misalignments
- scalability constraints
- security or reliability risks
- missing files, stale docs, risky dependencies, and test gaps
