waxon

Use before any Waxon fix or behavior-changing edit, especially behavior regressions, product-flow issues, auth/deploy/UI bugs, or changes where user-stated specs or the overarching product objective could be lost. Reads SPECS.md and keeps the objective, failure, causal hypothesis, non-goals, and proof path aligned before editing.

Run a Waxon browser-use test suite from a markdown file. Use when the user asks to run, rerun, execute, validate, or fix a Browser Use or signed-in user experience suite and provides or references a `.md` test-suite file such as `tests/browser-use-signed-in-user-experience.md`.

Use when making Waxon design, styling, layout, responsive UI, visual polish, or frontend interaction changes. Loads the repo-local design-system reference and approved UI comparison workflow before editing the Next.js app.