Grove Testing Skill When to Activate Activate this skill when: - Deciding what to test (not just how) - Writing tests for new Grove features - Reviewing existing tests for effectiveness - Asked to "add tests" without specific guidance - Evaluating whether tests are providing real value - Refactoring causes many tests to break (symptom of bad tests) For technical implementation (Vitest syntax, mocking patterns, assertions), use the skill alongside this one. --- The Testing Philosophy "Write tests. Not too many. Mostly integration." — Guillermo Rauch This captures everything Grove believes abou…