Playwright E2E testing patterns with Page Object Model, configuration, CI/CD setup, and flaky test strategies.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add affaan-m/everything-claude-code --skill e2e-testingCompatible with
Supported agents
Provides Page Object Model structure for maintainable test organization, with reusable page classes that encapsulate locators and navigation logic
Covers multi-browser testing across Chromium, Firefox, WebKit, and mobile devices with configurable retries, parallelization, and artifact capture (screenshots, videos, traces)
Includes flaky test identification and remediation pa
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versione2e-testingExecute the skills CLI command in your project's root directory to begin installation:
epx add affaan-m/everything-claude-code --skill e2e-testingFetches e2e-testing from affaan-m/everything-claude-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/e2e-testing
Restart Cursor to activate e2e-testing. Access via /e2e-testingin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
playwright-e2e-testing
bobmatnyc/claude-mpm-skills · Testing · 2 shared tags
java-coding-standards
affaan-m/everything-claude-code · Backend · same repo
nuxt4-patterns
affaan-m/everything-claude-code · Productivity · same repo
investor-outreach
affaan-m/everything-claude-code · Productivity · same repo
springboot-security
affaan-m/everything-claude-code · Productivity · same repo
autonomous-loops
affaan-m/everything-claude-code · Productivity · same repo
e2e-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: e2e-testing is focused, and the summary matches what you get after install.
e2e-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
e2e-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added e2e-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: e2e-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
e2e-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: e2e-testing is focused, and the summary matches what you get after install.
e2e-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: e2e-testing is focused, and the summary matches what you get after install.
showing 1-10 of 64