E2E Coverage Triage

Use this skill to reduce E2E runtime and flakes without losing real coverage. The aim is not to hide setup; it is to put each behavior at the right proof layer.

Core Rule

Scenario text describes product behavior. Step code handles test mechanics.

Only mention empty state, account creation, fixture IDs, seeded records, or test isolation in Gherkin when that is the product behavior under test. Do not mention helper internals, cleanup, Storybook, or ctx fields in feature text.

Coverage Boundary

Keep in app E2E when the scenario proves a real cross-boundary workflow: