Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-testingExecute the skills CLI command in your project's root directory to begin installation:
Fetches web-testing from mrgoonie/claudekit-skills 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:
Restart Cursor to activate web-testing. Access via /web-testing in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
0
total installs
0
this week
2.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2.0K
stars
Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.
npx vitest run # Unit tests
npx playwright test # E2E tests
npx playwright test --ui # E2E with UI
k6 run load-test.js # Load tests
npx @axe-core/cli https://example.com # Accessibility
npx lighthouse https://example.com # Performance
| Layer | Ratio | Framework | Speed |
|---|---|---|---|
| Unit | 70% | Vitest/Jest | <50ms |
| Integration | 20% | Vitest + fixtures | 100-500ms |
| E2E | 10% | Playwright | 5-30s |
./references/unit-integration-testing.md - Unit/integration patterns./references/e2e-testing-playwright.md - Playwright E2E workflows./references/component-testing.md - React/Vue/Angular component testing./references/testing-pyramid-strategy.md - Test ratios, priority matrix./references/cross-browser-checklist.md - Browser/device matrix./references/mobile-gesture-testing.md - Touch, swipe, orientation./references/shadow-dom-testing.md - Web components testing./references/interactive-testing-patterns.md - Forms, keyboard, drag-drop./references/functional-testing-checklist.md - Feature testing./references/performance-core-web-vitals.md - LCP/CLS/INP, Lighthouse CI./references/visual-regression.md - Screenshot comparison./references/test-flakiness-mitigation.md - Stability strategies./references/accessibility-testing.md - WCAG checklist, axe-core./references/security-testing-overview.md - OWASP Top 10, tools./references/security-checklists.md - Auth, API, headers./references/vulnerability-payloads.md - SQL/XSS/CSRF payloads./references/api-testing.md - API test patterns./references/load-testing-k6.md - k6 load test patterns./references/pre-release-checklist.md - Complete release checklistjobs:
test:
steps:
- run: npm run test:unit # Gate 1: Fast fail
- run: npm run test:e2e # Gate 2: After unit pass
- run: npm run test:a11y # Accessibility
- run: npx lhci autorun # Performance
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
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.
mrgoonie/claudekit-skills
mrgoonie/claudekit-skills
github/awesome-copilot
aj-geddes/useful-ai-prompts
refoundai/lenny-skills
supercent-io/skills-template
web-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
web-testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in web-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added web-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
web-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: web-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
web-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
web-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: web-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: web-testing is focused, and the summary matches what you get after install.
showing 1-10 of 39