code-commentsRules for when a code comment earns its place. Use whenever writing new code, reviewing a diff, or deciding whether to keep, cut, or rewrite a comment — including docstrings and doc comments. Triggers on writing functions, reviewing PRs, "should I comment this", "add a docstring", or any comment alr
test-strategyDeciding what deserves a test, what kind (unit/integration/e2e), and when to write it — as distinct from how to write a good test (see writing-tests). Use when planning test coverage for new code, reviewing a PR for missing or excessive tests, or choosing between a unit, integration, or end-to-end t
unslopCut AI tells from any writing. Must always apply.