klass-hero

Diagnose a production issue end-to-end across Honeycomb (error shape) and the prod DB error_tracker tables (who + why), scope impact honestly, and optionally file a PII-scrubbed issue. Invoke with: /analyze-prod-issue "<symptom>"

Fetch, triage, and address PR review comments for the current branch. Reads all comments from the PR, classifies each as actionable, nit, question, or dismissible, presents a structured assessment for confirmation, then plans and applies fixes. Use when: "address PR comments", "handle review feedback", "fix PR comments", "triage PR review", "respond to review", or after receiving PR review notifications. Invoke with /address-pr-comments.

Deliberate TDD-first, design-heavy workflow for building an Elixir/Phoenix change end-to-end — surface rival designs, pick one, drive red→green, keep the test suite lean. Invoke with: /build-elixir <what you're building>

Use when the user wants to read a Daily QA discussion by number, triage the findings (Carried-Forward and New Code Review), assess validity against current code, present a structured summary, then systematically fix confirmed issues. Invoke with the discussion number as argument (e.g. `/triage-qa-discussion 449`).

This skill should be used when the user wants to assess or scope a GitHub issue before committing to work — triggers on "assess issue

Test-drive code changes using Chrome DevTools 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>].

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".

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 entities, schemas, context functions, or LiveViews. Distilled from "Testing Elixir" by Leopardi & Matthias.

Scaffold a new database-backed entity in conventional Phoenix (schema-as-struct). Generates an Ecto migration and ONE entity module (Ecto schema + struct + functional core) at the context root, a test, and wires CRUD into the context facade. Invoke with: /gen-migration <context> <entity> [field:type ...] [--references table:field] Example: /gen-migration messaging reaction message_id:binary_id emoji:string --references messages:message_id

Review code changes for conventional-Phoenix convention compliance by spawning the architecture-reviewer (8 structural checks), boundary-checker (5 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

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

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]