Skip to content
Skills Library
Programming · Testing

e2e-setup

/e2e-setup

Learn a web app once and write .e2e/e2e-env.md, the environment file every other E2E skill reads first. Also checks that playwright-cli, which the other E2E skills rely on, is installed. Use when a repo has no .e2e/e2e-env.md yet, when asked to set up or prepare Playwright E2E testing for an app, or when that file is stale after an auth, roles or seed change.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Learn a web app once and write .e2e/e2e-env.md, the environment file every other E2E skill reads first. Also checks that playwright-cli, which the other E2E skills rely on, is installed. Use when a repo has no .e2e/e2e-env.md yet, when asked to set up or prepare Playwright E2E testing for an app, or when that file is stale after an auth, roles or seed change.

Original author description

Learn a web app once and write .e2e/e2e-env.md, the environment file every other E2E skill reads first. Also checks that playwright-cli, which the other E2E skills rely on, is installed. Use when a repo has no .e2e/e2e-env.md yet, when asked to set up or prepare Playwright E2E testing for an app, or when that file is stale after an auth, roles or seed change.

How it works

  1. 1. Read
  2. 2. Ask
  3. 3. Prove
  4. 4. Write
Original SKILL.md headings · 75 lines, 628 words
SKILL.md preview
---
name: e2e-setup
description: Learn a web app once and write .e2e/e2e-env.md, the environment file every other E2E skill reads first. Also checks that playwright-cli, which the other E2E skills rely on, is installed. Use when a repo has no .e2e/e2e-env.md yet, when asked to set up or prepare Playwright E2E testing for an app, or when that file is stale after an auth, roles or seed change.
license: MIT
---

# e2e-setup

Input: the repo (if any), a base URL, one test account. Output: `.e2e/e2e-env.md`, committed, and `.env.e2e` with the passwords, never committed. Later sessions read it instead of re-learning the app, so it holds what a QA engineer needs on day one and nothing a reader can get from one `cat`.

Facts come from code first. A crawl sees only what is reachable and misses roles, flags and reset hooks; the code has all three. Steps 1 and 2 use file reading and search only. The browser is used once, in step 3, to prove the file, and `playwright-cli` is the one command needed.

Every E2E skill needs `playwright-cli`. If `playwright-cli --version` fails, ask the user to run `npm install -g @playwright/cli@latest`, then continue.

## 1. Read

In this order, stopping when the question is answered:

1. README, `package.json` scripts, Dockerfile or compose: how it runs, ports.
2. Routes or pages: the URL list and which ones need a session.
3. Auth: login route, session cookie or token, redirect when signed out, roles or plan tiers, feature flags that gate UI.
4. Seed, fixtures, migrations: test accounts, seeded records a test can rely on by name, prices.
5. Test hooks: reset or reseed endpoints, latency or failure toggles, anything under `_` or `debug`.
6. Ready signals: `data-state`, `aria-busy`, loading text, toasts. Locator conventions: `data-testid` pattern, labels on inputs.
7. Existing Playwright config and specs: base URL, `storageState`, what is already covered.

Done when: every section of the file below has either a fact with its source file, or `unknown`.

## 2. Ask

Collect every `unknown` and every guess into one short list and ask the user once. Typical gaps: base URL per environment, which account is safe to use, how to reset state, what must never be touched (production data, real emails, real payments). No user available: keep the list as the file's `Open questions` section.

## 3. Prove

One smoke check. Each step is one `playwright-cli` command, in this order: `open <base url><login path>`, `snapshot`, `fill <email ref> <email>`, `fill <password ref> <password>`, `click <submit ref>`, `snapshot`, `close`.

Write down the exact labels and button name of the login form and the landing URL as seen, since specs will repeat these steps verbatim. The app is already running at the base URL given; a 404 or connection error on `open` goes under `Open questions` and the login section stays `(unverified)`.

Done when: the login steps in the file ran once live.

## 4. Write

Passwords first. Each one goes into `.env.e2e` at the repo root as `E2E_PASSWORD_<NAME>=<password>`, and `.env.e2e` goes into `.gitignore` before anything is committed. No password, token or key is ever written to `.e2e/e2e-env.md`; that file names the variable.

Then `.e2e/e2e-env.md`, markdown, under 60 lines, these headings in this order:

```
# Test environment: <app name>
- Base URL: <url>
- Reset: <endpoint or command, or "none: tests must clean up">
- Never touch: <list, or "nothing known">

## Accounts
- <email>, password in `E2E_PASSWORD_<NAME>` (`.env.e2e`), <role>, <what they own in the seed>

## Login
<the exact steps as proven: goto, labels, button, landing URL>

## Pages
- <path>: <what it is>, <auth required?>, <ready signal>

## Seed facts tests can rely on
- <records by display name, prices, counts>

## Test hooks
- <toggle>: <effect>, <how to turn on and off>

## Conventions
- Locators: <testid pattern, label style>
- Ready signals: <attribute and values>

## Existing suite
- <config path, how to run, what is covered, or "none">

## Open questions
- <each unknown or guess>
```

Mark every line that came from a guess with `(unverified)`. Done when the file exists, the login section was proven in step 3, `Open questions` lists every guess, and `git check-ignore .env.e2e` prints the path.

Versions

The database has no other skills named e2e-setup.

Database snapshot: 13.11.2026 · package version 836f279a4090 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pw-init
    Set up Playwright in a project. Use when user says \"set up playwright\", \"add e2e tests\", \"configure playwright\", \"testing setup\", \"init playwright\", or \"add test infrastructure\".
  • 100pw-init
    Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".
  • 100pw-init
    Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".
  • 100playwright-testing
    Use when a manual-QA agent does live browser testing through the Playwright MCP server — exploring/profiling a web app or executing a web test case against a running app, with no test code generated. Web/PWA/hybrid targets; used by app-profiler and test-runner. Mobile native →…
  • 100playwright-testing
    Use when a manual-QA agent does live browser testing through the Playwright MCP server — exploring/profiling a web app or executing a web test case against a running app, with no test code generated. Web/PWA/hybrid targets; used by app-profiler and test-runner. Mobile native →…
  • 100playwright-e2e
    End-to-end test and click-verify a web app with Playwright — write specs, drive authenticated pages, screenshot, and run in CI. Use when a web change has to be proven in a real browser rather than by unit tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.