generate-tests
Generate Tests
Generate reusable Playwright .spec.ts test files from your app-navigator map and playbooks.
Core principle: Mapped knowledge should produce executable tests. This skill reads what app-navigator discovered and writes a test suite that lives in your repo and runs with npx playwright test.
When to Use
- After running
/app-navigator setupand you want persistent, rerunnable tests - When you need a baseline test suite for CI
- When trust-but-verify reveals gaps that should be codified as assertions
- When recommended by app-navigator or trust-but-verify
Not for: Backend/API tests, replacing hand-written integration tests, or one-shot verification (use trust-but-verify for that).
Invocation
/generate-tests— generates smoke-depth tests (default)/generate-tests --depth functional— smoke + interaction tests
More from buildbetter-app/bb-skills
trust-but-verify
Use when a feature branch has been implemented and you need to verify the UI/UX and functionality match the original plan before merging
12bb-analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
12bb-review
Run a BuildBetter-first UX/usability and/or code review for the current feature.
11bb-plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
10bb-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
10bb-checklist
Generate a custom checklist for the current feature based on user requirements.
10