Design a new user flow before building it, or audit an existing flow for friction, using the product-flow-designer agent. Use when: planning a new multi-step feature (onboarding, signup, booking, invite, wishlist) before implementation, or auditing a conversion journey for drop-off, dead-ends, or mobile friction. Invoke with: /design-flow <flow> [design|evaluate]
Review frontend/design changes for klass-hero by spawning the design-system-guardian (static code: tokens, duplication, lint_typography + credo) and ui-critic (rendered: hierarchy, spacing, contrast, accessibility, mobile) agents in parallel, then consolidating into a unified report. Use when: reviewing a PR that touches LiveViews/components/templates/CSS, checking UI or design quality before merge, validating frontend changes, or after editing anything under lib/klass_hero_web/ or assets/css/. Invoke with: /review-design
Review code changes for DDD/Ports & Adapters architecture compliance by spawning the architecture-reviewer (12 structural checks), boundary-checker (6 semantic violation checks), and regression-analyzer (8 behaviour- preservation checks) agents in parallel. Consolidates findings into a unified report. Use when: reviewing a PR, checking architecture before merge, validating structural changes, or after modifying bounded context code. Invoke with: /review-architecture
Test-drive code changes using Playwright and Tidewave MCP. Verifies backend logic, UI flows, responsive design, and edge cases. Use when: completing a feature branch, before creating a PR, after addressing PR review comments, or when asked to "test-drive", "verify changes", or "QA this". Invoke with /test-drive [branch|unstaged|<issue-number>].
Use when writing, modifying, or reviewing tests for Elixir/Phoenix code in this project — ExUnit unit/integration tests, property-based tests with stream_data, or Phoenix LiveView tests. Triggers on `.exs` test files, `mix test` failures, modules ending in `Test`, `use ExUnit.Case`, `use ExUnitProperties`, `Phoenix.LiveViewTest`, `live/3`, `render_submit`, `assert_patch`, ConnCase, DataCase, Mox, factories, sandbox setup, or when adding tests for new domain models, schemas, use cases, or LiveViews. Distilled from "Testing Elixir" by Leopardi & Matthias.
Create well-formed GitHub issues from findings, hypotheses, or gaps discovered during codebase exploration. Explores code to validate the finding, gathers references, classifies issue type (FEATURE/BUG/TASK), selects labels, drafts the body following project templates, and creates via gh CLI. Invoke with: `/create-issue "description of finding"`. Also triggers on "file an issue", "open an issue", "create a ticket", "turn this into an issue".
Perform memory consolidation — a reflective pass over memory files that synthesizes recent learnings into durable, well-organized memories so future sessions orient quickly. Supports two modes: "consolidate" (full 4-phase pass) and "prune" (lighter cleanup of stale/duplicate memories). Use when: "dream", "consolidate memories", "clean up memories", "prune memories", "organize memories", or at the end of a productive session. Invoke with: /dream [consolidate|prune]
Upgrade Hex dependencies with safety checks and changelog review. Detects outdated deps, classifies upgrades by semver risk, presents an assessment table for confirmation, then applies upgrades with test verification. Use when: "upgrade deps", "update dependencies", "check for outdated packages", or "bump phoenix". Invoke with: /dep-upgrade [package-name|--all]