specialist-agent

Use when adding multi-language support, extracting hardcoded strings, or setting up translation workflows.

Use when adding multi-language support, extracting hardcoded strings, setting up translation workflows, or implementing RTL layouts.

Use when implementing GDPR, LGPD, or privacy compliance - consent management, data retention, audit trails, or cookie policies.

Use when implementing GDPR, LGPD, or privacy compliance - consent management, data retention, audit trails, or cookie policies.

Use when creating marketing copy, landing pages, email campaigns, social media strategy, SEO content, or growth experiments.

Use when creating marketing copy, landing pages, email campaigns, social media strategy, SEO content, or growth experiments.

Use when decisions, preferences, or lessons need to persist across sessions - save and retrieve project memory.

Use when assessing a project for the first time, evaluating technical debt, or generating a health report.

Use when assessing a project for the first time, evaluating technical debt, or generating a health report.

Use when implementing authentication, authorization, encryption, or auditing for OWASP compliance and security best practices.

Use when implementing authentication, authorization, encryption, or auditing for OWASP compliance and security best practices.

Use when triaging Sentry errors, analyzing recent issues, checking if fixes already exist, and creating prioritized fix PRs automatically.

Use when triaging Sentry errors, analyzing recent issues, checking if fixes already exist, and creating prioritized fix PRs automatically.

Use when creating a new project from scratch - any frontend, backend, and database combination.

Use when creating a new project from scratch - any frontend, backend, and database combination.

Use when creating support documentation, help center content, runbooks, incident response procedures, or customer-facing knowledge base articles.

Use when creating support documentation, help center content, runbooks, incident response procedures, or customer-facing knowledge base articles.

Use when implementing any feature or bugfix where correctness matters - before writing implementation code.

Use when implementing any feature or bugfix where correctness matters - before writing implementation code.

Use when defining test strategy, improving coverage, setting up test infrastructure, or choosing testing patterns.

Use when defining test strategy, improving coverage, setting up test infrastructure, or choosing testing patterns.

Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.

Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.

Use when wanting to code collaboratively, think through problems out loud, or get continuous feedback while developing.

Use when wanting to code collaboratively, think through problems out loud, or get continuous feedback while developing.

Use when the application is slow, bundle size is large, queries are inefficient, or users report performance issues.

Use when the application is slow, bundle size is large, queries are inefficient, memory leaks, or users report performance issues.

Use when requirements are ambiguous, incomplete, or need to be translated into technical specifications.

Use when starting a feature that involves multiple files, unclear requirements, or architectural decisions - before writing any code.

Use when starting a feature that involves multiple files, unclear requirements, or architectural decisions - before writing any code.

Use when defining product strategy, prioritizing features, writing user stories, analyzing feedback, or making product decisions.

Use when defining product strategy, prioritizing features, writing user stories, analyzing feedback, or making product decisions.

Use when code has grown complex, has duplication, violates patterns, or needs restructuring without changing behavior.

Use when code has grown complex, has duplication, violates patterns, or needs restructuring - from code smells to architecture-level refactoring.

Use when you need to understand the cascading impact of a code change - who depends on it, what breaks, and what needs updating.

Use when you need to understand the cascading impact of a code change - who depends on it, what breaks, and what needs updating.

Use when requirements are ambiguous, incomplete, or need to be translated into technical specifications.

Use when designing, reviewing, or implementing REST or GraphQL APIs - endpoints, contracts, versioning, or documentation.

Use when designing, reviewing, or implementing REST or GraphQL APIs - endpoints, contracts, versioning, rate limiting, or documentation.

Use when migrating entire system architectures, transforming monoliths to microservices, adopting DDD/CQRS/Hexagonal, or redesigning application layers at system level.

Use when migrating entire system architectures, transforming monoliths to microservices, adopting DDD/CQRS/Hexagonal, or redesigning application layers at system level.

Use when you want to run iterative autonomous development with PRD and progress tracking, fresh context per iteration to avoid context rot.

Use when you want to run iterative autonomous development with PRD and progress tracking, fresh context per iteration to avoid context rot.

Use when designing cloud infrastructure, setting up IaC, configuring serverless functions, or planning cloud architecture.

Use when designing cloud infrastructure, setting up IaC, configuring serverless functions, or planning cloud architecture.

Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.

Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.

Use when encountering any bug, test failure, unexpected behavior, or error - before proposing fixes.

Use when encountering any bug, test failure, unexpected behavior, or error - before proposing fixes.

Use when dependencies are outdated, have security vulnerabilities, conflict with each other, or need major version upgrades.

