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.