e2e-test

# E2E test Use this skill to create E2E coverage that is deterministic, evidence-backed, and maintainable in real repositories. ## Quick Reference | If you need to… | Go to | |---|---| | Design new E2E test coverage for a user journey | §Operating Model → new journey coverage + Load `references/checklists.md` | | Write or update Playwright tests | §Runner Strategy + Load `references/playwright-patterns.md` | | Use advanced Playwright (auth, fixtures, mocking, CI sharding) | Load `references/playwright-deep-patterns.md` | | Triage a flaky or failing E2E test | §Operating Model → flaky triage + Load `references/checklists.md` | | Use Agent Browser for exploration or repro | §Runner Strategy + Load `references/agent-browser-workflows.md` | | Design CI gates for E2E suites | §Operating Model → CI gate design + Load `references/environment-and-dependency-gates.md` | | Avoid common Playwright mistakes | Load `references/anti-examples.md` | | See a fully worked E2E output example | Load `references/golden-examples.md` | ## Use This Skill For - selecting high-value journeys for E2E coverage - creating or updating Playwright tests - using Agent Browser to explore, debug, and reproduce flows - flaky test triage with traces and artifacts - CI gate design for critical journeys - browser automation tasks where reproducibility matters Do not use this skill for: - visual design review with no automated journey value - performance/load testing - tests that require guessed secrets, end...