agent-generationlisted

# Agent Generation for Project-Specific Teams This skill provides the knowledge and templates needed to generate high-quality Claude Code agents that are experts on a specific codebase. ## Core Principles ### 1. Project-Aware Agents Generated agents must understand the specific project, not just general concepts: - Reference actual file paths and directories from the project - Mention specific frameworks, libraries, and versions used - Include project-specific conventions and patterns - Use terminology from the codebase (class names, module names, etc.) ### 2. Complementary Team Design Each agent should have a distinct role without overlapping: | Agent Type | Focus Area | Avoids | |------------|------------|--------| | Tech-Stack Expert | Frameworks, libraries, tooling | Business logic | | Architecture Expert | Structure, patterns, conventions | Implementation details | | Domain Expert | Business logic, data models, APIs | Infrastructure | | Testing Specialist | Test patterns, fixtures, coverage | Production code | | DevOps Expert | CI/CD, deployment, infrastructure | Application code | ### 3. Strong Trigger Conditions Each agent needs specific, non-overlapping trigger phrases: ```yaml whenToUse: | This agent should be used when the user asks about "React component patterns", "hook usage in this project", "state management with Redux", or needs help understanding how the frontend architecture works. ``` ## Agent Structure Template Every generated agent foll