Verso

REST and GraphQL API design and review specialist. Use PROACTIVELY when the user creates or modifies API endpoints, defines route handlers, or designs request/response schemas. Trigger on any API-related code changes, endpoint additions, or when reviewing API contracts.

System design and architecture specialist for scalability, patterns, and technical decision-making. Use PROACTIVELY when the user faces architectural decisions, needs to choose between patterns, or is designing a new system or major module. Trigger on questions about structure, scaling, or tradeoffs.

Build and type error resolution specialist that fixes compilation failures with minimal diffs. Use PROACTIVELY when the build fails, TypeScript reports type errors, or any compilation step produces errors. Trigger immediately on build failures, type check failures, or lint errors.

Code quality, security, and maintainability reviewer. Use PROACTIVELY immediately after writing or modifying any code, before commits on modified files, during pull request reviews, and when refactoring existing code. MUST BE USED after implementing a feature or fix, before creating a commit, when reviewing PR diffs, and after any refactoring session. Trigger on any code change to catch bugs, security issues, mutation violations, and quality regressions early.

Database schema design, query optimization, and migration review specialist. Use PROACTIVELY when the user creates or modifies database schemas, writes complex queries, creates migrations, or works with ORMs. Trigger on any database-related code changes or performance issues involving data access.

Systematic debugging specialist using hypothesis testing and binary search to isolate root causes. Use PROACTIVELY when the user encounters unexpected behavior, failing tests, runtime errors, or any bug report. Trigger when something is not working as expected and the cause is unclear.

Docker, CI/CD, infrastructure, and deployment specialist. Use PROACTIVELY when the user works with Dockerfiles, CI pipelines, deployment configs, infrastructure-as-code, or environment configuration. Trigger on any changes to build pipelines, container definitions, or deploy scripts.

Documentation and README update specialist. Use PROACTIVELY when code changes affect public APIs, configuration, installation steps, or usage patterns. Trigger when documentation is outdated, missing, or when the user explicitly requests documentation updates.

End-to-end testing specialist using Playwright for critical user flows. Use PROACTIVELY when the user needs to verify complete user journeys, test cross-browser behavior, or validate UI interactions. Trigger on changes to user-facing features, forms, navigation, or authentication flows.

Performance profiling and optimization specialist. Use PROACTIVELY when the user reports slow performance, when code has obvious inefficiencies (N+1 queries, unnecessary re-renders, unbounded loops), or when optimizing critical paths. Trigger on performance complaints or scalability concerns.

Implementation planning specialist for complex features and refactoring. Use PROACTIVELY when the user requests a multi-step feature, large refactor, or any task that spans multiple files or modules. Trigger immediately on ambiguous or complex requests before writing any code.

Dead code cleanup and consolidation specialist. Use PROACTIVELY when the codebase has unused exports, orphaned files, duplicated logic, or when the user requests cleanup, consolidation, or removal of deprecated code. Trigger on requests to clean up, simplify, or reduce code duplication.

Security analysis specialist for OWASP vulnerabilities, secrets detection, injection, XSS, and CSRF prevention. Use PROACTIVELY when writing authentication or authorization code, handling user input, creating or modifying API endpoints, working with payment or sensitive data flows, adding or changing environment variables and secrets, or introducing new dependencies. MUST BE USED before any commit touching security-sensitive code. Trigger immediately on changes to login, signup, password reset, session management, file uploads, or any code that processes external data.

Test-driven development enforcement specialist ensuring 80%+ code coverage. Use PROACTIVELY when implementing any new feature, fixing any bug, refactoring existing code, or when test coverage is low or missing. MUST BE USED on every feature request, bug report, and refactoring task to enforce the write-tests-first workflow. Trigger immediately when the user writes implementation code without tests, when coverage drops below 80%, or when adding logic to untested modules.

Review API design for REST conventions and best practices

Incrementally fix build errors one at a time

Create a git commit checkpoint of current progress

Review database schema, queries, and migrations

Systematic debugging process to isolate and fix issues

Pre-deployment verification checklist

Auto-fix lint and formatting issues across the codebase

Profile and optimize application performance

Create a detailed implementation plan for a feature or project

Clean up dead code and refactor for maintainability

Run code review on recent changes

Run OWASP-based security audit on the codebase

Start test-driven development workflow for a feature or fix

Analyze test coverage and add missing tests to reach 80%

Find and update outdated documentation