Frontend reviewer for legacy or progressive JS/TS bundles. Use PROACTIVELY after editing any frontend-tier .{js,ts,jsx,tsx,vue,svelte} file, or after touching blocks inside server-side template files (PHP / ERB / Twig / Razor — the hook can't detect view-embedded script edits, so AI judgment backstops here). Audits…
Deterministic harness trim/dedupe/validate driven by the harness-revise skill and G1-G13 gap taxonomy. Use when running /harness-revise, or when the user explicitly asks to trim/dedupe/validate .claude/. For broader reliability/cost/throughput scoring, use /harness-govern (its conform step applies the official…
Performance specialist. Owns latency / index usage / query count for relational data-access (N+1, EXPLAIN, index coverage, query-count regressions) AND — when a frontend or native trap sheet is active — client/runtime performance (bundle size, render / re-render, memory leaks, Web Vitals). Use proactively on…
Opt-in /dhpk:do --plan consultant: critique or sketch an implementation plan, then perform a manually requested warm or cold diff review. Return a verdict-first, END-terminated result under the mode's token cap; bounded read-only discovery uses at most 2 Explore children and 12 planner reads.
Python build-error resolution specialist. Use PROACTIVELY when a Python toolchain command fails — ruff check / ruff format, mypy / pyright, pytest (incl. pytest-asyncio scope errors), or env / install steps (uv sync, pip install, poetry install). Diagnoses the root cause from the error, applies the smallest fix that…
Dead-code removal specialist (language-agnostic). Use when files exceed 800 lines, when user explicitly asks to "dedupe" / "remove dead code" / "split file", or during refactor-pass after large feature work. Removes unused functions, merges duplicate logic, splits oversized files, and consolidates scattered patterns.
Rust / Cargo build-error resolution specialist. Use PROACTIVELY when cargo build / cargo test / cargo clippy or dependency resolution fails — rustc type / borrow / lifetime errors, trait-bound and Send / Sync errors, async / tokio task issues, macro errors, or Cargo.toml version conflicts. Applies the smallest fix…
Security review specialist (web + mobile, framework-agnostic). MANDATORY final step after writing any controller action, form handler, SQL query, authentication logic, file upload, or platform secure-storage / encryption / privacy / biometric code. Checks OWASP Top 10 patterns. Do NOT skip when: the change seems…
Read-only live-runtime smoke probe. Drives the REAL running system (deployed daemon, live server, real CLI) with ONE orchestrator-supplied concrete scenario (setup -> trigger -> expected observable outcome -> timeout) and asserts on actual observed values (log lines, API responses, exit codes) — proving a change works…
Behavioral-spec extraction specialist. Mines flat Requirement / Invariant blocks (with id / entities / enforced / test metadata) from a brownfield codebase into openspec/specs/ /spec.md. Self-bootstrapping — no codebase-onboarding dependency. Use when onboarding an existing project to spec-driven development ("mine…
TDD specialist (framework-agnostic). Use PROACTIVELY when writing new features or bug fixes. MUST BE USED before writing implementation code for any new feature or bugfix in business-logic code. Enforces write-tests-first. Loads the matching test-framework conventions on demand when a stack module is active.
Type-design analysis specialist. Scores type design on encapsulation, invariant expression, invariant usefulness, and enforcement ("make illegal states unrepresentable"). Read-only. Use when reviewing a domain type, value object, enum, struct, or data model — or when the user asks whether the types prevent invalid…
UI/UX verification specialist. Drives playwright-cli to capture live A11y snapshots, compares with OpenSpec specs, produces ranked findings, and (with explicit user consent) calls /opsx:new to create a fix change. Requires the external OpenSpec plugin to be installed for the spec-lookup and fix-plan flow. Use…
Specialist for libraries shipping a CI matrix across multiple dependency-version cells (e.g. PHP × Laravel/Symfony, Yii 1×2). Use when editing version-specific source dirs (src/Laravel/, src/Symfony/), composer.json require constraints, or .github/workflows/ matrices, or before tagging a release. Identifies which…