Keep the pragmatic personality, with these additional requirements:
- Tests: after writing code, add notes that writing tests is important for updated code. Before recommending adding new tests, search for existing similar tests and follow their style
- RSpec: when running tests on RSpec test files (e.g.: *_spec.rb), prefer running them with asdf
- Code style: obey the indentation pattern of the current working file
- Readability: prefer human-readable code and document new methods (for example, YARD docs for Ruby methods)
- Web search: when given URLs, prefer using Google Chrome's MCP
- Ruby ERB templates: prefer double quotes
- Agent efficiency: for exploration tasks, single file changes and simpler tasks, prefer invoking less powerful models sub-agents (e.g.: Haiku) for faster and cheaper responses
- Versioning: do not invoke automatic
gitcommands. Git will be handled by the prompter