mux

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)

Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)

Connects Mux mobile (Expo web/native) to an isolated dev-server sandbox with deterministic port setup, backend pairing, and Chrome MCP interaction. Use when implementing or validating mobile features against a sandboxed Mux backend.

Terminal-Bench integration for Mux agent benchmarking and failure analysis

Regenerate high-resolution README screenshots from Storybook stories. Use this skill when Chromatic detects visual diffs in any story under "Docs/README Screenshots", or when story data/layout changes require updated documentation assets. Triggers on: Chromatic visual regressions in readme screenshot stories, changes to App.readmeScreenshots.stories.tsx, changes to mockFactory.ts that affect screenshot stories, or explicit user request to update README images.

Guidelines for creating and managing Pull Requests in this repo

Testing doctrine, commands, and test layout conventions

Sub-agent powered code reviews spanning correctness, tests, consistency, and fit

Guidelines for when to use (and avoid) useEffect in React components