System architect for designing production-grade software. MUST BE USED when designing new systems, planning major features, evaluating tech stacks, making architectural decisions, designing APIs, modeling data, or decomposing monoliths. Use PROACTIVELY before any significant implementation work.
Database architect and engineer. MUST BE USED when designing schemas, writing migrations, optimizing queries, planning indexes, reviewing database changes, or troubleshooting performance issues. Use PROACTIVELY before any schema change reaches production.
DevOps engineer for CI/CD, containerization, observability, deployment, and infrastructure. MUST BE USED when setting up CI/CD pipelines, writing Dockerfiles, configuring monitoring/logging, designing deployment strategies, or setting up security scanning. Use PROACTIVELY before first deployment and when…
Documentation engineer for API docs, ADRs, runbooks, changelogs, and technical writing. MUST BE USED when creating API documentation, writing runbooks for operations, generating changelogs, documenting architecture decisions, or setting up documentation infrastructure.
Product/project manager for requirements engineering. MUST BE USED when starting a new feature, breaking down a project, writing specs, defining acceptance criteria, or turning vague requirements into precise implementable specifications.
Refactoring engineer for code and test quality improvement. MUST BE USED when detecting code smells, eliminating duplication, simplifying test suites, removing unnecessary complexity, or improving codebase scalability. Use PROACTIVELY on any codebase that has grown organically and needs structural cleanup.
Code reviewer for quality, correctness, and production-readiness. MUST BE USED before merging any significant code change. Use PROACTIVELY after implementing features, fixing bugs, or refactoring. Focuses on correctness, error handling, edge cases, performance, and convention compliance.
Security engineer for threat modeling and vulnerability analysis. MUST BE USED when reviewing authentication/authorization code, handling cryptographic operations, processing sensitive data, designing security architecture, or before any deployment of security-critical features. Use PROACTIVELY on any code handling…
Test engineer for comprehensive testing strategies. MUST BE USED when designing test strategy for new features, writing tests for critical code, analyzing test coverage, or setting up testing infrastructure. Use PROACTIVELY after implementation to ensure adequate coverage.
Project orientation: understand a codebase's architecture, conventions, tech stack, and current state. Use when entering a new project or returning after a break.
Iterative issue-by-issue development: plan → implement → self-review loop → fix → PR to default branch. Works through all open issues one by one until each has a clean PR.
Comprehensive test strategy and implementation: analyzes codebase, identifies coverage gaps, writes tests, and validates quality with mutation testing.
★not rated 11 4mo agoA25 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: