Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/e2e
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Passed 19 of 20 test cases with the skill, and 10 of 20 without it.
and 14 more in the full report
10 fixed9 passed either way0 still failing1 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just created a fresh git worktree to work on an E2E test in `apps/web`. Before running any Playwright tests or package commands, I want to make sure the environment is ready. What dependency installation command should I run, and from which directory?
| Checked | Without skill | With skill |
|---|---|---|
| Navigates to the apps directory before executing pnpm install | Missed | Passed |
| Passes the frozen-lockfile flag during workspace dependency installation | Missed | Passed |
The instructions your model reads when the skill loads.
Write and run E2E coverage directly in the primary conversation. For a cost-controlled feature workflow, the user switches that conversation to the lower-cost implementation/test model before this phase.
Write E2E tests using TDD (Red-Green-Refactor). Always run the tests you create and watch them fail before implementing.
/tdd — Follow the Red-Green-Refactor cycle when writing tests./pr-fixup — Use after the PR opens only for CI or reviewer findings./playwright-cli — Interactive browser automation. Use to validate features against the dev server before writing tests, and to debug failing tests with --debug=cli.Load references/fixture-state.md for capability-readiness, remembered
workflow selection, cross-record correlation, restart persistence, and
provider-backed PR feedback fixture rules.
Load references/ui-state-and-cleanup.md for lifecycle, WebSocket, terminal,
Dockview, and sidebar/context-menu rules.
apps/web/e2e/
apps/web/e2e/
├── fixtures/
│ ├── backend.ts # Worker-scoped backend + frontend process
│ ├── test-base.ts # Extended fixture (apiClient, seedData, testPage)
│ └── office-fixture.ts # Office fixtures (officeApi, officeSeed with workspace+agent)
├── helpers/
│ ├── api-client.ts # HTTP client for seeding data (read for available methods)
│ └── office-api-client.ts # Office-specific API client (onboarding, issues, agents)
├── pages/ # Page objects (read for available pages and methods)
└── tests/ # Spec files (*.spec.ts), grouped by feature
├── task/ # Task creation, deletion, archiving, environment, subtasks
test cases passed, vs 10 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.