Quality

CMUX Architecture defines the cmux package structure, layering model, dependency inversion, and Swift 6 concurrency rules. Use it before adding or meaningfully rewriting Swift files, packages, coordinators, services, repositories, or public package APIs.

CMux Debugging instruments debug events, provides a Debug menu, and avoids runtime pitfalls in the cmux terminal multiplexer. Use it when adding debug probes, diagnosing UI/runtime issues, or touching terminal rendering and list views.

CMUX Shared Behavior enforces a single shared action and mutation path across all entrypoints (shortcuts, command palette, context menu, CLI, settings, debug menu) with consistent optimistic updates and rollback; use it when adding entrypoints or when tests missed a bug.

Cmux Socket Policy defines threading and focus rules for cmux socket and CLI commands to keep telemetry off the main thread and prevent commands from stealing macOS app focus.

cmux Testing defines Swift Testing rules for cmux and validates test target compilation and test wiring. Use when adding or changing tests, touching package/refactor code, or deciding whether reload.sh is enough validation.

Intended vs Implemented compares documented requirements against actual code to find security and correctness gaps that generic scanners miss, citing both documentation and implementation evidence for each finding. Use it when auditing AI-built code, access control, or whether a codebase matches its own documentation.

Shipping Artifacts defines the durable documentation set that makes an AI-built app reviewable before shipping: architecture, user/permission flows, variables/secrets, and a test-coverage map, plus conditional docs for emails, cron, SEO, and embedded agents. Use when documenting a codebase for handoff, mapping trust boundaries, planning test coverage, or preparing for security or performance

Sprint Retrospective Facilitator guides a structured sprint retrospective, identifying what went well, what didn't, and prioritized action items with owners and deadlines. Use it when running a retrospective, reflecting on a sprint, or turning team feedback into actionable improvements.

Strategy Red Team attacks the load-bearing assumptions in a PRD, roadmap, or strategy before reality does. It steelmans each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria. Use when stress-testing a plan or preparing a doc for executive review.

Test Scenarios creates comprehensive test scenarios from user stories, including test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use it when writing QA test cases, creating test plans, defining acceptance tests, or validating feature implementations.

Performs automated accessibility audits on web content, identifying WCAG violations and suggesting fixes. Useful for developers ensuring inclusive user interfaces.

Performs adversarial code reviews to identify vulnerabilities, bugs, and weaknesses, enhancing software quality and security.