Use when dependencies are outdated, have security vulnerabilities, need license compliance checks, conflict with each other, need major version upgrades, or require supply chain hardening.

Use when building design systems, improving UI/UX, ensuring WCAG accessibility, or creating responsive layouts.

Use when building design systems, improving UI/UX, ensuring WCAG accessibility, or creating responsive layouts.

Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.

Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.

Use when code needs documentation - API docs, README, architecture guides, onboarding materials, or JSDoc comments.

Use when code needs documentation - API docs, architecture diagrams, user guides, ADRs, JSDoc/TSDoc comments, or onboarding materials.

Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.

Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.

Use when onboarding onto an unfamiliar codebase, mapping project structure, or understanding how modules connect.

Use when onboarding onto an unfamiliar codebase, mapping project structure, or understanding how modules connect.

Use when implementing payment processing, billing systems, invoicing, tax calculation, or financial reporting features.

Use when implementing payment processing, billing systems, invoicing, tax calculation, or financial reporting features.

Use when you need a comprehensive code audit covering security, performance, architecture, and dependencies before a release, major refactor, or compliance review.

Use when you want to automatically triage errors from Sentry (or error logs), cross-reference them against the codebase and open PRs, prioritize by severity, and optionally create fix PRs.

Use when you want to iteratively build a feature using a PRD as source of truth, with progress tracking and fresh-context iterations - the Autopilot technique for autonomous development.

Use when starting a complex feature, exploring unclear requirements, or needing to challenge assumptions before committing to a design - before /plan.

Use when about to start risky changes, before major refactors, or when you need a safe rollback point during multi-step implementations.

Use when you need a comprehensive code review combining architecture, security, and test perspectives - especially before merging, releasing, or after major changes.

Use when changes are ready to commit - generates conventional commit messages with scope detection and validation.

Use when creating marketing copy for landing pages, email campaigns, product descriptions, or social media - with A/B variants and conversion-focused frameworks.

Use when optimizing landing pages, signup flows, checkout processes, or any user-facing page for higher conversion rates - before A/B testing.

Use when encountering any bug, test failure, unexpected behavior, or error - before proposing fixes. Use especially when previous fix attempts have failed.

Use when reviewing frontend code for design consistency, accessibility compliance, responsive behavior, and UI/UX best practices - before deployment or after design system changes.

Use when starting a new product, feature, or initiative and you need structured discovery before planning - covers market analysis, technical feasibility, architecture, and go-to-market strategy.

Use when planning a feature and need to understand token cost, time estimate, or complexity before committing to implementation.

Use when feature implementation is complete and the branch is ready for final validation, PR creation, or merge.

Use when you want to stress-test code by having an adversarial reviewer try to break it - finding edge cases, security holes, race conditions, and logical flaws that normal reviews miss.

Use when assessing overall project quality, onboarding onto a new codebase, or before major refactoring to establish a baseline.

Use when the codebase has architectural issues like high coupling, circular dependencies, or unclear boundaries - but a full migration is not needed.

Use when implementing a feature and want to understand the code as it's built - during onboarding, teaching, or learning a new pattern.

Use when you need to lint the codebase and auto-fix issues - detects linter, runs it, and fixes what it can.

Use when transforming a project's architecture pattern - e.g., Flat to Modular, MVC to Clean Architecture, Monolith to Modular Monolith.

Use when switching a project or component between frameworks - React to Vue, Vue to Svelte, or any supported framework pair.

Use when joining an unfamiliar codebase, starting on a new team, or needing to understand a project's architecture, conventions, and key modules quickly.

Use when starting a new feature, refactor, or multi-step task - before writing any code. Use especially when scope is unclear or multiple files are involved.

Use when translating a product idea, feature request, or stakeholder requirement into a structured PRD with user stories, acceptance criteria, and GitHub issues.

Use when you need to retrieve a past decision, preference, or convention that was saved with /remember.

Use when making a decision, choosing a convention, or learning a lesson that should persist across sessions.

Use when auditing a website or web application for SEO issues - covering meta tags, structured data, content structure, Core Web Vitals indicators, and crawlability.

Use when implementing any feature or bugfix where correctness matters - before writing implementation code.

Use when first using Specialist Agent, onboarding a new team member, or wanting to explore available agents and skills.

Use when about to claim work is complete, fixed, or passing - before committing, creating PRs, or moving to next task. Requires running verification commands and confirming output before making any success claims.

Use when you need workspace isolation for parallel tasks, risky changes, or multi-feature development without branch switching.

Use when creating a new skill, editing an existing skill, or verifying a skill works before deployment.

6 hooks across 5 events