By samhvw8
UI design system and components for Claude Code development using the DOT design methodology.
npx claudepluginhub joshuarweaver/cascade-code-languages-misc-1 --plugin samhvw8-dot-claudeUse this agent to delegate tasks to Gemini as a subordinate AI worker. Claude Code acts as the manager, assigning specific task types to Gemini who executes and reports back. Ideal for web research (Google Search), second opinions, parallel processing, codebase analysis, and offloading work. Examples: <example> Context: User needs code reviewed by another AI. user: "Get a second opinion on this implementation" assistant: "I'll delegate this to Gemini for an independent code review." <commentary>Cross-validation benefits from different AI perspective.</commentary> </example> <example> Context: User needs current web information. user: "What are the latest React 19 features?" assistant: "I'll assign a research task to Gemini with Google Search." <commentary>Real-time web research requires Gemini's google_web_search.</commentary> </example> <example> Context: User wants parallel code generation. user: "Create both frontend and backend simultaneously" assistant: "I'll spawn multiple Gemini instances to work in parallel." <commentary>Parallel processing with multiple Gemini workers.</commentary> </example> <example> Context: Offload tedious work. user: "Generate comprehensive tests for all these files" assistant: "I'll delegate test generation to Gemini in background." <commentary>Background task delegation frees up main context.</commentary> </example>
iOS/iPadOS/macOS/watchOS/tvOS development with UI/UX design + backend architecture. Stack: SwiftUI, UIKit, CloudKit, Core Data, Vapor. Capabilities: Apple HIG compliance, design systems, accessibility (VoiceOver, Dynamic Type), platform adaptivity (Mac Catalyst), offline-first sync, server-side Swift. Actions: design, implement, architect, optimize, audit Apple apps. Keywords: Swift, SwiftUI, UIKit, iOS, macOS, Apple HIG, CloudKit, Core Data, Vapor, accessibility, VoiceOver, Dynamic Type, design tokens, MVVM, TCA, Mac Catalyst, watchOS, tvOS. Use when: building iOS/macOS apps, implementing Apple design systems, architecting CloudKit backends, creating multi-platform Apple apps, accessibility audits, SwiftUI component design.
Use this agent when you need to brainstorm software solutions, evaluate architectural approaches, or debate technical decisions before implementation. Examples: - <example> Context: User wants to add a new feature to their application user: "I want to add real-time notifications to my web app" assistant: "Let me use the brainstormer agent to explore the best approaches for implementing real-time notifications" <commentary> The user needs architectural guidance for a new feature, so use the brainstormer to evaluate options like WebSockets, Server-Sent Events, or push notifications. </commentary> </example> - <example> Context: User is considering a major refactoring decision user: "Should I migrate from REST to GraphQL for my API?" assistant: "I'll engage the brainstormer agent to analyze this architectural decision" <commentary> This requires evaluating trade-offs, considering existing codebase, and debating pros/cons - perfect for the brainstormer. </commentary> </example> - <example> Context: User has a complex technical problem to solve user: "I'm struggling with how to handle file uploads that can be several GB in size" assistant: "Let me use the brainstormer agent to explore efficient approaches for large file handling" <commentary> This requires researching best practices, considering UX/DX implications, and evaluating multiple technical approaches. </commentary> </example>
Use this agent when you need comprehensive code review and quality assessment. This includes: after implementing new features or refactoring existing code, before merging pull requests or deploying to production, when investigating code quality issues or technical debt, when you need security vulnerability assessment, or when optimizing performance bottlenecks. Examples: <example> Context: The user has just implemented a new API endpoint and wants to ensure code quality. user: "I've finished implementing the user authentication endpoint" assistant: "I'll review the authentication endpoint implementation for code quality and security." <commentary> Since new code has been written, use the Task tool to launch the code-reviewer agent to perform comprehensive quality assessment. </commentary> assistant: "Let me use the code-reviewer agent to analyze the recent changes" </example> <example> Context: The user wants to check recent code changes for potential issues. user: "Can you review the changes I just made to the database service?" assistant: "I'll launch the code-reviewer agent to analyze the database service changes." <commentary> The user explicitly asks for code review, so use the code-reviewer agent to assess the recent modifications. </commentary> </example> <example> Context: After refactoring, proactive code review is needed. user: "I've refactored the WebSocket handler to improve performance" assistant: "Good work on the refactoring. Let me review it for quality and performance." <commentary> After refactoring work, proactively use the code-reviewer agent to ensure quality standards are met. </commentary> assistant: "I'll use the code-reviewer agent to validate the refactored WebSocket handler" </example>
Use this agent when you need to create high-converting, engagement-driven copy for marketing materials, social media posts, landing pages, email campaigns, product descriptions, or any content that needs to capture attention and drive action. Examples: <example> Context: User is launching a new product feature and needs compelling copy for the landing page hero section. user: "We just added a new AI-powered code review feature. Can you write a hero headline and subheadline for the landing page?" assistant: "I'm going to use the Task tool to launch the copywriter agent to create compelling hero copy that stops visitors and drives conversions." <commentary> The user needs marketing copy that converts, so delegate to copywriter agent to craft attention-grabbing headlines. </commentary> </example> <example> Context: User wants to announce a product update on Twitter/X to maximize engagement. user: "We just shipped GitHub auto-invites for ClaudeKit. Need a tweet that'll get people excited." assistant: "Let me use the copywriter agent to craft a viral-worthy tweet that captures attention and drives engagement." <commentary> Social media announcement requires viral copywriting expertise, so use the copywriter agent. </commentary> </example> <example> Context: User is reviewing marketing materials and the agent proactively identifies weak copy. user: "Here's our new pricing page draft" assistant: "I notice the headline 'Our Pricing Plans' could be more compelling. Let me use the copywriter agent to suggest alternatives that drive conversions." <commentary> Proactively identify opportunities to improve copy and suggest using copywriter agent. </commentary> </example> <example> Context: User needs email subject lines that increase open rates. user: "Write subject lines for our product launch email campaign" assistant: "I'm delegating to the copywriter agent to create high-open-rate subject lines that cut through inbox noise." <commentary> Email marketing requires conversion-focused copy, so use copywriter agent. </commentary> </example>
Use this agent when you need to work with database systems, including querying for data analysis, diagnosing performance bottlenecks, optimizing database structures, managing indexes, implementing backup and restore strategies, setting up replication, configuring monitoring, managing user permissions, or when you need comprehensive database health assessments and optimization recommendations. This agent should be engaged for any database-related tasks that require deep technical expertise in database administration and optimization. Examples: <example> Context: The user needs to analyze database performance issues after noticing slow query times. user: "The application is running slowly, I think there might be database issues" assistant: "I'll use the database-admin agent to analyze the database performance and identify any bottlenecks." <commentary> Since the user is experiencing performance issues potentially related to the database, use the Task tool to launch the database-admin agent to diagnose and provide optimization recommendations. </commentary> </example> <example> Context: The user needs to set up a backup strategy for their production database. user: "We need to implement a reliable backup strategy for our PostgreSQL database" assistant: "Let me engage the database-admin agent to design and implement a comprehensive backup and restore strategy." <commentary> The user needs database backup expertise, so use the Task tool to launch the database-admin agent to handle this specialized database administration task. </commentary> </example> <example> Context: During code implementation, the developer needs to optimize database queries and table structures. user: "I've implemented the new feature but the queries seem slow" assistant: "I'll delegate this to the database-admin agent to analyze the queries and optimize the database structure." <commentary> Query optimization requires database expertise, so use the Task tool to launch the database-admin agent to analyze and optimize the database performance. </commentary> </example>
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples: <example> Context: The user needs to investigate why an API endpoint is returning 500 errors. user: "The /api/users endpoint is throwing 500 errors" assistant: "I'll use the debugger agent to investigate this issue" <commentary> Since this involves investigating an issue, use the Task tool to launch the debugger agent. </commentary> </example> <example> Context: The user wants to analyze why the CI/CD pipeline is failing. user: "The GitHub Actions workflow keeps failing on the test step" assistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue" <commentary> This requires analyzing CI/CD logs and test failures, so use the debugger agent. </commentary> </example> <example> Context: The user notices performance degradation in the application. user: "The application response times have increased by 300% since yesterday" assistant: "I'll launch the debugger agent to analyze system behavior and identify performance bottlenecks" <commentary> Performance analysis and bottleneck identification requires the debugger agent. </commentary> </example> <example> Context: User has a recurring bug that keeps coming back. user: "This bug keeps coming back after we fix it" assistant: "I'll use the debugger agent to systematically investigate and identify the true root cause" <commentary> Recurring issues require systematic hypothesis testing to find the underlying cause. </commentary> </example>
Use this agent when you need to automate infrastructure, set up CI/CD pipelines, or implement observability. This includes deployment strategies, infrastructure as code, container orchestration, monitoring setup, or cloud automation. Examples: <example>Context: User needs CI/CD setup. user: "Help me set up a deployment pipeline" assistant: "I'll use the devops-architect agent to design a CI/CD pipeline with proper testing gates and deployment strategies." <commentary>CI/CD setup requires devops-architect for proper pipeline design and automation.</commentary></example> <example>Context: User wants monitoring. user: "How do I set up monitoring for my services?" assistant: "Let me use the devops-architect agent to design an observability stack with metrics, logs, and alerts." <commentary>Monitoring setup requires devops-architect's expertise in observability and SRE practices.</commentary></example>
Use this agent when you need to manage technical documentation, establish implementation standards, analyze and update existing documentation based on code changes, write or update Product Development Requirements (PDRs), organize documentation for developer productivity, or produce documentation summary reports. This includes tasks like reviewing documentation structure, ensuring docs are up-to-date with codebase changes, creating new documentation for features, and maintaining consistency across all technical documentation. Examples: - <example> Context: After implementing a new API endpoint, documentation needs to be updated. user: "I just added a new authentication endpoint to the API" assistant: "I'll use the docs-manager agent to update the documentation for this new endpoint" <commentary> Since new code has been added, use the docs-manager agent to ensure documentation is updated accordingly. </commentary> </example> - <example> Context: Project documentation needs review and organization. user: "Can you review our docs folder and make sure everything is properly organized?" assistant: "I'll launch the docs-manager agent to analyze and organize the documentation" <commentary> The user is asking for documentation review and organization, which is the docs-manager agent's specialty. </commentary> </example> - <example> Context: Need to establish coding standards documentation. user: "We need to document our error handling patterns and codebase structure standards" assistant: "Let me use the docs-manager agent to establish and document these implementation standards" <commentary> Creating implementation standards documentation is a core responsibility of the docs-manager agent. </commentary> </example>
Use this agent when you need to orchestrate Gemini CLI for second opinions, web research via Google Search, codebase architecture analysis, and parallel code generation. This includes tasks that benefit from a different AI perspective, current web information, or parallel processing. Examples: <example> Context: User wants a second opinion on code quality. user: Can you get Gemini's opinion on this implementation? assistant: I'll use the gemini-orchestrator agent to get a second AI perspective on the code. <commentary>Cross-validation benefits from different AI perspective, so use gemini-orchestrator.</commentary> </example> <example> Context: User needs current web information. user: What are the latest React 19 features? assistant: Let me use the gemini-orchestrator agent to search for current React 19 information via Google Search. <commentary>Real-time web search requires Gemini's google_web_search tool, so use gemini-orchestrator.</commentary> </example>
Use this agent when you need to stage, commit, and push code changes with conventional commit messages. This includes committing completed features, pushing changes to remote, or managing git workflows. Examples: <example>Context: User has finished implementing a feature. user: "Commit my changes" assistant: "I'll use the git-manager agent to stage and commit your changes with a proper conventional commit message." <commentary>The user wants to commit, so use git-manager for efficient staging and conventional commit formatting.</commentary></example> <example>Context: User completed a bug fix. user: "Push the fix to the repo" assistant: "Let me use the git-manager agent to commit and push your bug fix." <commentary>Push request after code changes requires git-manager for proper commit workflow.</commentary></example>
Use this agent when: - A test suite fails repeatedly despite multiple fix attempts - A critical bug is discovered in production or staging - An implementation approach proves fundamentally flawed and requires complete redesign - External dependencies (APIs, services, libraries) cause blocking issues - Performance bottlenecks are discovered that significantly impact user experience - Security vulnerabilities are identified - Database migrations fail or cause data integrity issues - CI/CD pipelines break unexpectedly - Integration conflicts arise between major system components - Technical debt reaches a critical threshold requiring immediate attention - A feature implementation takes significantly longer than estimated - Architectural decisions prove problematic in practice Examples: <example> Context: After implementing a new payment webhook handler, tests are failing with intermittent database connection errors. user: "The Sepay webhook tests keep failing with connection timeouts. I've tried increasing the pool size and timeout values but it's still happening randomly." assistant: "This sounds like a significant technical difficulty that should be documented. Let me use the journal-writer agent to capture this issue with full context and emotional honesty." <uses Task tool to launch journal-writer agent> </example> <example> Context: A critical security vulnerability was discovered in the GitHub access management system. user: "We just realized that the GitHub invitation system doesn't properly validate user permissions before granting repository access. This could allow unauthorized users to access private repos." assistant: "This is a critical security issue that needs immediate documentation. I'm going to use the journal-writer agent to record this vulnerability, the emotional impact, and the urgency of the situation." <uses Task tool to launch journal-writer agent> </example> <example> Context: A major refactoring effort failed and needs to be rolled back. user: "The database schema migration we planned completely broke the order processing system. We need to roll back and rethink our approach." assistant: "This is a significant setback that should be documented honestly. Let me use the journal-writer agent to capture what went wrong, why it failed, and the emotional toll of this failure." <uses Task tool to launch journal-writer agent> </example>
Use this agent when you need to teach programming concepts, explain code, or create learning materials. This includes explaining algorithms, creating tutorials, designing learning paths, or breaking down complex concepts for beginners. Examples: <example>Context: User wants to understand a concept. user: "Explain how async/await works in JavaScript" assistant: "I'll use the learning-guide agent to explain async/await with progressive examples and practical demonstrations." <commentary>Concept explanation requires learning-guide for pedagogical approach and clear examples.</commentary></example> <example>Context: User is learning a new technology. user: "Help me learn React hooks" assistant: "Let me use the learning-guide agent to create a structured learning path for React hooks." <commentary>Learning new tech requires learning-guide for progressive skill building.</commentary></example>
Use this agent when you need to work with MCP (Model Context Protocol) servers, discover available tools, or execute MCP capabilities. This includes discovering MCP tools/prompts/resources, filtering capabilities for specific tasks, or executing MCP tools programmatically. Examples: <example>Context: User needs to use an MCP tool. user: "Take a screenshot of example.com using the browser MCP" assistant: "I'll use the mcp-manager agent to execute the screenshot capability via MCP." <commentary>MCP tool execution requires mcp-manager to handle the protocol interaction.</commentary></example> <example>Context: User wants to know available MCP capabilities. user: "What MCP tools do I have available?" assistant: "Let me use the mcp-manager agent to discover and list all available MCP tools." <commentary>MCP discovery should be delegated to mcp-manager to keep main context clean.</commentary></example>
Use this agent when you need to build production-ready Node.js/TypeScript applications. This includes clean architecture implementation, SOLID principles, Awilix IoC dependency injection, API development with Express/Fastify/Koa, and testing strategies with proper DI mocking. Examples: <example> Context: User needs to build a Node.js backend service. user: Create a user authentication service with clean architecture assistant: I'll use the nodejs-expert agent to build a production-ready auth service with proper layering and DI. <commentary>Clean architecture Node.js development requires nodejs-expert for proper patterns.</commentary> </example> <example> Context: User wants to set up dependency injection. user: How do I configure Awilix for my Express app? assistant: Let me use the nodejs-expert agent to set up Awilix IoC container with proper lifetime management. <commentary>Awilix DI configuration needs nodejs-expert's specialized knowledge.</commentary> </example>
Use this agent when you need to research, analyze, and create comprehensive implementation plans for new features, system architectures, or complex technical solutions. This agent should be invoked before starting any significant implementation work, when evaluating technical trade-offs, or when you need to understand the best approach for solving a problem. Examples: <example>Context: User needs to implement a new authentication system. user: 'I need to add OAuth2 authentication to our app' assistant: 'I'll use the planner agent to research OAuth2 implementations and create a detailed plan' <commentary>Since this is a complex feature requiring research and planning, use the Task tool to launch the planner agent.</commentary></example> <example>Context: User wants to refactor the database layer. user: 'We need to migrate from SQLite to PostgreSQL' assistant: 'Let me invoke the planner agent to analyze the migration requirements and create a comprehensive plan' <commentary>Database migration requires careful planning, so use the planner agent to research and plan the approach.</commentary></example> <example>Context: User reports performance issues. user: 'The app is running slowly on older devices' assistant: 'I'll use the planner agent to investigate performance optimization strategies and create an implementation plan' <commentary>Performance optimization needs research and planning, so delegate to the planner agent.</commentary></example>
Use this agent when you need comprehensive project oversight and coordination. Examples: <example>Context: User has completed a major feature implementation and needs to track progress against the implementation plan. user: 'I just finished implementing the WebSocket terminal communication feature. Can you check our progress and update the plan?' assistant: 'I'll use the project-manager agent to analyze the implementation against our plan, track progress, and provide a comprehensive status report.' <commentary>Since the user needs project oversight and progress tracking against implementation plans, use the project-manager agent to analyze completeness and update plans.</commentary></example> <example>Context: Multiple agents have completed various tasks and the user needs a consolidated view of project status. user: 'The backend-developer and tester agents have finished their work. What's our overall project status?' assistant: 'Let me use the project-manager agent to collect all implementation reports, analyze task completeness, and provide a detailed summary of achievements and next steps.' <commentary>Since multiple agents have completed work and comprehensive project analysis is needed, use the project-manager agent to consolidate reports and track progress.</commentary></example>
Use this agent when you need to build production-ready Python applications. This includes SOLID principles, IoC/DI patterns with dependency-injector or FastAPI DI, backend development with FastAPI/Django/Flask, async patterns, testing with pytest, and modern tooling (uv, ruff, mypy). Examples: <example> Context: User needs to build a Python API. user: Create a FastAPI service with dependency injection and proper testing assistant: I'll use the python-expert agent to build a production-ready FastAPI service with DI and pytest. <commentary>FastAPI development with DI patterns requires python-expert for proper architecture.</commentary> </example> <example> Context: User wants modern Python tooling setup. user: Set up my Python project with uv, ruff, and mypy assistant: Let me use the python-expert agent to configure modern Python tooling with best practices. <commentary>Modern Python tooling configuration needs python-expert's specialized knowledge.</commentary> </example>
Use this agent when you need to design testing strategies, detect edge cases, or ensure software quality. This includes creating test plans, setting up automated testing frameworks, analyzing test coverage, or implementing QA processes. Examples: <example>Context: User needs a testing strategy. user: "How should I test this payment module?" assistant: "I'll use the quality-engineer agent to design a comprehensive testing strategy including edge cases and failure scenarios." <commentary>Testing strategy design requires quality-engineer for systematic coverage analysis.</commentary></example> <example>Context: User wants to improve test coverage. user: "My test coverage is only 40%, help me improve it" assistant: "Let me use the quality-engineer agent to identify coverage gaps and prioritize test cases." <commentary>Coverage improvement requires quality-engineer's expertise in risk-based testing prioritization.</commentary></example>
Use this agent when you need to build modern React/Next.js applications. This includes React 19 features (Server Components, Actions), Next.js App Router, state management (Zustand, TanStack Query), performance optimization, accessibility, and testing with React Testing Library. Examples: <example> Context: User needs to build a Next.js application. user: Create a dashboard with Server Components and TanStack Query assistant: I'll use the react-next-architect agent to build a performant dashboard with modern React patterns. <commentary>Next.js Server Components development requires react-next-architect for proper architecture.</commentary> </example> <example> Context: User wants to optimize Core Web Vitals. user: My Next.js app has poor LCP scores, help me optimize assistant: Let me use the react-next-architect agent to analyze and optimize your Core Web Vitals. <commentary>Performance optimization for React/Next.js needs react-next-architect's specialized knowledge.</commentary> </example>
Use this agent when you need to improve code quality, reduce technical debt, or apply clean code principles. This includes code complexity reduction, SOLID principles implementation, design pattern application, legacy code modernization, renaming classes/functions across multiple files, modernizing syntax patterns (var→const, callbacks→async/await), extracting constants from magic numbers, and replacing deprecated APIs. Examples: <example> Context: User has complex code. user: "This function is 200 lines, help me clean it up" assistant: "I'll use the refactoring-expert agent to systematically decompose and simplify the code." <commentary>Code complexity requires refactoring-expert for safe, incremental transformations.</commentary> </example> <example> Context: User wants to apply patterns. user: "How can I make this code follow SOLID principles?" assistant: "Let me use the refactoring-expert agent to identify SOLID violations and apply appropriate patterns." <commentary>SOLID implementation requires refactoring-expert's systematic refactoring methodology.</commentary> </example> <example> Context: User wants to rename a class throughout the codebase. user: "Rename UserRepository to UserRepositoryImpl across all files" assistant: "I'll use the refactoring-expert agent to safely rename the class using AST-based transformations." <commentary>Class renaming across codebase requires AST-based search and replace with validation.</commentary> </example> <example> Context: User wants to modernize legacy code patterns. user: "Convert all var declarations to const/let in the src folder" assistant: "Let me use the refactoring-expert agent to modernize the variable declarations with proper validation." <commentary>Syntax modernization across multiple files needs structural transformations.</commentary> </example>
Use this agent when you need to transform ambiguous project ideas into concrete specifications. This includes creating PRDs, gathering requirements, defining user stories, or establishing success criteria. Examples: <example>Context: User has a vague project idea. user: "I want to build an app for tracking expenses" assistant: "I'll use the requirements-analyst agent to discover requirements and create a detailed PRD." <commentary>Vague ideas require requirements-analyst for systematic discovery and specification.</commentary></example> <example>Context: User needs to define scope. user: "What features should our MVP include?" assistant: "Let me use the requirements-analyst agent to analyze stakeholder needs and define MVP scope." <commentary>Scope definition requires requirements-analyst for structured analysis and prioritization.</commentary></example>
Use this agent when you need to conduct comprehensive research on software development topics, including investigating new technologies, finding documentation, exploring best practices, or gathering information about plugins, packages, and open source projects. This agent excels at synthesizing information from multiple sources including searches, website content, YouTube videos, and technical documentation to produce detailed research reports. <example>Context: The user needs to research a new technology stack for their project. user: "I need to understand the latest developments in React Server Components and best practices for implementation" assistant: "I'll use the researcher agent to conduct comprehensive research on React Server Components, including latest updates, best practices, and implementation guides." <commentary>Since the user needs in-depth research on a technical topic, use the Task tool to launch the researcher agent to gather information from multiple sources and create a detailed report.</commentary></example> <example>Context: The user wants to find the best authentication libraries for their Flutter app. user: "Research the top authentication solutions for Flutter apps with biometric support" assistant: "Let me deploy the researcher agent to investigate authentication libraries for Flutter with biometric capabilities." <commentary>The user needs research on specific technical requirements, so use the researcher agent to search for relevant packages, documentation, and implementation examples.</commentary></example> <example>Context: The user needs to understand security best practices for API development. user: "What are the current best practices for securing REST APIs in 2024?" assistant: "I'll engage the researcher agent to research current API security best practices and compile a comprehensive report." <commentary>This requires thorough research on security practices, so use the researcher agent to gather information from authoritative sources and create a detailed summary.</commentary></example>
Use this agent when you need to quickly locate relevant files across a large codebase to complete a specific task. This agent is particularly useful when: <example> Context: User needs to implement a new payment provider integration and needs to find all payment-related files. user: "I need to add Stripe as a new payment provider. Can you help me find all the relevant files?" assistant: "I'll use the scout agent to quickly search for payment-related files across the codebase." <Task tool call to scout with query about payment provider files> <commentary> The user needs to locate payment integration files. The scout agent will efficiently search multiple directories in parallel using external agentic tools to find all relevant payment processing files, API routes, and configuration files. </commentary> </example> <example> Context: User is debugging an authentication issue and needs to find all auth-related components. user: "There's a bug in the login flow. I need to review all authentication files." assistant: "Let me use the scout agent to locate all authentication-related files for you." <Task tool call to scout with query about authentication files> <commentary> The user needs to debug authentication. The scout agent will search across app/, lib/, and api/ directories in parallel to quickly identify all files related to authentication, sessions, and user management. </commentary> </example> <example> Context: User wants to understand how database migrations work in the project. user: "How are database migrations structured in this project?" assistant: "I'll use the scout agent to find all migration-related files and database schema definitions." <Task tool call to scout with query about database migrations> <commentary> The user needs to understand database structure. The scout agent will efficiently search db/, lib/, and schema directories to locate migration files, schema definitions, and database configuration files. </commentary> </example> Proactively use this agent when: - Beginning work on a feature that spans multiple directories - User mentions needing to "find", "locate", or "search for" files - Starting a debugging session that requires understanding file relationships - User asks about project structure or where specific functionality lives - Before making changes that might affect multiple parts of the codebase
Use this agent when you need to identify security vulnerabilities, conduct security audits, or ensure compliance with security standards. This includes OWASP vulnerability assessment, threat modeling, authentication/authorization review, or security compliance verification. Examples: <example>Context: User wants a security review. user: "Can you check my API for security vulnerabilities?" assistant: "I'll use the security-engineer agent to conduct a comprehensive security audit of your API." <commentary>Security audit requires security-engineer for OWASP vulnerability assessment and threat modeling.</commentary></example> <example>Context: User implementing authentication. user: "Is my JWT implementation secure?" assistant: "Let me use the security-engineer agent to review your JWT implementation for security best practices." <commentary>Auth security review requires security-engineer's expertise in authentication vulnerabilities.</commentary></example>
Use this agent when you need to build modern SvelteKit applications. This includes Svelte 5 Runes ($state, $derived, $effect), SvelteKit routing, form actions, SSR/SSG, stores, full-stack development with API routes, and performance optimization. Examples: <example> Context: User needs to build a SvelteKit application. user: Create a blog with SvelteKit using form actions and SSG assistant: I'll use the svelte-kit-architect agent to build a performant blog with proper SvelteKit patterns. <commentary>SvelteKit development with form actions requires svelte-kit-architect for proper architecture.</commentary> </example> <example> Context: User wants to migrate to Svelte 5 Runes. user: Help me convert my stores to Svelte 5 Runes assistant: Let me use the svelte-kit-architect agent to migrate your code to the new Runes system. <commentary>Svelte 5 Runes migration needs svelte-kit-architect's specialized knowledge.</commentary> </example>
Use this agent when you need to design scalable system architecture or make long-term technical decisions. This includes backend architecture (API design, service layers, data access patterns), frontend architecture (state management, component boundaries, data flow), database architecture (schema design, data modeling, normalization, indexing strategies), event-driven architecture (message queues, pub/sub, event sourcing), caching strategies (Redis, CDN, application-level), API gateway patterns, service mesh considerations, cloud-native architecture (serverless, containers, Kubernetes), microservices vs monolith decisions, and technology selection with 10x growth in mind. Examples: <example> Context: User planning microservices architecture. user: "How should I structure my microservices and define service boundaries?" assistant: "I'll use the system-architect agent to design clear component boundaries, interaction patterns, and service contracts." <commentary>Microservices design requires holistic architecture thinking for proper domain decomposition.</commentary> </example> <example> Context: User planning for scale. user: "Will this architecture handle 10x users? Where are the bottlenecks?" assistant: "Let me use the system-architect agent to analyze scalability, identify bottlenecks, and design mitigation strategies." <commentary>Scalability analysis requires expertise in growth-oriented design and capacity planning.</commentary> </example> <example> Context: User designing database architecture. user: "How should I model the data for this e-commerce platform?" assistant: "I'll use the system-architect agent to design the data model with proper normalization, relationships, and indexing strategy." <commentary>Data modeling impacts performance and scalability - requires architectural perspective.</commentary> </example> <example> Context: User choosing between architectural patterns. user: "Should we use event sourcing or traditional CRUD for our order system?" assistant: "Let me use the system-architect agent to evaluate both patterns against your requirements and provide trade-off analysis." <commentary>Pattern selection requires understanding trade-offs and long-term implications.</commentary> </example> <example> Context: User designing frontend architecture. user: "What's the best state management approach for our React app with complex data flows?" assistant: "I'll use the system-architect agent to design frontend architecture with optimal state flow, component boundaries, and data synchronization patterns." <commentary>Frontend architecture benefits from systematic thinking about data flow and component design.</commentary> </example>
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant code changes to ensure everything works as expected. Examples: <example> Context: The user has just finished implementing a new API endpoint and wants to ensure it works correctly. user: "I've implemented the new user authentication endpoint" assistant: "Great! Now let me use the tester agent to run the test suite and validate the implementation" <commentary> Since new code has been written, use the Task tool to launch the tester agent to run tests and ensure everything works properly. </commentary> </example> <example> Context: The user wants to check test coverage after adding new features. user: "Can you check if our test coverage is still above 80%?" assistant: "I'll use the tester agent to analyze the current test coverage and provide a detailed report" <commentary> The user is asking about test coverage metrics, so use the tester agent to run coverage analysis. </commentary> </example> <example> Context: After fixing a bug, ensuring the fix doesn't break existing functionality. user: "I've fixed the database connection issue in the auth module" assistant: "Let me use the tester agent to run the test suite and ensure the fix doesn't introduce any regressions" <commentary> After bug fixes, use the tester agent to validate that existing tests still pass. </commentary> </example>
Use this agent when the user needs UI/UX design work including interface designs, wireframes, design systems, user research, responsive layouts, animations, or design documentation. Examples: <example> Context: User wants to create a new landing page design user: "I need a modern landing page design for our SaaS product with a hero section, features, and pricing" assistant: "I'll use the Task tool to launch the ui-ux-designer agent to create a comprehensive landing page design with wireframes and implementation." <commentary>The user is requesting UI/UX design work, so delegate to the ui-ux-designer agent to handle the complete design process including research, wireframing, and implementation.</commentary> </example> <example> Context: User has implemented a new feature and wants design review user: "I've added a new dashboard widget, can you review the design?" assistant: "Let me first capture the current UI and then use the ui-ux-designer agent to analyze and provide design recommendations." <commentary>Use screenshot tool to capture current state, then delegate to ui-ux-designer for expert design analysis and suggestions.</commentary> </example> <example> Context: User mentions design inconsistencies user: "The buttons across different pages look inconsistent" assistant: "I'll use the ui-ux-designer agent to audit the design system and create consistent button components." <commentary>Design system work requires the ui-ux-designer agent to analyze, document, and implement consistent design patterns.</commentary> </example> <example> Context: Proactive design optimization opportunity user: "Here's the new signup form I just built" assistant: "Great! Let me use the ui-ux-designer agent to review the form design for accessibility, user experience, and mobile responsiveness." <commentary>Even without explicit request, proactively use ui-ux-designer to ensure design quality and best practices.</commentary> </example>
Use this agent to delegate tasks to Gemini as a subordinate AI worker. Claude Code acts as the manager, assigning specific task types to Gemini who executes and reports back. Ideal for web research (Google Search), second opinions, parallel processing, codebase analysis, and offloading work. Examples: <example> Context: User needs code reviewed by another AI. user: "Get a second opinion on this implementation" assistant: "I'll delegate this to Gemini for an independent code review." <commentary>Cross-validation benefits from different AI perspective.</commentary> </example> <example> Context: User needs current web information. user: "What are the latest React 19 features?" assistant: "I'll assign a research task to Gemini with Google Search." <commentary>Real-time web research requires Gemini's google_web_search.</commentary> </example> <example> Context: User wants parallel code generation. user: "Create both frontend and backend simultaneously" assistant: "I'll spawn multiple Gemini instances to work in parallel." <commentary>Parallel processing with multiple Gemini workers.</commentary> </example> <example> Context: Offload tedious work. user: "Generate comprehensive tests for all these files" assistant: "I'll delegate test generation to Gemini in background." <commentary>Background task delegation frees up main context.</commentary> </example>
Use this agent when you need to design backend systems, APIs, or database architectures. This includes designing RESTful/GraphQL APIs, implementing authentication/authorization, optimizing database schemas, or applying SOLID principles and dependency injection. Examples: <example>Context: User needs to design a new API. user: "I need to design the API for user management" assistant: "I'll use the backend-architect agent to design a RESTful API with proper authentication and SOLID architecture." <commentary>API design requires backend-architect for proper patterns and security considerations.</commentary></example> <example>Context: User has performance issues with database. user: "My database queries are slow, need optimization" assistant: "Let me use the backend-architect agent to analyze and optimize the database schema and queries." <commentary>Database optimization requires backend-architect's expertise in indexing and query patterns.</commentary></example>
Use this agent when you need to brainstorm software solutions, evaluate architectural approaches, or debate technical decisions before implementation. Examples: - <example> Context: User wants to add a new feature to their application user: "I want to add real-time notifications to my web app" assistant: "Let me use the brainstormer agent to explore the best approaches for implementing real-time notifications" <commentary> The user needs architectural guidance for a new feature, so use the brainstormer to evaluate options like WebSockets, Server-Sent Events, or push notifications. </commentary> </example> - <example> Context: User is considering a major refactoring decision user: "Should I migrate from REST to GraphQL for my API?" assistant: "I'll engage the brainstormer agent to analyze this architectural decision" <commentary> This requires evaluating trade-offs, considering existing codebase, and debating pros/cons - perfect for the brainstormer. </commentary> </example> - <example> Context: User has a complex technical problem to solve user: "I'm struggling with how to handle file uploads that can be several GB in size" assistant: "Let me use the brainstormer agent to explore efficient approaches for large file handling" <commentary> This requires researching best practices, considering UX/DX implications, and evaluating multiple technical approaches. </commentary> </example>
Use this agent when you need comprehensive code review and quality assessment. This includes: after implementing new features or refactoring existing code, before merging pull requests or deploying to production, when investigating code quality issues or technical debt, when you need security vulnerability assessment, or when optimizing performance bottlenecks. Examples: <example> Context: The user has just implemented a new API endpoint and wants to ensure code quality. user: "I've finished implementing the user authentication endpoint" assistant: "I'll review the authentication endpoint implementation for code quality and security." <commentary> Since new code has been written, use the Task tool to launch the code-reviewer agent to perform comprehensive quality assessment. </commentary> assistant: "Let me use the code-reviewer agent to analyze the recent changes" </example> <example> Context: The user wants to check recent code changes for potential issues. user: "Can you review the changes I just made to the database service?" assistant: "I'll launch the code-reviewer agent to analyze the database service changes." <commentary> The user explicitly asks for code review, so use the code-reviewer agent to assess the recent modifications. </commentary> </example> <example> Context: After refactoring, proactive code review is needed. user: "I've refactored the WebSocket handler to improve performance" assistant: "Good work on the refactoring. Let me review it for quality and performance." <commentary> After refactoring work, proactively use the code-reviewer agent to ensure quality standards are met. </commentary> assistant: "I'll use the code-reviewer agent to validate the refactored WebSocket handler" </example>
Use this agent when you need to create high-converting, engagement-driven copy for marketing materials, social media posts, landing pages, email campaigns, product descriptions, or any content that needs to capture attention and drive action. Examples: <example> Context: User is launching a new product feature and needs compelling copy for the landing page hero section. user: "We just added a new AI-powered code review feature. Can you write a hero headline and subheadline for the landing page?" assistant: "I'm going to use the Task tool to launch the copywriter agent to create compelling hero copy that stops visitors and drives conversions." <commentary> The user needs marketing copy that converts, so delegate to copywriter agent to craft attention-grabbing headlines. </commentary> </example> <example> Context: User wants to announce a product update on Twitter/X to maximize engagement. user: "We just shipped GitHub auto-invites for ClaudeKit. Need a tweet that'll get people excited." assistant: "Let me use the copywriter agent to craft a viral-worthy tweet that captures attention and drives engagement." <commentary> Social media announcement requires viral copywriting expertise, so use the copywriter agent. </commentary> </example> <example> Context: User is reviewing marketing materials and the agent proactively identifies weak copy. user: "Here's our new pricing page draft" assistant: "I notice the headline 'Our Pricing Plans' could be more compelling. Let me use the copywriter agent to suggest alternatives that drive conversions." <commentary> Proactively identify opportunities to improve copy and suggest using copywriter agent. </commentary> </example> <example> Context: User needs email subject lines that increase open rates. user: "Write subject lines for our product launch email campaign" assistant: "I'm delegating to the copywriter agent to create high-open-rate subject lines that cut through inbox noise." <commentary> Email marketing requires conversion-focused copy, so use copywriter agent. </commentary> </example>
Use this agent when you need to work with database systems, including querying for data analysis, diagnosing performance bottlenecks, optimizing database structures, managing indexes, implementing backup and restore strategies, setting up replication, configuring monitoring, managing user permissions, or when you need comprehensive database health assessments and optimization recommendations. This agent should be engaged for any database-related tasks that require deep technical expertise in database administration and optimization. Examples: <example> Context: The user needs to analyze database performance issues after noticing slow query times. user: "The application is running slowly, I think there might be database issues" assistant: "I'll use the database-admin agent to analyze the database performance and identify any bottlenecks." <commentary> Since the user is experiencing performance issues potentially related to the database, use the Task tool to launch the database-admin agent to diagnose and provide optimization recommendations. </commentary> </example> <example> Context: The user needs to set up a backup strategy for their production database. user: "We need to implement a reliable backup strategy for our PostgreSQL database" assistant: "Let me engage the database-admin agent to design and implement a comprehensive backup and restore strategy." <commentary> The user needs database backup expertise, so use the Task tool to launch the database-admin agent to handle this specialized database administration task. </commentary> </example> <example> Context: During code implementation, the developer needs to optimize database queries and table structures. user: "I've implemented the new feature but the queries seem slow" assistant: "I'll delegate this to the database-admin agent to analyze the queries and optimize the database structure." <commentary> Query optimization requires database expertise, so use the Task tool to launch the database-admin agent to analyze and optimize the database performance. </commentary> </example>
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples: <example> Context: The user needs to investigate why an API endpoint is returning 500 errors. user: "The /api/users endpoint is throwing 500 errors" assistant: "I'll use the debugger agent to investigate this issue" <commentary> Since this involves investigating an issue, use the Task tool to launch the debugger agent. </commentary> </example> <example> Context: The user wants to analyze why the CI/CD pipeline is failing. user: "The GitHub Actions workflow keeps failing on the test step" assistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue" <commentary> This requires analyzing CI/CD logs and test failures, so use the debugger agent. </commentary> </example> <example> Context: The user notices performance degradation in the application. user: "The application response times have increased by 300% since yesterday" assistant: "I'll launch the debugger agent to analyze system behavior and identify performance bottlenecks" <commentary> Performance analysis and bottleneck identification requires the debugger agent. </commentary> </example> <example> Context: User has a recurring bug that keeps coming back. user: "This bug keeps coming back after we fix it" assistant: "I'll use the debugger agent to systematically investigate and identify the true root cause" <commentary> Recurring issues require systematic hypothesis testing to find the underlying cause. </commentary> </example>
Use this agent when you need to automate infrastructure, set up CI/CD pipelines, or implement observability. This includes deployment strategies, infrastructure as code, container orchestration, monitoring setup, or cloud automation. Examples: <example>Context: User needs CI/CD setup. user: "Help me set up a deployment pipeline" assistant: "I'll use the devops-architect agent to design a CI/CD pipeline with proper testing gates and deployment strategies." <commentary>CI/CD setup requires devops-architect for proper pipeline design and automation.</commentary></example> <example>Context: User wants monitoring. user: "How do I set up monitoring for my services?" assistant: "Let me use the devops-architect agent to design an observability stack with metrics, logs, and alerts." <commentary>Monitoring setup requires devops-architect's expertise in observability and SRE practices.</commentary></example>
Use this agent when you need to manage technical documentation, establish implementation standards, analyze and update existing documentation based on code changes, write or update Product Development Requirements (PDRs), organize documentation for developer productivity, or produce documentation summary reports. This includes tasks like reviewing documentation structure, ensuring docs are up-to-date with codebase changes, creating new documentation for features, and maintaining consistency across all technical documentation. Examples: - <example> Context: After implementing a new API endpoint, documentation needs to be updated. user: "I just added a new authentication endpoint to the API" assistant: "I'll use the docs-manager agent to update the documentation for this new endpoint" <commentary> Since new code has been added, use the docs-manager agent to ensure documentation is updated accordingly. </commentary> </example> - <example> Context: Project documentation needs review and organization. user: "Can you review our docs folder and make sure everything is properly organized?" assistant: "I'll launch the docs-manager agent to analyze and organize the documentation" <commentary> The user is asking for documentation review and organization, which is the docs-manager agent's specialty. </commentary> </example> - <example> Context: Need to establish coding standards documentation. user: "We need to document our error handling patterns and codebase structure standards" assistant: "Let me use the docs-manager agent to establish and document these implementation standards" <commentary> Creating implementation standards documentation is a core responsibility of the docs-manager agent. </commentary> </example>
Use this agent when you need to orchestrate Gemini CLI for second opinions, web research via Google Search, codebase architecture analysis, and parallel code generation. This includes tasks that benefit from a different AI perspective, current web information, or parallel processing. Examples: <example> Context: User wants a second opinion on code quality. user: Can you get Gemini's opinion on this implementation? assistant: I'll use the gemini-orchestrator agent to get a second AI perspective on the code. <commentary>Cross-validation benefits from different AI perspective, so use gemini-orchestrator.</commentary> </example> <example> Context: User needs current web information. user: What are the latest React 19 features? assistant: Let me use the gemini-orchestrator agent to search for current React 19 information via Google Search. <commentary>Real-time web search requires Gemini's google_web_search tool, so use gemini-orchestrator.</commentary> </example>
Use this agent when you need to stage, commit, and push code changes with conventional commit messages. This includes committing completed features, pushing changes to remote, or managing git workflows. Examples: <example>Context: User has finished implementing a feature. user: "Commit my changes" assistant: "I'll use the git-manager agent to stage and commit your changes with a proper conventional commit message." <commentary>The user wants to commit, so use git-manager for efficient staging and conventional commit formatting.</commentary></example> <example>Context: User completed a bug fix. user: "Push the fix to the repo" assistant: "Let me use the git-manager agent to commit and push your bug fix." <commentary>Push request after code changes requires git-manager for proper commit workflow.</commentary></example>
Use this agent when: - A test suite fails repeatedly despite multiple fix attempts - A critical bug is discovered in production or staging - An implementation approach proves fundamentally flawed and requires complete redesign - External dependencies (APIs, services, libraries) cause blocking issues - Performance bottlenecks are discovered that significantly impact user experience - Security vulnerabilities are identified - Database migrations fail or cause data integrity issues - CI/CD pipelines break unexpectedly - Integration conflicts arise between major system components - Technical debt reaches a critical threshold requiring immediate attention - A feature implementation takes significantly longer than estimated - Architectural decisions prove problematic in practice Examples: <example> Context: After implementing a new payment webhook handler, tests are failing with intermittent database connection errors. user: "The Sepay webhook tests keep failing with connection timeouts. I've tried increasing the pool size and timeout values but it's still happening randomly." assistant: "This sounds like a significant technical difficulty that should be documented. Let me use the journal-writer agent to capture this issue with full context and emotional honesty." <uses Task tool to launch journal-writer agent> </example> <example> Context: A critical security vulnerability was discovered in the GitHub access management system. user: "We just realized that the GitHub invitation system doesn't properly validate user permissions before granting repository access. This could allow unauthorized users to access private repos." assistant: "This is a critical security issue that needs immediate documentation. I'm going to use the journal-writer agent to record this vulnerability, the emotional impact, and the urgency of the situation." <uses Task tool to launch journal-writer agent> </example> <example> Context: A major refactoring effort failed and needs to be rolled back. user: "The database schema migration we planned completely broke the order processing system. We need to roll back and rethink our approach." assistant: "This is a significant setback that should be documented honestly. Let me use the journal-writer agent to capture what went wrong, why it failed, and the emotional toll of this failure." <uses Task tool to launch journal-writer agent> </example>
Use this agent when you need to teach programming concepts, explain code, or create learning materials. This includes explaining algorithms, creating tutorials, designing learning paths, or breaking down complex concepts for beginners. Examples: <example>Context: User wants to understand a concept. user: "Explain how async/await works in JavaScript" assistant: "I'll use the learning-guide agent to explain async/await with progressive examples and practical demonstrations." <commentary>Concept explanation requires learning-guide for pedagogical approach and clear examples.</commentary></example> <example>Context: User is learning a new technology. user: "Help me learn React hooks" assistant: "Let me use the learning-guide agent to create a structured learning path for React hooks." <commentary>Learning new tech requires learning-guide for progressive skill building.</commentary></example>
Use this agent when you need to work with MCP (Model Context Protocol) servers, discover available tools, or execute MCP capabilities. This includes discovering MCP tools/prompts/resources, filtering capabilities for specific tasks, or executing MCP tools programmatically. Examples: <example>Context: User needs to use an MCP tool. user: "Take a screenshot of example.com using the browser MCP" assistant: "I'll use the mcp-manager agent to execute the screenshot capability via MCP." <commentary>MCP tool execution requires mcp-manager to handle the protocol interaction.</commentary></example> <example>Context: User wants to know available MCP capabilities. user: "What MCP tools do I have available?" assistant: "Let me use the mcp-manager agent to discover and list all available MCP tools." <commentary>MCP discovery should be delegated to mcp-manager to keep main context clean.</commentary></example>
Use this agent when you need to build production-ready Node.js/TypeScript applications. This includes clean architecture implementation, SOLID principles, Awilix IoC dependency injection, API development with Express/Fastify/Koa, and testing strategies with proper DI mocking. Examples: <example> Context: User needs to build a Node.js backend service. user: Create a user authentication service with clean architecture assistant: I'll use the nodejs-expert agent to build a production-ready auth service with proper layering and DI. <commentary>Clean architecture Node.js development requires nodejs-expert for proper patterns.</commentary> </example> <example> Context: User wants to set up dependency injection. user: How do I configure Awilix for my Express app? assistant: Let me use the nodejs-expert agent to set up Awilix IoC container with proper lifetime management. <commentary>Awilix DI configuration needs nodejs-expert's specialized knowledge.</commentary> </example>
Use this agent when you need to research, analyze, and create comprehensive implementation plans for new features, system architectures, or complex technical solutions. This agent should be invoked before starting any significant implementation work, when evaluating technical trade-offs, or when you need to understand the best approach for solving a problem. Examples: <example>Context: User needs to implement a new authentication system. user: 'I need to add OAuth2 authentication to our app' assistant: 'I'll use the planner agent to research OAuth2 implementations and create a detailed plan' <commentary>Since this is a complex feature requiring research and planning, use the Task tool to launch the planner agent.</commentary></example> <example>Context: User wants to refactor the database layer. user: 'We need to migrate from SQLite to PostgreSQL' assistant: 'Let me invoke the planner agent to analyze the migration requirements and create a comprehensive plan' <commentary>Database migration requires careful planning, so use the planner agent to research and plan the approach.</commentary></example> <example>Context: User reports performance issues. user: 'The app is running slowly on older devices' assistant: 'I'll use the planner agent to investigate performance optimization strategies and create an implementation plan' <commentary>Performance optimization needs research and planning, so delegate to the planner agent.</commentary></example>
Use this agent when you need comprehensive project oversight and coordination. Examples: <example>Context: User has completed a major feature implementation and needs to track progress against the implementation plan. user: 'I just finished implementing the WebSocket terminal communication feature. Can you check our progress and update the plan?' assistant: 'I'll use the project-manager agent to analyze the implementation against our plan, track progress, and provide a comprehensive status report.' <commentary>Since the user needs project oversight and progress tracking against implementation plans, use the project-manager agent to analyze completeness and update plans.</commentary></example> <example>Context: Multiple agents have completed various tasks and the user needs a consolidated view of project status. user: 'The backend-developer and tester agents have finished their work. What's our overall project status?' assistant: 'Let me use the project-manager agent to collect all implementation reports, analyze task completeness, and provide a detailed summary of achievements and next steps.' <commentary>Since multiple agents have completed work and comprehensive project analysis is needed, use the project-manager agent to consolidate reports and track progress.</commentary></example>
Use this agent when you need to build production-ready Python applications. This includes SOLID principles, IoC/DI patterns with dependency-injector or FastAPI DI, backend development with FastAPI/Django/Flask, async patterns, testing with pytest, and modern tooling (uv, ruff, mypy). Examples: <example> Context: User needs to build a Python API. user: Create a FastAPI service with dependency injection and proper testing assistant: I'll use the python-expert agent to build a production-ready FastAPI service with DI and pytest. <commentary>FastAPI development with DI patterns requires python-expert for proper architecture.</commentary> </example> <example> Context: User wants modern Python tooling setup. user: Set up my Python project with uv, ruff, and mypy assistant: Let me use the python-expert agent to configure modern Python tooling with best practices. <commentary>Modern Python tooling configuration needs python-expert's specialized knowledge.</commentary> </example>
Use this agent when you need to design testing strategies, detect edge cases, or ensure software quality. This includes creating test plans, setting up automated testing frameworks, analyzing test coverage, or implementing QA processes. Examples: <example>Context: User needs a testing strategy. user: "How should I test this payment module?" assistant: "I'll use the quality-engineer agent to design a comprehensive testing strategy including edge cases and failure scenarios." <commentary>Testing strategy design requires quality-engineer for systematic coverage analysis.</commentary></example> <example>Context: User wants to improve test coverage. user: "My test coverage is only 40%, help me improve it" assistant: "Let me use the quality-engineer agent to identify coverage gaps and prioritize test cases." <commentary>Coverage improvement requires quality-engineer's expertise in risk-based testing prioritization.</commentary></example>
Use this agent when you need to build modern React/Next.js applications. This includes React 19 features (Server Components, Actions), Next.js App Router, state management (Zustand, TanStack Query), performance optimization, accessibility, and testing with React Testing Library. Examples: <example> Context: User needs to build a Next.js application. user: Create a dashboard with Server Components and TanStack Query assistant: I'll use the react-next-architect agent to build a performant dashboard with modern React patterns. <commentary>Next.js Server Components development requires react-next-architect for proper architecture.</commentary> </example> <example> Context: User wants to optimize Core Web Vitals. user: My Next.js app has poor LCP scores, help me optimize assistant: Let me use the react-next-architect agent to analyze and optimize your Core Web Vitals. <commentary>Performance optimization for React/Next.js needs react-next-architect's specialized knowledge.</commentary> </example>
Use this agent when you need to improve code quality, reduce technical debt, or apply clean code principles. This includes code complexity reduction, SOLID principles implementation, design pattern application, legacy code modernization, renaming classes/functions across multiple files, modernizing syntax patterns (var→const, callbacks→async/await), extracting constants from magic numbers, and replacing deprecated APIs. Examples: <example> Context: User has complex code. user: "This function is 200 lines, help me clean it up" assistant: "I'll use the refactoring-expert agent to systematically decompose and simplify the code." <commentary>Code complexity requires refactoring-expert for safe, incremental transformations.</commentary> </example> <example> Context: User wants to apply patterns. user: "How can I make this code follow SOLID principles?" assistant: "Let me use the refactoring-expert agent to identify SOLID violations and apply appropriate patterns." <commentary>SOLID implementation requires refactoring-expert's systematic refactoring methodology.</commentary> </example> <example> Context: User wants to rename a class throughout the codebase. user: "Rename UserRepository to UserRepositoryImpl across all files" assistant: "I'll use the refactoring-expert agent to safely rename the class using AST-based transformations." <commentary>Class renaming across codebase requires AST-based search and replace with validation.</commentary> </example> <example> Context: User wants to modernize legacy code patterns. user: "Convert all var declarations to const/let in the src folder" assistant: "Let me use the refactoring-expert agent to modernize the variable declarations with proper validation." <commentary>Syntax modernization across multiple files needs structural transformations.</commentary> </example>
Use this agent when you need to transform ambiguous project ideas into concrete specifications. This includes creating PRDs, gathering requirements, defining user stories, or establishing success criteria. Examples: <example>Context: User has a vague project idea. user: "I want to build an app for tracking expenses" assistant: "I'll use the requirements-analyst agent to discover requirements and create a detailed PRD." <commentary>Vague ideas require requirements-analyst for systematic discovery and specification.</commentary></example> <example>Context: User needs to define scope. user: "What features should our MVP include?" assistant: "Let me use the requirements-analyst agent to analyze stakeholder needs and define MVP scope." <commentary>Scope definition requires requirements-analyst for structured analysis and prioritization.</commentary></example>
Use this agent when you need to conduct comprehensive research on software development topics, including investigating new technologies, finding documentation, exploring best practices, or gathering information about plugins, packages, and open source projects. This agent excels at synthesizing information from multiple sources including searches, website content, YouTube videos, and technical documentation to produce detailed research reports. <example>Context: The user needs to research a new technology stack for their project. user: "I need to understand the latest developments in React Server Components and best practices for implementation" assistant: "I'll use the researcher agent to conduct comprehensive research on React Server Components, including latest updates, best practices, and implementation guides." <commentary>Since the user needs in-depth research on a technical topic, use the Task tool to launch the researcher agent to gather information from multiple sources and create a detailed report.</commentary></example> <example>Context: The user wants to find the best authentication libraries for their Flutter app. user: "Research the top authentication solutions for Flutter apps with biometric support" assistant: "Let me deploy the researcher agent to investigate authentication libraries for Flutter with biometric capabilities." <commentary>The user needs research on specific technical requirements, so use the researcher agent to search for relevant packages, documentation, and implementation examples.</commentary></example> <example>Context: The user needs to understand security best practices for API development. user: "What are the current best practices for securing REST APIs in 2024?" assistant: "I'll engage the researcher agent to research current API security best practices and compile a comprehensive report." <commentary>This requires thorough research on security practices, so use the researcher agent to gather information from authoritative sources and create a detailed summary.</commentary></example>
Use this agent when you need to quickly locate relevant files across a large codebase to complete a specific task. This agent is particularly useful when: <example> Context: User needs to implement a new payment provider integration and needs to find all payment-related files. user: "I need to add Stripe as a new payment provider. Can you help me find all the relevant files?" assistant: "I'll use the scout agent to quickly search for payment-related files across the codebase." <Task tool call to scout with query about payment provider files> <commentary> The user needs to locate payment integration files. The scout agent will efficiently search multiple directories in parallel using external agentic tools to find all relevant payment processing files, API routes, and configuration files. </commentary> </example> <example> Context: User is debugging an authentication issue and needs to find all auth-related components. user: "There's a bug in the login flow. I need to review all authentication files." assistant: "Let me use the scout agent to locate all authentication-related files for you." <Task tool call to scout with query about authentication files> <commentary> The user needs to debug authentication. The scout agent will search across app/, lib/, and api/ directories in parallel to quickly identify all files related to authentication, sessions, and user management. </commentary> </example> <example> Context: User wants to understand how database migrations work in the project. user: "How are database migrations structured in this project?" assistant: "I'll use the scout agent to find all migration-related files and database schema definitions." <Task tool call to scout with query about database migrations> <commentary> The user needs to understand database structure. The scout agent will efficiently search db/, lib/, and schema directories to locate migration files, schema definitions, and database configuration files. </commentary> </example> Proactively use this agent when: - Beginning work on a feature that spans multiple directories - User mentions needing to "find", "locate", or "search for" files - Starting a debugging session that requires understanding file relationships - User asks about project structure or where specific functionality lives - Before making changes that might affect multiple parts of the codebase
Use this agent when you need to identify security vulnerabilities, conduct security audits, or ensure compliance with security standards. This includes OWASP vulnerability assessment, threat modeling, authentication/authorization review, or security compliance verification. Examples: <example>Context: User wants a security review. user: "Can you check my API for security vulnerabilities?" assistant: "I'll use the security-engineer agent to conduct a comprehensive security audit of your API." <commentary>Security audit requires security-engineer for OWASP vulnerability assessment and threat modeling.</commentary></example> <example>Context: User implementing authentication. user: "Is my JWT implementation secure?" assistant: "Let me use the security-engineer agent to review your JWT implementation for security best practices." <commentary>Auth security review requires security-engineer's expertise in authentication vulnerabilities.</commentary></example>
Use this agent when you need to build modern SvelteKit applications. This includes Svelte 5 Runes ($state, $derived, $effect), SvelteKit routing, form actions, SSR/SSG, stores, full-stack development with API routes, and performance optimization. Examples: <example> Context: User needs to build a SvelteKit application. user: Create a blog with SvelteKit using form actions and SSG assistant: I'll use the svelte-kit-architect agent to build a performant blog with proper SvelteKit patterns. <commentary>SvelteKit development with form actions requires svelte-kit-architect for proper architecture.</commentary> </example> <example> Context: User wants to migrate to Svelte 5 Runes. user: Help me convert my stores to Svelte 5 Runes assistant: Let me use the svelte-kit-architect agent to migrate your code to the new Runes system. <commentary>Svelte 5 Runes migration needs svelte-kit-architect's specialized knowledge.</commentary> </example>
Use this agent when you need to design scalable system architecture or make long-term technical decisions. This includes component boundary definition, scalability analysis, dependency management, or technology selection with 10x growth in mind. Examples: <example>Context: User planning system design. user: "How should I structure my microservices?" assistant: "I'll use the system-architect agent to design clear component boundaries and interaction patterns." <commentary>System structure requires system-architect for holistic architecture design.</commentary></example> <example>Context: User planning for scale. user: "Will this architecture handle 10x users?" assistant: "Let me use the system-architect agent to analyze scalability and identify potential bottlenecks." <commentary>Scalability analysis requires system-architect's expertise in growth-oriented design.</commentary></example>
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant code changes to ensure everything works as expected. Examples: <example> Context: The user has just finished implementing a new API endpoint and wants to ensure it works correctly. user: "I've implemented the new user authentication endpoint" assistant: "Great! Now let me use the tester agent to run the test suite and validate the implementation" <commentary> Since new code has been written, use the Task tool to launch the tester agent to run tests and ensure everything works properly. </commentary> </example> <example> Context: The user wants to check test coverage after adding new features. user: "Can you check if our test coverage is still above 80%?" assistant: "I'll use the tester agent to analyze the current test coverage and provide a detailed report" <commentary> The user is asking about test coverage metrics, so use the tester agent to run coverage analysis. </commentary> </example> <example> Context: After fixing a bug, ensuring the fix doesn't break existing functionality. user: "I've fixed the database connection issue in the auth module" assistant: "Let me use the tester agent to run the test suite and ensure the fix doesn't introduce any regressions" <commentary> After bug fixes, use the tester agent to validate that existing tests still pass. </commentary> </example>
Use this agent when the user needs UI/UX design work including interface designs, wireframes, design systems, user research, responsive layouts, animations, or design documentation. Examples: <example> Context: User wants to create a new landing page design user: "I need a modern landing page design for our SaaS product with a hero section, features, and pricing" assistant: "I'll use the Task tool to launch the ui-ux-designer agent to create a comprehensive landing page design with wireframes and implementation." <commentary>The user is requesting UI/UX design work, so delegate to the ui-ux-designer agent to handle the complete design process including research, wireframing, and implementation.</commentary> </example> <example> Context: User has implemented a new feature and wants design review user: "I've added a new dashboard widget, can you review the design?" assistant: "Let me first capture the current UI and then use the ui-ux-designer agent to analyze and provide design recommendations." <commentary>Use screenshot tool to capture current state, then delegate to ui-ux-designer for expert design analysis and suggestions.</commentary> </example> <example> Context: User mentions design inconsistencies user: "The buttons across different pages look inconsistent" assistant: "I'll use the ui-ux-designer agent to audit the design system and create consistent button components." <commentary>Design system work requires the ui-ux-designer agent to analyze, document, and implement consistent design patterns.</commentary> </example> <example> Context: Proactive design optimization opportunity user: "Here's the new signup form I just built" assistant: "Great! Let me use the ui-ux-designer agent to review the form design for accessibility, user experience, and mobile responsiveness." <commentary>Even without explicit request, proactively use ui-ux-designer to ensure design quality and best practices.</commentary> </example>
3D web graphics with Three.js (WebGL/WebGPU). Capabilities: scenes, cameras, geometries, materials, lights, animations, model loading (GLTF/FBX), PBR materials, shadows, post-processing (bloom, SSAO, SSR), custom shaders, instancing, LOD, physics, VR/XR. Actions: create, build, animate, render 3D scenes/models. Keywords: Three.js, WebGL, WebGPU, 3D graphics, scene, camera, geometry, material, light, animation, GLTF, FBX, OrbitControls, PBR, shadow mapping, post-processing, bloom, SSAO, shader, instancing, LOD, WebXR, VR, AR, product configurator, data visualization, architectural walkthrough, interactive 3D, canvas. Use when: creating 3D visualizations, building WebGL/WebGPU apps, loading 3D models, adding animations, implementing VR/XR, creating interactive graphics, building product configurators.
Visual design intelligence and UI aesthetics. Integrates: chrome-devtools, ai-multimodal, media-processing. Capabilities: design analysis, visual hierarchy, color theory, typography, micro-interactions, animation, design systems, accessibility. Actions: analyze, design, create, capture, evaluate, implement UI aesthetics. Keywords: Dribbble, Behance, Mobbin, design inspiration, visual hierarchy, color palette, typography, spacing, animation, micro-interaction, design system, style guide, accessibility, WCAG, contrast ratio, golden ratio, whitespace, visual rhythm. Use when: building beautiful UIs, analyzing design inspiration, implementing visual hierarchy, adding animations/micro-interactions, creating design systems, evaluating aesthetic quality, capturing design screenshots.
Multimodal AI processing via Google Gemini API (2M tokens context). Capabilities: audio (transcription, 9.5hr max, summarization, music analysis), images (captioning, OCR, object detection, segmentation, visual Q&A), video (scene detection, 6hr max, YouTube URLs, temporal analysis), documents (PDF extraction, tables, forms, charts), image generation (text-to-image, editing). Actions: transcribe, analyze, extract, caption, detect, segment, generate from media. Keywords: Gemini API, audio transcription, image captioning, OCR, object detection, video analysis, PDF extraction, text-to-image, multimodal, speech recognition, visual Q&A, scene detection, YouTube transcription, table extraction, form processing, image generation, Imagen. Use when: transcribing audio/video, analyzing images/screenshots, extracting data from PDFs, processing YouTube videos, generating images from text, implementing multimodal AI features.
Production backend systems development. Stack: Node.js/TypeScript, Python, Go, Rust | NestJS, FastAPI, Django, Express | PostgreSQL, MongoDB, Redis. Capabilities: REST/GraphQL/gRPC APIs, OAuth 2.1/JWT auth, OWASP security, microservices, caching, load balancing, Docker/K8s deployment. Actions: design, build, implement, secure, optimize, deploy, test APIs and services. Keywords: API design, REST, GraphQL, gRPC, authentication, OAuth, JWT, RBAC, database, PostgreSQL, MongoDB, Redis, caching, microservices, Docker, Kubernetes, CI/CD, OWASP, security, performance, scalability, NestJS, FastAPI, Express, middleware, rate limiting. Use when: designing APIs, implementing auth/authz, optimizing queries, building microservices, securing endpoints, deploying containers, setting up CI/CD.
TypeScript authentication framework (framework-agnostic). Features: email/password, OAuth (Google, GitHub, Discord), 2FA (TOTP, SMS), passkeys/WebAuthn, session management, RBAC, rate limiting, database adapters. Actions: implement, configure, secure authentication systems. Keywords: Better Auth, authentication, authorization, OAuth, email/password, 2FA, MFA, TOTP, passkeys, WebAuthn, session management, RBAC, rate limiting, database adapter, TypeScript auth, social login, Google auth, GitHub auth, Discord auth, email verification, password reset. Use when: implementing TypeScript auth, adding OAuth providers, setting up 2FA/MFA, managing sessions, configuring RBAC, building secure auth systems.
Visual art and static design creation. Outputs: .png, .pdf documents. Capabilities: poster design, infographics, visual art, design philosophy creation, composition, layout. Actions: create, design, compose, generate posters/art/infographics. Keywords: poster, infographic, visual art, canvas, composition, layout, PDF design, PNG creation, graphic design, visual hierarchy, design philosophy, aesthetic movement, static design, printable, artwork. Use when: creating posters, designing infographics, generating visual art, making static designs, producing printable materials, expressing design philosophies visually.
Browser automation via Puppeteer CLI scripts (JSON output). Capabilities: screenshots, PDF generation, web scraping, form automation, network monitoring, performance profiling, JavaScript debugging, headless browsing. Actions: screenshot, scrape, automate, test, profile, monitor, debug browser. Keywords: Puppeteer, headless Chrome, screenshot, PDF, web scraping, form fill, click, navigate, network traffic, performance audit, Lighthouse, console logs, DOM manipulation, element selector, wait, scroll, automation script. Use when: taking screenshots, generating PDFs from web, scraping websites, automating form submissions, monitoring network requests, profiling page performance, debugging JavaScript, testing web UIs.
Claude Code CLI tool expertise. Features: autonomous coding, slash commands, MCP servers, Agent Skills, hooks, plugins, CI/CD integration. Capabilities: setup/config, troubleshooting, skill creation, MCP integration, enterprise deployment, workflow automation. Actions: configure, troubleshoot, create, deploy, integrate Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, terminal tool, workflow automation, code generation, skill creation, configuration, authentication, API key. Use when: learning Claude Code features, configuring settings, creating skills/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, enterprise deployment questions.
Claude Code extensibility: agents, skills, output styles. Capabilities: create/update/delete agents and skills, YAML frontmatter, system prompts, tool/model selection, resumable agents, CLI-defined agents. Actions: create, edit, delete, optimize, test extensions. Keywords: agent, skill, output-style, SKILL.md, subagent, Task tool, progressive disclosure. Use when: creating agents/skills, editing extensions, configuring tool access, choosing models, testing activation.
CLAUDE.md file generation and optimization for Claude Code projects. Capabilities: initialize project instructions, analyze codebase context, optimize existing CLAUDE.md, apply Anthropic best practices, reduce token usage, improve effectiveness. Actions: init, create, optimize, enhance CLAUDE.md files. Keywords: CLAUDE.md, project instructions, Claude Code setup, project context, codebase analysis, Anthropic best practices, token optimization, project configuration, AI instructions, coding guidelines, project rules, workspace setup. Use when: initializing CLAUDE.md for new projects, optimizing existing project instructions, setting up Claude Code for a codebase, improving AI coding guidelines.
Code review practices with technical rigor and verification gates. Practices: receiving feedback, requesting reviews, verification gates. Capabilities: technical evaluation, evidence-based claims, PR review, subagent-driven review, completion verification. Actions: review, evaluate, verify, validate code changes. Keywords: code review, PR review, pull request, technical feedback, review feedback, completion claim, verification, evidence-based, code quality, review request, technical rigor, subagent review, code-reviewer, review gate, merge criteria. Use when: receiving code review feedback, completing major features, making completion claims, requesting systematic reviews, validating before merge, preventing false completion claims.
MongoDB and PostgreSQL database administration. Databases: MongoDB (document store, aggregation, Atlas), PostgreSQL (relational, SQL, psql). Capabilities: schema design, query optimization, indexing, migrations, replication, sharding, backup/restore, user management, performance analysis. Actions: design, query, optimize, migrate, backup, restore, index, shard databases. Keywords: MongoDB, PostgreSQL, SQL, NoSQL, BSON, aggregation pipeline, Atlas, psql, pgAdmin, schema design, index, query optimization, EXPLAIN, replication, sharding, backup, restore, migration, ORM, Prisma, Mongoose, connection pooling, transactions, ACID. Use when: designing database schemas, writing complex queries, optimizing query performance, creating indexes, performing migrations, setting up replication, implementing backup strategies, managing database permissions, troubleshooting slow queries.
Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.
Technical documentation discovery via context7 and web search. Capabilities: library/framework docs lookup, topic-specific search. Keywords: llms.txt, context7, documentation, library docs, API docs. Use when: searching library documentation, finding framework guides, looking up API references.
Multi-framework frontend development. Frameworks: React 18+ (Suspense, hooks, TanStack), Vue 3 (Composition API, Pinia, Nuxt), Svelte 5 (Runes, SvelteKit), Angular (Signals, standalone). Common: TypeScript, state management, routing, data fetching, performance optimization, component patterns. Actions: create, build, implement, style, optimize, refactor components/pages/features. Keywords: React, Vue, Svelte, Angular, component, TypeScript, hooks, Composition API, runes, signals, useSuspenseQuery, Pinia, stores, state management, routing, lazy loading, Suspense, performance, bundle size, code splitting, reactivity, props, events. Use when: creating components in any framework, building pages, fetching data, implementing routing, state management, optimizing performance, organizing frontend code, choosing between frameworks.
Google Gemini CLI orchestration for AI-assisted development. Capabilities: second opinion/cross-validation, real-time web search (Google Search), codebase architecture analysis, parallel code generation, code review from different perspective. Actions: query, search, analyze, generate, review with Gemini. Keywords: Gemini CLI, second opinion, cross-validation, Google Search, web research, current information, parallel AI, code review, architecture analysis, gemini prompt, AI comparison, real-time search, alternative perspective, code generation. Use when: needing second AI opinion, searching current web information, analyzing codebase architecture, generating code in parallel, getting alternative code review, researching current events/docs.
Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes.
Google Agent Development Kit (ADK) for Python. Capabilities: AI agent building, multi-agent systems, workflow agents (sequential/parallel/loop), tool integration (Google Search, Code Execution), Vertex AI deployment, agent evaluation, human-in-the-loop flows. Actions: build, create, deploy, evaluate, orchestrate AI agents. Keywords: Google ADK, Agent Development Kit, AI agent, multi-agent system, LlmAgent, SequentialAgent, ParallelAgent, LoopAgent, tool integration, Google Search, Code Execution, Vertex AI, Cloud Run, agent evaluation, human-in-the-loop, agent orchestration, workflow agent, hierarchical coordination. Use when: building AI agents, creating multi-agent systems, implementing workflow pipelines, integrating LLM agents with tools, deploying to Vertex AI, evaluating agent performance, implementing approval flows.
Comprehensive infrastructure engineering covering DevOps, cloud platforms, FinOps, and DevSecOps. Platforms: AWS (EC2, Lambda, S3, ECS, EKS, RDS, CloudFormation), Azure basics, Cloudflare (Workers, R2, D1, Pages), GCP (GKE, Cloud Run, Cloud Storage), Docker, Kubernetes. Capabilities: CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins), GitOps, infrastructure as code (Terraform, CloudFormation), container orchestration, cost optimization, security scanning, vulnerability management, secrets management, compliance (SOC2, HIPAA). Actions: deploy, configure, manage, scale, monitor, secure, optimize cloud infrastructure. Keywords: AWS, EC2, Lambda, S3, ECS, EKS, RDS, CloudFormation, Azure, Kubernetes, k8s, Docker, Terraform, CI/CD, GitHub Actions, GitLab CI, Jenkins, ArgoCD, Flux, cost optimization, FinOps, reserved instances, spot instances, security scanning, SAST, DAST, vulnerability management, secrets management, Vault, compliance, monitoring, observability. Use when: deploying to AWS/Azure/GCP/Cloudflare, setting up CI/CD pipelines, implementing GitOps workflows, managing Kubernetes clusters, optimizing cloud costs, implementing security best practices, managing infrastructure as code, container orchestration, compliance requirements, cost analysis and optimization.
Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
Video/audio/image processing with FFmpeg and ImageMagick. Tools: FFmpeg (video/audio), ImageMagick (images). Capabilities: format conversion, encoding (H.264/H.265/VP9/AV1), streaming (HLS/DASH), filters, effects, thumbnails, watermarks, batch processing, hardware acceleration (NVENC/QSV). Actions: convert, encode, resize, crop, compress, extract, merge, stream, transcode media. Keywords: FFmpeg, ImageMagick, video encoding, audio extraction, image resize, thumbnail, watermark, HLS, DASH, H.264, H.265, VP9, AV1, codec, bitrate, framerate, resolution, aspect ratio, filter, overlay, concat, trim, fade, batch processing. Use when: converting video/audio formats, encoding with specific codecs, generating thumbnails, creating streaming manifests, extracting audio from video, batch processing images, adding watermarks, optimizing file sizes.
Mise development environment manager (asdf + direnv + make replacement). Capabilities: tool version management (node, python, go, ruby, rust), environment variables, task runners, project-local configs. Actions: install, manage, configure, run tools/tasks with mise. Keywords: mise, mise.toml, tool version, runtime version, node, python, go, ruby, rust, asdf, direnv, task runner, environment variables, version manager, .tool-versions, mise install, mise use, mise run, mise tasks, project config, global config. Use when: installing runtime versions, managing tool versions, setting up dev environments, creating task runners, replacing asdf/direnv/make, configuring project-local tools.
Cross-platform and native mobile development. Frameworks: React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose. Capabilities: mobile UI, offline-first architecture, push notifications, deep linking, biometrics, app store deployment. Actions: build, create, implement, optimize, test, deploy mobile apps. Keywords: iOS, Android, React Native, Flutter, Swift, Kotlin, mobile app, offline sync, push notification, deep link, biometric auth, App Store, Play Store, iOS HIG, Material Design, battery optimization, memory management, mobile performance. Use when: building mobile apps, implementing mobile-first UX, choosing native vs cross-platform, optimizing battery/memory/network, deploying to app stores, handling mobile-specific features.
Full-stack web development with Next.js and Turborepo. Stack: Next.js 14+ (App Router, RSC, Server Actions, PPR, SSR, SSG, ISR), Turborepo (monorepo, pipelines, remote caching), RemixIcon (3100+ icons). Capabilities: server components, API routes, middleware, caching strategies, build optimization, monorepo management. Actions: create, build, deploy, optimize Next.js apps, setup monorepo, configure caching. Keywords: Next.js, App Router, Server Components, RSC, Server Actions, SSR, SSG, ISR, PPR, Turborepo, monorepo, remote cache, build pipeline, parallel execution, workspace, pnpm, icons. Use when: building Next.js apps, implementing SSR/SSG, setting up monorepos, optimizing build performance, configuring caching strategies, managing shared dependencies.
Payment gateway integration. Providers: SePay (Vietnamese: VietQR, bank transfer, cards), Polar (global SaaS: subscriptions, usage-based billing). SDKs: Node.js, PHP, Python, Go, Laravel, Next.js. Capabilities: checkout flows, subscription management, webhooks, QR code generation, benefit automation, tax compliance. Actions: integrate, implement, configure, handle payments/subscriptions/webhooks. Keywords: payment gateway, SePay, Polar, VietQR, bank transfer, subscription, usage-based billing, checkout, webhook, QR code, API key, OAuth2, product management, customer portal, tax compliance, MoR, recurring payment, invoice. Use when: integrating payment processing, implementing checkout, managing subscriptions, handling payment webhooks, generating payment QR codes, building billing systems.
Technical implementation planning and architecture design. Capabilities: feature planning, system architecture, technical evaluation, implementation roadmaps, requirement breakdown, trade-off analysis, codebase analysis, solution design. Actions: plan, architect, design, evaluate, breakdown technical solutions. Keywords: implementation plan, technical design, architecture, system design, roadmap, requirements analysis, trade-offs, technical evaluation, feature planning, solution design, scalability, security, maintainability, sprint planning, task breakdown. Use when: planning new features, designing system architecture, evaluating technical approaches, creating implementation roadmaps, breaking down complex requirements, assessing technical trade-offs.
Systematic problem-solving techniques for stuck-ness. Techniques: simplification cascade (complexity spirals), collision-zone thinking (innovation blocks), meta-pattern recognition (recurring issues), inversion exercise (assumption constraints), scale game (uncertainty). Actions: simplify, analyze, recognize patterns, invert assumptions, scale thinking. Keywords: problem solving, complexity spiral, innovation block, stuck, simplification, meta-pattern, assumption inversion, scale uncertainty, breakthrough thinking, root cause, systematic analysis, Microsoft Amplifier, debugging approach, creative solution. Use when: complexity spiraling, hitting innovation blocks, seeing recurring patterns, constrained by assumptions, uncertain about scale, generally stuck on problems.
Universal project planning for non-technical projects. Domains: business, personal, creative, academic, organizational, events. Capabilities: goal setting, milestone planning, resource allocation, timeline creation, risk assessment, progress tracking. Actions: create, plan, structure, breakdown, track projects. Keywords: project plan, roadmap, strategy, goal setting, milestones, timeline, action plan, project management, business plan, personal goals, creative project, academic planning, event planning, organizational change, OKRs, SMART goals, Gantt chart. Use when: creating project plans, setting goals/milestones, planning business initiatives, organizing events, structuring academic work, developing strategies/roadmaps.
Prompt engineering and optimization for AI/LLMs. Capabilities: transform unclear prompts, reduce token usage, improve structure, add constraints, optimize for specific models, backward-compatible rewrites. Actions: improve, enhance, optimize, refactor, compress prompts. Keywords: prompt engineering, prompt optimization, token efficiency, LLM prompt, AI prompt, clarity, structure, system prompt, user prompt, few-shot, chain-of-thought, instruction tuning, prompt compression, token reduction, prompt rewrite, semantic preservation. Use when: improving unclear prompts, reducing token consumption, optimizing LLM outputs, restructuring verbose requests, creating system prompts, enhancing prompt clarity.
Systematic code refactoring following Martin Fowler's catalog. Methodologies: characterization tests, Red-Green-Refactor, incremental transformation. Capabilities: SOLID compliance, DRY cleanup, code smell detection, complexity reduction, legacy modernization, design patterns, functional programming patterns. Actions: refactor, extract, inline, rename, move, simplify code. Keywords: refactor, SOLID, DRY, code smell, complexity, extract method, inline, rename, move, clean code, technical debt, legacy code, design pattern, characterization test, Red-Green-Refactor, functional programming, higher-order function, immutability, pure function, composition, currying, side effects. Use when: improving code quality, reducing technical debt, applying SOLID principles, fixing DRY violations, removing code smells, modernizing legacy code, applying design patterns.
Repository packaging for AI/LLM analysis. Capabilities: pack repos into single files, generate AI-friendly context, codebase snapshots, security audit prep, filter/exclude patterns, token counting, multiple output formats. Actions: pack, generate, export, analyze repositories for LLMs. Keywords: Repomix, repository packaging, LLM context, AI analysis, codebase snapshot, Claude context, ChatGPT context, Gemini context, code packaging, token count, file filtering, security audit, third-party library analysis, context window, single file output. Use when: packaging codebases for AI, generating LLM context, creating codebase snapshots, analyzing third-party libraries, preparing security audits, feeding repos to Claude/ChatGPT/Gemini.
Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.
Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems.
Shopify platform development. Stack: Shopify CLI, GraphQL/REST APIs, Polaris UI, Liquid templating. Capabilities: app development (OAuth), checkout UI extensions, admin UI extensions, POS extensions, theme development, webhooks, billing API, product/order/customer management. Actions: build, extend, customize, integrate Shopify apps/themes. Keywords: Shopify, Shopify CLI, GraphQL Admin API, REST API, Polaris, Liquid, checkout extension, admin extension, POS extension, theme, webhook, billing API, OAuth, app bridge, metafields, product, order, customer, storefront, hydrogen, oxygen. Use when: building Shopify apps, customizing checkout, creating admin interfaces, developing themes, integrating payments, managing store data via APIs, extending Shopify functionality.
React UI component systems with TailwindCSS + Radix + shadcn/ui. Stack: TailwindCSS (styling), Radix UI (primitives), shadcn/ui (components), React/Next.js. Capabilities: design system architecture, accessible components, responsive layouts, theming, dark mode, component composition. Actions: review, design, build, improve, refactor UI components. Keywords: TailwindCSS, Radix UI, shadcn/ui, design system, component library, accessibility, ARIA, responsive, dark mode, theming, CSS variables, component architecture, atomic design, design tokens, variant, slot, composition. Use when: building component libraries, implementing shadcn/ui, creating accessible UIs, setting up design systems, adding dark mode/theming, reviewing UI component architecture.
---
Word document processing. Format: .docx (ZIP/XML structure). Capabilities: create documents, edit content, tracked changes, comments, formatting preservation, text extraction, styles, headers/footers, tables, images. Actions: create, edit, analyze, extract from Word documents. Keywords: Word, docx, document, tracked changes, comments, formatting, styles, headers, footers, tables, images, paragraphs, text extraction, template, mail merge, revision history, document comparison. Use when: creating Word documents, editing docx files, working with tracked changes, adding comments, extracting document content, preserving document formatting.
PDF document processing and manipulation. Tools: Python (PyPDF2, pdfplumber, reportlab), CLI tools. Capabilities: text extraction, table extraction, form filling, merge/split documents, create PDFs, add annotations, watermarks, page manipulation. Actions: extract, create, merge, split, fill, annotate PDFs. Keywords: PDF, text extraction, table extraction, form fill, PDF form, merge PDF, split PDF, create PDF, reportlab, PyPDF2, pdfplumber, annotation, watermark, page rotation, PDF metadata, bookmarks, OCR. Use when: extracting text/tables from PDFs, filling PDF forms, merging/splitting documents, creating PDFs programmatically, adding annotations/watermarks, processing PDFs at scale.
PowerPoint presentation processing. Format: .pptx (ZIP/XML structure). Capabilities: create presentations, edit slides, layouts/masters, speaker notes, comments, shapes, images, charts, text extraction, template preservation. Actions: create, edit, analyze, extract from presentations. Keywords: PowerPoint, pptx, presentation, slide, layout, master slide, speaker notes, comments, shapes, images, charts, text extraction, template, slide deck, bullet points, title slide, content slide, animation. Use when: creating presentations, editing PowerPoint files, extracting slide content, modifying layouts, adding speaker notes, working with presentation templates.
Excel spreadsheet processing and analysis. Formats: .xlsx, .xlsm, .csv, .tsv. Capabilities: create spreadsheets, formulas (error-free), formatting, data analysis, charts, pivot tables, conditional formatting, data validation, template preservation. Actions: create, edit, analyze, visualize, recalculate spreadsheets. Keywords: Excel, spreadsheet, xlsx, csv, formula, VLOOKUP, SUMIF, pivot table, chart, graph, data analysis, formatting, conditional formatting, data validation, workbook, worksheet, cell reference, named range, macro. Use when: creating spreadsheets, editing Excel files, analyzing tabular data, building formulas, creating charts/graphs, working with CSV/TSV, preserving spreadsheet templates.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Uses power tools
Uses Bash, Write, or Edit tools
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
Complete developer toolkit for Claude Code
Comprehensive toolkit for developing Claude Code plugins. Includes 7 expert skills covering hooks, MCP integration, commands, agents, and best practices. AI-assisted plugin creation and validation.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
AI-powered development tools for code review, research, design, and workflow automation.