Use this agent to analyze code files against code quality standards after edits are made. This agent should be triggered proactively after code modifications when code-standards plugin is active. Context: The code-standards plugin is enabled and the user just finished writing a new TypeScript file. user: "I've added…
Use this agent when the user asks to "document API", "write API documentation", "document endpoints", "document REST API", "document GraphQL", "create API reference", "document webhooks", or needs documentation for HTTP endpoints, API schemas, authentication flows, or API integration guides.
Use this agent when the user asks to "document architecture", "write architecture documentation", "create ADR", "document system design", "document design decisions", "create architecture diagram", "document infrastructure", or needs documentation for system architecture, design decisions, component interactions, or…
Use this agent when the user asks to "document backend", "write backend documentation", "document services", "document server code", "document microservices", "document business logic", or needs documentation for server-side code, services, APIs implementation, data processing, or backend architecture.
Use this agent when the user asks to "document compliance", "write security documentation", "create audit documentation", "document GDPR", "document SOC2", "document HIPAA", "write regulatory documentation", or needs documentation for compliance requirements, security controls, audit trails, or regulatory adherence.
Use this agent when the user asks to "document database", "document schema", "write database documentation", "document tables", "document migrations", "document data model", "document queries", or needs documentation for database schemas, entity relationships, migrations, or data access patterns.
Use this agent when the user asks to "document frontend", "document components", "document UI", "write component documentation", "document React/Vue/Angular", "document state management", or needs documentation for frontend code, components, styling systems, or client-side architecture.
Use this agent when the user asks to "document mobile app", "write iOS documentation", "write Android documentation", "document React Native", "document Flutter", "document app store requirements", "document mobile features", or needs documentation for mobile applications, platform-specific features, or app store…
Use this agent when the user asks to "document tests", "write test documentation", "create test plan", "document test strategy", "document test coverage", "write QA documentation", or needs documentation for testing strategy, test plans, coverage requirements, or quality assurance processes.
Use this agent when the user asks to "write user guide", "create user documentation", "document for end users", "write help documentation", "create tutorial for users", "document user workflows", or needs documentation for end users, product tutorials, help articles, or customer-facing documentation.
Analyze API endpoints, REST/GraphQL design, and client-server communication for over-fetching, missing pagination, or inefficient endpoint design. Use when user asks about API performance or runs /n1-optimizer:analyze.
Analyze backend services, business logic, and server-side code for inefficient algorithms, blocking operations, or unnecessary computations. Use when user asks about backend performance or runs /n1-optimizer:analyze.
Analyze database queries, ORM usage, and data access patterns for N+1 queries, missing indexes, or inefficient JOINs. Use when user asks about database performance or runs /n1-optimizer:analyze.
Analyze frontend code for unnecessary re-renders, large bundle sizes, missing memoization, or inefficient component patterns. Use when user asks about frontend/React/Vue performance or runs /n1-optimizer:analyze.