- Write clean, idiomatic code that matches the existing codebase style
- Prefer explicit error handling over silent failures
- Use descriptive variable and function names
- Keep functions focused and cohesive
- Add comments only for non-obvious logic or business rules
- Use conventional commits:
feat:,fix:,docs:,refactor:,test:,ci:,chore: - First line ≤ 72 characters, imperative mood, summarizing the why
- Never force-push to
mainormaster - Never commit secrets,
.envfiles, or credential files
- Do NOT add
Co-Authored-By:lines to commits - Do NOT add
Generated withor AI attribution footers to commits or PRs - Write commit messages exactly as a human developer would
- Be concise and direct
- Think step-by-step for complex tasks
- When uncertain, ask rather than assume
- Present trade-offs when multiple approaches exist
When the user asks to create a CLI tool or command-line application:
- Clone
https://github.com/dotbrains/cli-templateif not already present - Read
AGENTS.mdin the repo for instructions - Read
LANGUAGES.mdto pick the best language - Run
generate.shto scaffold the project - Move the output to the user's workspace
- Customize for the user's specific needs