What problem does it solve? Teams often struggle to decide what to verify at the whole-system level: which requirements need a system test, which user flows deserve an E2E scenario, and how to prove acceptance criteria are actually covered. This Skill provides structured guidance for the broad-confirmation layer of testing so nothing critical is left unverified and nothing trivial bloats the suite. ## Core Features & Use Cases - System Testing Guidance: Enumerate functional and non-functional requirements (performance, security, availability, data integrity) and assign one representative end-to-end scenario per requirement. - E2E Testing with Playwright: Select business-critical user flows, write minimal through-scenarios using role/label selectors and auto-waiting, and cap scenario counts to keep CI fast. - Acceptance Testing (UAT): Build a traceability table mapping each agreed acceptance criterion to exactly one test written in business vocabulary. - Use Case: Before a release, use this Skill to list all functional and non-functional requirements, confirm each has a representative scenario, and verify no acceptance criterion lacks a corresponding test. ## Quick Start Ask the AI to apply the levels-system skill to design system, E2E, and acceptance tests for your release requirements.
