- Use British English spelling in comments, strings, and documentation
- For non-trivial work, use plan mode to confirm the approach before implementation
- No demos, examples, or documentation unless explicitly requested
- For anything beyond a trivial single change, use TaskCreate to break down the task into sensible, actionable steps before starting work
- Use TaskUpdate to mark tasks
in_progresswhen starting andcompletedwhen done - Use TaskList to review progress and identify the next task
- Keep tasks granular enough to track progress but not so fine-grained they become noise
- Use TDD (red, green, refactor) for anything beyond a trivial single change, when a test platform is available — write a failing test first, make it pass, then refactor
- Use the framework's native test tooling
- Cover edge cases and error paths, not just happy paths
- Use conventional commits:
feat:,fix:,refactor:,test:,chore:, etc. - Keep commits atomic and focused
- Briefly reflect on what could have been done better — approach, structure, performance, or missed edge cases
- Share the reflection concisely so we can improve iteratively