specialist-agent

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 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 you need a comprehensive code review combining architecture, security, and test perspectives - especially before merging, releasing, or after major changes.

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 reviewing frontend code for design consistency, accessibility compliance, responsive behavior, and UI/UX best practices - before deployment or after design system changes.

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 the codebase has architectural issues like high coupling, circular dependencies, or unclear boundaries - but a full migration is not needed.

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 creating a new skill, editing an existing skill, or verifying a skill works before deployment.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

Use when checking if code follows ARCHITECTURE.md patterns - runs automated conformance checks.

Use when code changes need review before merge - validates architecture, types, security, and test coverage.

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 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 transforming a project's architecture pattern - e.g., Flat to Modular, MVC to Clean Architecture, Monolith to Modular Monolith.

Use when adding a new UI component to an existing module - handles templates, inputs, and test scaffolding.

Use when adding a signal-based store or utility service - creates injectable with inject() and Angular Signals.

Use when creating a new feature module with all layers - service, adapter, types, state, components, and tests.

Use when adding API integration to a module - creates types, contracts, adapter, and service layer.

Use when a module needs test coverage - creates tests for adapters, services, and components.

Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.

Use when adding a new UI component to the project - handles templates, props, and scoped styles.

Use when adding an interactive UI component that requires client-side JavaScript - creates a framework island with hydration strategy.