What problem does it solve? Writing automated tests without a consistent architecture leads to duplicated components, flaky suites, and untraceable coverage. This Skill enforces the KATA (Komponent Action Test Architecture) pattern on Playwright + TypeScript projects through a mandatory Plan → Code → Review workflow, so every test is atomic, traceable to a TMS ticket, and passes type, lint, and execution gates before merge. ## Core Features & Use Cases - Structured Plan → Code → Review pipeline: Plans ATCs from acceptance criteria with anti-duplication checks against kata-manifest.json, codes components and test files via isolated subagents, then runs three parallel verifiers (test, typecheck, lint) as the merge gate. - KATA component architecture: Generates Api/Page components extending ApiBase/UiBase, registers them in fixtures, selects the correct fixture ({api}, {ui}, or {test}), and applies equivalence partitioning, BVA, and ATC atomicity rules. - Read-only explain mode: Explains existing automated tests and reports their assertions without entering the Plan-Code-Review workflow or editing any files. - Use Case: Given a Jira story with acceptance criteria, the Skill derives candidate ATCs, reuses existing components from the manifest, writes the integration or E2E test under tests/integration/{module}/ or tests/e2e/{module}/, and verifies it with bun run test, types:check, and lint:check before handing off to git workflows. ## Quick Start Ask the AI to automate the acceptance criteria of a specific Jira ticket into KATA-compliant Playwright tests using the test-automation skill.
