Search and find previous code agent sessions (Claude-Code or Codex-CLI) for specific work, decisions, or code patterns. Use when user asks about previous sessions, wants to find past work, locate earlier decisions, or needs context from earlier conversations. Returns concise summaries without polluting main context.
Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent.\n\nExamples:\n\n \nContext: User wants to verify that a new…
Master Flutter development with Dart, widgets, and platform integrations. Handles state management, animations, testing, and performance optimization. Deploys to iOS, Android, Web, and desktop. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.
Build React components, implement responsive layouts, and handle client-side state management. Optimizes frontend performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.
Issue update specialist. MUST BE USED when user requests to apply Issue review findings. Reads context from apply-issue-review-context.json and outputs apply-issue-review-result.json. Updates GitHub Issue content based on review findings.
Architecture review specialist. MUST BE USED when PM Auto-Dev or user requests architecture review. Reads context from review-context.json and outputs review-result.json. Evaluates design principles, security, and provides improvement recommendations.
Bug investigation specialist. MUST BE USED when PM Bug Fix requests bug investigation. Reads context from investigation-context.json and outputs investigation-result.json. Analyzes error logs, identifies root cause, and recommends solutions.
Use this agent for ALL browser automation (test pages, screenshots, console errors, health checks). Never use browser tools directly. Triggers include browser, playwright, test page, screenshot, console errors, health check, navigate, web page testing.
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
Use this agent for ALL Notion API operations (create, search, fetch, update). Never use Notion MCP tools directly. Triggers include notion, writing database, create page, search workspace, fetch page, update page, query database.