What problem does it solve? Setting up a test framework from scratch involves dozens of decisions—directory layout, config timeouts, fixture architecture, data factories, CI reporters—that are easy to get wrong and tedious to repeat. This Skill automates the entire initialization so a project gets a consistent, convention-following test setup in one guided run. ## Core Features & Use Cases - Stack Auto-Detection: Scans project manifests (package.json, pyproject.toml, go.mod, pom.xml, etc.) to detect frontend, backend, fullstack, or mobile stacks and selects the right framework (Playwright, Cypress, pytest, JUnit, Go test, xUnit, RSpec, Maestro). - Complete Scaffolding: Creates test directories, framework config with tuned timeouts and reporters, .env.example, fixture indexes with mergeTests, faker-based data factories with auto-cleanup, and sample tests following Given-When-Then structure. - Write-Time Enforcement: Installs a Claude Code hook (tea-enforce.cjs) that blocks hard-coded waits and other test-quality violations at write time, with stack-scoped globs in .tea/enforce-config.json. - Use Case: A team starting a React + Vite storefront runs the workflow and receives a Playwright setup with auth fixtures, an order factory, sample API and UI tests, package.json scripts, and a tests/README.md—validated against a built-in checklist. ## Quick Start Ask the agent to set up a test framework for this project, for example by saying "let's setup test framework", and follow the Create mode prompts.
