alexei-led/testing-e2e
dist/gemini/skills/testing-e2e/SKILL.md
Playwright-based end-to-end browser testing of user flows. Use when running existing Playwright tests, generating browser checks, recording a visible session, or verifying a user journey end-to-end. NOT for unit tests, API-only tests, or logic tests where curl or JSDOM suffices — use improving-tests or fixing-code instead.
$ install --global
skillsauthnpx skillsauth add alexei-led/claude-code-config testing-e2eInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 18, 2026, 3:50 AM343.9s1 file scanned
SKILL.md
- description:
- Playwright-based end-to-end browser testing of user flows. Use when running
- name:
- testing-e2e
E2E Testing with Playwright
Run browser tests against real user flows. Keep scripts temporary unless the user asks to add permanent tests.
Workflow
- Ask what to run if the user did not specify: existing tests, generate a new check, record a session, or verify a feature.
- Read existing test context:
playwright.config.*package.jsonscripts**/*.spec.ts,**/*.test.ts,**/e2e/**- fixture, seed, and database reset docs
- Detect or start the dev server from project docs/scripts.
- Use deterministic fixtures. No production data, random order, wall-clock dependence, or leftover state.
- Generate temporary scripts under
/tmpwhen needed. - Prefer semantic locators: role, label, text, test id, CSS last.
- Run the test, read the full output, fix failures, and rerun.
Playwright Helper Skill
If the bundled playwright-skill helper is installed alongside this skill,
find its directory from the loaded skill path and run helper scripts from
there:
cd <playwright-skill-dir> && node scripts/run.js /tmp/e2e-check.js
If the helper is unavailable, use project-local Playwright commands instead:
npx playwright test --reporter=list
npx playwright test /tmp/e2e-check.spec.ts --reporter=list
Generated Test Rules
- Write temporary tests to
/tmp/e2e-<name>.spec.tsor/tmp/e2e-<name>.js. - Never use fixed
waitForTimeoutdelays. - Use
waitForSelector,waitForURL, or assertions on visible UI state. - Capture screenshots, traces, or HTML reports when failures need evidence.
- Do not declare success while tests fail.
Failure handling
- No dev server running: read project docs and
package.jsonscripts for a start command; ask the user if none found. - Test still failing after two fix attempts: capture a screenshot/trace, report the exact failure line, and stop — do not loop blindly.
- No
playwright.config.*found: generate a minimal temporary config under/tmp; do not write into the project without asking.
Output Contract
## E2E Result
### Target
<app/flow tested>
### Commands
- `<command>`
### Result
pass | fail | blocked
### Evidence
- screenshot/trace/output path or key failure line
### Next Fix
- <if failing>
Related Skills
alexei-led/spec-flow
tools
VerifiedTrustedCommunity
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
35SKILL.mdUpdated Jul 18, 2026
alexei-led/writing-web
development
VerifiedTrustedCommunity
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
35SKILL.mdUpdated Jul 18, 2026
alexei-led/writing-typescript
tools
VerifiedTrustedCommunity
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
35SKILL.mdUpdated Jul 18, 2026
alexei-led/writing-shell
tools
VerifiedTrustedCommunity
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.
35SKILL.mdUpdated Jul 18, 2026