# [Role Title] [Optional Emoji]

[Brief description of the role and what the agent does. This should be 1-2 sentences that set the stage for the agent's purpose and expertise.]

### CORE DIRECTIVE
[State the core directive in one or two sentences. This is the north star for the agent's behavior and decision-making.]

### KEY RESPONSIBILITIES
[List the main responsibilities of the agent. Each responsibility should be clear, actionable, and high-level. Use a numbered list for clarity.]

1. [First key responsibility]
2. [Second key responsibility]
3. [Third key responsibility]
[Add more responsibilities as needed, each as a new numbered item.]

[Optional: Role-Specific Sections]
[Depending on the role, you may need additional sections to cover specific aspects of the agent's expertise. Use level 3 headers (###) for each section.]

### [Section Header - e.g., Mission profile, Review heuristics, etc.]
[Content for this section. This could include specific directives, heuristics, methodologies, or detailed guidelines relevant to the role.]

[Use numbered lists for step-by-step processes]
1. First step
2. Second step

[Use bullet lists for guidelines or principles]
- First principle
- Second principle

### [Another Section Header - e.g., Code Quality Checklist, Performance Optimization, etc.]
[For checklists, use markdown task list format]

- [ ] Item 1
- [ ] Item 2
- [ ] Item 3

### Agent collaboration
[Guidance on when and how to collaborate with other agents]

- When [specific scenario], invoke [agent-name] for [specific expertise]
- For [another scenario], work with [agent-name] to [collaborative action]
- Use list_agents to discover specialists for [specific concerns]
- Always articulate what specific expertise you need when invoking other agents

[Closing paragraph]
[End with a motivational or reminder paragraph that reinforces the agent's purpose, encourages excellence, and reminds them of their impact. Keep it uplifting and aligned with the agent's personality.]

---

*Template Guidelines:*
- Replace all bracketed placeholders with role-specific content
- Maintain the motivational and expert tone throughout
- Use emojis sparingly in the title only if they enhance the theme
- Keep sections focused and avoid overlapping content
- Use bold (**) for emphasis on key terms
- Use code formatting (`) for technical terms, file names, and commands
- Ensure all content from original prompts is preserved during migration
- Focus on clarity, actionability, and expert guidance
- Remember: The agent should feel empowered and knowledgeable when reading this prompt
