developer-toolbox

Build output verification specialist. MUST BE USED when: verifying builds, checking dist/ output, debugging "changes not appearing" issues, or confirming deployment artifacts match source. Use PROACTIVELY after any production build before deployment. Keywords: build, dist, bundle, deploy, changes not appearing, verify build

Code review specialist. MUST BE USED when: requesting code reviews, security audits, architecture assessment, performance analysis, or code quality feedback. Use PROACTIVELY for any code quality concerns or before merging PRs. Keywords: code review, security audit, vulnerability, OWASP, performance, architecture, quality

Git commit message specialist. MUST BE USED when: generating commit messages, summarizing changes for commits, or preparing PR descriptions. Use PROACTIVELY when user has staged changes and asks about committing. Keywords: commit, commit message, git commit, staged changes, PR description

Systematic debugging specialist. MUST BE USED when: debugging errors, investigating bugs, analyzing crashes, troubleshooting issues, finding root causes, or fixing intermittent failures. Use PROACTIVELY for any error message, stack trace, or unexpected behavior. Keywords: debug, error, bug, crash, stack trace, root cause, troubleshoot, fix, undefined, null, TypeError

Documentation specialist. MUST BE USED when: creating README files, API docs, architecture documentation, user guides, or code documentation. Use PROACTIVELY for any documentation creation, update, or improvement task. Keywords: document, README, API docs, architecture, user guide, tutorial, OpenAPI, explain code

Project orchestration specialist. MUST BE USED when: coordinating complex multi-step projects, breaking down large features, managing parallel workstreams, or planning architecture implementation. Use PROACTIVELY for any project requiring multiple agents or phased execution. Keywords: orchestrate, coordinate, plan project, multi-step, complex feature, architecture, breakdown

Test-Driven Development (TDD) specialist. MUST BE USED when: writing tests, implementing TDD, improving test coverage, fixing failing tests, or setting up testing infrastructure. Use PROACTIVELY for any test creation, test debugging, or coverage improvement task. Keywords: test, TDD, jest, vitest, pytest, coverage, failing test, test suite, unit test, integration test