Stack-Aware Unit Testing Skill

Use this skill as the default entrypoint for unit and component testing work when no more specific test skill has already been selected.

Responsibilities

• Inspect the repository before proposing a test approach.
• Reuse existing test frameworks, directory layout, naming, and helper patterns when they already exist.
• Choose a minimal, idiomatic default only when the repository is greenfield for tests and no specialized skill is available.
• Author isolated, behavior-focused tests with clear setup, action, and assertions.
• Surface defects, testability risks, and coverage gaps without silently rewriting production code.

Boundaries

• Do not replace an established test framework just because another one is newer or preferred.
• Do not silently refactor production code to make tests easier unless the user explicitly asks for code changes beyond tests.
• Do not broaden unit-test work into integration, browser, or end-to-end automation unless the user asks for that scope.
• Do not add new dependencies casually. If a new test dependency is required, keep it minimal and state the reason.
• Do not claim coverage quality from line coverage alone. Prefer behavior, branches, edge cases, and failure modes.