Use when writing, reviewing, or improving tests in a frontend project — triggers include "write tests", "add tests", "test this component", "improve test coverage", "/frontend-testing", or any request to create or fix frontend tests. Also triggered when TDD is active in a frontend codebase to provide the testing context and patterns.
설치
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when writing, reviewing, or improving tests in a frontend project — triggers include "write tests", "add tests", "test this component", "improve test coverage", "/frontend-testing", or any request to create or fix frontend tests. Also triggered when TDD is active in a frontend codebase to provide the testing context and patterns.
Frontend Testing
Before writing any test
Inspect the stack — follow references/stack-detection.md. Read package.json, runner config, and an existing test file. Don't assume the runner, framework, utilities, or file conventions. If something looks weird or inconsistent, stop and advise before writing.
Match existing conventions — file naming, location, import style, test structure. Don't introduce a second pattern.
Reference files
../generic-testing/process.md — universal fundamentals (determinism, AAA, behavior over implementation). Apply on every test.