app-navigator
App Navigator
Map your application's UI and build reusable Playwright playbooks for browser-based testing and verification.
Core principle: Know your app before you test it. This skill creates a living knowledge base of routes, pages, components, and interactions that other skills (like trust-but-verify) build on.
When to Use
- Setting up browser-based testing for the first time in a project
- After significant UI changes that may have shifted routes or layouts
- Before running trust-but-verify, if no app-map.md exists yet
- When you need to understand the app's page structure
Not for: API-only projects, backend-only changes, or projects without a web UI.
Invocation
/app-navigator setup-- map the app and write playbooks/app-navigator audit-- UI/UX audit (v2, not yet implemented)
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