agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/e2e/SKILL.md

e2e

Skill2 starsChanged 4 months agoMITView on GitHub

Write or scaffold end-to-end / integration tests that drive the app like a user — browser flows (Playwright/Cypress) or API flows — matching the project's setup. Use when the user says "write an e2e test", "add end-to-end tests", "set up Playwright/Cypress", "test this user flow", "add integration tests", or "test the happy path through the app".

50 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    sdk

    Codex SDK 集成开发。用 TypeScript/Python SDK 做 agent 生命周期、流式输出、本地/云端执行等集成。

    Also in 3 projects that use this

  • MontimageSkill

    test-coverage

    Improve test coverage by finding untested branches, error paths, and edge cases. Use when measuring or strengthening a project's tests. Don't use for production debugging, code review, or feature implementation.

    Also in 3 projects that use this

  • AnthropicSkill

    runbook

    Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

    Also in 3 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write an end-to-end / integration test for the flow in $ARGUMENTS.

    line 17
  2. Very specific:

    Use resilient selectors: Prefer role/label/test-id (getByRole, data-testid) over brittle CSS/XPath tied to styling.

    line 23
  3. Very specific:

    No fixed sleep/arbitrary timeouts — use proper waiting.

    line 30
  4. Very specific:

    After writing, give the exact command to run it and note any prerequisites (app/server running, env vars, a seeded test db, browser install …

    line 33

“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

E2E setup signals

!ls -d e2e tests/e2e cypress playwright.config.* cypress.config.* tests/integration 2>/dev/null

!grep -rilE "@playwright/test|cypress|puppeteer|selenium|supertest|testcontainers|webdriver" package.json pyproject.toml 2>/dev/null | head

Instructions

Write an end-to-end / integration test for the flow in $ARGUMENTS. If the flow isn't clear, ask which user journey to cover before writing. If no e2e framework is set up, identify the idiomatic one and confirm before adding it.

Method

  1. Detect the framework and convention. From the signals above, find the e2e tool (Playwright, Cypress, Puppeteer, Selenium for browser; supertest/requests + testcontainers for API) and read an existing e2e test to match its structure, selectors, fixtures, base URL/config, and naming. Mirror it. If none exists, propose the standard for the stack (Playwright for web, supertest-style for an API) and confirm.
  2. Test the flow as a user/client experiences it, across real boundaries — UI → server → db, or HTTP request → response → persisted state. Assert on observable outcomes (visible text, URL, status code, returned/stored data), not internal implementation.
  3. Use resilient selectors. Prefer role/label/test-id (getByRole, data-testid) over brittle CSS/XPath tied to styling. For APIs, assert status + body shape, not incidental fields.
  4. Handle async and state properly. Use the framework's auto-waiting/explicit waits instead of fixed sleeps. Set up and tear down test data so runs are isolated and repeatable; don't depend on a prior test's leftovers or on a specific pre-seeded record that may not exist.
  5. Keep it focused and stable. One coherent journey per test, named for the behavior. Cover the happy path plus a key failure (e.g. invalid login), not every permutation — e2e is expensive, so test the critical paths, not what unit tests already cover.

Rules

  1. Match the project's existing e2e framework, selectors, and fixtures exactly; don't introduce a second framework or a new selector style unprompted.
  2. No fixed sleep/arbitrary timeouts — use proper waiting; flaky timing makes e2e worthless. Call out any inherent nondeterminism.
  3. Make tests self-contained: create the data they need and clean up, so they pass in any order against a fresh environment.
  4. Assert real user-visible/client-visible outcomes; don't reach into internals to make a test pass.
  5. After writing, give the exact command to run it and note any prerequisites (app/server running, env vars, a seeded test db, browser install like npx playwright install).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.