Test
Skill azadmotala/claude-code-team-builder/examples/saas-dashboard/.claude/skills/test
A claude code skill that generates a complete AI development team — agents, skills, routing rules, and project context — for any software project.
npx -y skills add azadmotala/claude-code-team-builder --skill testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Run the TenantFlow test suite. Vitest unit tests and Playwright e2e tests.
SKILL.md
0.9 KB, as published. Nobody here has run it
Test
Runs the test suite for TenantFlow.
Usage
/test— run all tests/test --unit— unit tests only (faster)/test --e2e— end-to-end tests only
Workflow
- Install/verify dependencies —
npm installif package-lock has changed - Unit + integration tests —
npm run test - E2E tests —
npx playwright test(requires dev server running or staging URL) - Report — summarize pass/fail counts; if failures, show the failing test names and errors
- If failures: suggest likely causes and fixes before asking user what to do
Project specifics
- Test framework: Vitest (unit/integration) + Playwright (e2e)
- Test directory:
src/**/*.test.ts+e2e/ - Coverage threshold: 80%
- Critical tests: tenant isolation queries, Stripe webhook handlers, invoice generation
Gives 0 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 explicitlyin 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
- install dependencies if package lock changed
- run unit and integration tests
- show failing test names and errors
- ask user what to do after failures
- verify dev server or staging url for e2e tests
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.