## 🚀 Activation Template

Use this template when the user wants to begin a Soul decomposition engagement. Adapt questions to context; skip phases already answered.

---

### User Prompt (copy & customize)

```
I need an Ironclaw Soul for the following agent concept:

**Concept:** [one-sentence description]

**Primary users:** [who invokes this agent]

**Must-do behaviors:** [3–5 bullets]

**Must-not behaviors:** [3–5 bullets]

**Output modes:** [e.g., API JSON only / conversational / both]

**Language for modules:** [English / 繁體中文]

**Suggested role enum:** [Developer | Writer | ...]

**Domain tags:** [1–3 tags]

Please:
1. Present the module architecture map with ownership table
2. Author all modules in full
3. Deliver a valid POST /api/souls JSON payload (if output mode includes API)
```

---

### Consultant Opening (when user provides minimal input)

When activated with only a concept name, respond with:

1. **Restated concept** — your interpretation in one paragraph
2. **Recommended pattern** — A/B/C/D/E from SKILL.md
3. **Clarifying questions** — max 5, prioritized
4. **Provisional module tree** — subject to revision after answers

---

### Audit Mode Trigger

If the user says **"audit my Soul"** or pastes an existing `content` JSON:

1. Parse and inventory all modules
2. Run the Soul Linter checklist
3. Report findings by severity: **Critical / Major / Minor**
4. Propose a rebalanced module map (do not rewrite until user confirms)

---

### Fast-Track API Mode Trigger

If the user says **"generate JSON only"** or **"POST /api/souls"**:

- Skip conversational architecture brief
- Apply defaults: `is_public: 1`, compatibility `Claude 3.5 Sonnet` unless specified
- Output **only** the JSON object per RULES.md

---

### Example Mini-Concept

> **Concept:** SaaS onboarding email sequence writer
> **Pattern A** → SOUL (conversion copywriter identity), STYLE (email formatting, subject line conventions), RULES (no false claims, CAN-SPAM), SKILL (AIDA, sequence timing), prompts/default (brief intake for product features)

Use examples sparingly—only to teach the decomposition shape, not to override the user's domain.