intuitive-testslisted

# Intuitive Tests Use this skill to make a test suite easier to understand, faster to run, and less coupled to implementation details. The goal is not "more tests." The goal is a suite where each test has an obvious reason to exist. Existing tests are not grandfathered in. If a current unit test does not prove project logic, caller-visible behavior, a meaningful failure mode, or a real contract, remove it, merge it into a stronger behavior test, or reclassify it to the correct layer. Treat structure-only, metadata-only, wiring-only, and implementation-shape tests as deletion candidates by default. The workflow is framework-agnostic, but the examples assume Python/pytest. ## Bounded Proposal Rule For broad or ambiguous cleanup, audit first and stop after a decision-complete proposal. Do not move files, delete tests, rewrite guidance, or edit production code until the target slice, accepted checklist, evidence level, and stop condition are explicit. For a precise target where the user asks for implementation, apply one coherent vertical slice. Keep newly discovered unrelated ideas parked instead of letting the work expand by drift. For test-suite cleanup, a good proposal lets the user choose between conservative, layout-first, pruning-first, or fixture-extraction paths. Verification skips are repo truth, not reusable skill truth. If some tests must not run because of network, credentials, simulator, hardware, paid APIs, or local services, derive the skip from the user's