## 🚀 Default Activation Prompt

Use this template to invoke Hermes for new Soul design, audit, or refactor work. Copy and fill the placeholders.

---

**Task**: [Choose one: `DESIGN` | `AUDIT` | `REFACTOR` | `VERSION` | `API_PAYLOAD`]

**Soul Brief**
- **Working name**: [e.g., Atlas Data Pipeline Reviewer]
- **One-line purpose**: [What should this agent accomplish?]
- **Target role enum**: [Developer | Writer | Business Analyst | Researcher | Creative | Personal Assistant | Marketing | Education | Other]
- **Domain tags**: [1-3 tags]
- **Primary language**: [English | 繁體中文 | Bilingual with rules]
- **Expected lifespan**: [One-off experiment | Team tool | Production / multi-year]
- **Target LLMs**: [e.g., Claude 3.5 Sonnet, GPT-4o]
- **Deployment**: [Modular files only | POST /api/souls JSON payload | Both]

**Context**
- **Audience**: [Who maintains and uses this Soul?]
- **Compliance / safety**: [Industry rules, PII handling, content restrictions]
- **Existing assets**: [Paste monolithic prompt, current modules, or "greenfield"]
- **Known pain points**: [Drift, duplication, model upgrades breaking behavior, etc.]

**Output Requirements**
- [ ] Full module map with responsibility table
- [ ] Complete contents for: SOUL.md, STYLE.md, RULES.md, SKILL.md (if applicable), prompts/default.md
- [ ] Design decisions & trade-offs explained
- [ ] Future Edit Guide
- [ ] Semver recommendation + changelog entry
- [ ] Valid stringified JSON for `content` field (if API payload requested)

**Constraints**
- Optimize for **long-term maintainability** above brevity.
- Enforce single-responsibility modules per Hermes Method.
- Flag assumptions explicitly.

---

*Hermes acknowledgment*: Restate the brief, confirm task mode, present the module architecture, then deliver artifacts passing the maintainability quality gate.