E2e engineer
200 role-specific AI agents across 20 teams with typed artifact pipelines, 14 methodology skills, and 15 pre-baked team formations. The virtual engineering org for Claude Code, Cursor, Codex CLI.
npx -y skills add IrfanSadiqRahat/constellation --skill e2e-engineerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Playwright / Cypress, page objects, parallel sharding, flake control.
SKILL.md
1.1 KB, as published. Nobody here has run it
e2e-engineer
Operating principles
- E2E only on critical paths. Five paths max; cover the rest with smaller tests.
- No
sleepever. Use proper waits (expect,waitFor). Sleep = source of flake. - Page objects > selector strings everywhere. One source of truth per page.
- Data setup via API, not UI. Faster, more stable.
- Trace + video on failure. Debug from the artefact, not by re-running.
- Parallel by default, shard for speed. Per-test isolation strict.
- Flake budget = 0. Quarantine flaky tests; fix or delete in 1 week.
- Run on real Chrome / Firefox / Webkit, not just Chromium.
Smell-check
- Tests depending on order → not isolated
- Auth flow re-executed in every test → use storageState
- XPath selectors → use accessible role/name first
- Tests that hit production → wrong layer
Hand-off contract
qa-lead owns the test pyramid. interaction-designer owns the flows being tested. CI runs the suite as a release gate.
Gives 1 of the 12 instructions most e2e browser skills give
Counted across 407 of the 410 authors here whose files we hold, read 2026-08-06
- use page object model patternin 35 of 407, across 25 files
- Snapshot to get element refsin 24 of 407, across 14 files
- keep tests independentin 23 of 407, across 18 files
- Interact using refs from the latest snapshotin 23 of 407, across 11 files
- clean up test data after each testin 21 of 407, across 15 files
- test user behavior not implementationin 20 of 407, across 14 files
- quarantine flaky tests explicitlyhere, and in 19 of 407, across 10 files
- wait for specific network conditionsin 18 of 407, across 8 files
- re-snapshot after navigation or dom changesin 17 of 407, across 10 files
- Detect running dev servers before writing test codein 17 of 407, across 7 files
- use web-first assertionsin 17 of 407, across 14 files
- capture screenshots or videos on test failurein 17 of 407, across 14 files
Said here and by no other author read
- limit e2e tests to five critical paths
- replace sleep calls with proper waits
- use page objects instead of selector strings
- set up test data via API not UI
- run tests on real browsers not just Chromium
- maintain strict per-test isolation
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.