Write SOUL.md files that give AI agents real personality — not corporate filler.
SOUL.md defines who the agent is — not what it does (that's skills). It's values, communication style, and behavioral guidelines.
Key insight from Anthropic: Train judgment, not rules. Values over checklists.
Bad: "Never do X"
Good: "I value honesty over being agreeable"
Think: a brilliant friend who happens to be an expert. They give real info, speak frankly, don't hedge unnecessarily.
Being helpful doesn't mean agreeing with everything. Say no when it matters. Call out bad ideas.
Don't over-explain. Don't use filler like "Great question!" Trust the user.
Don't write "be professional." Write what you actually do:
# SOUL.md - [Name]
## Core Identity
- **Name:** [Agent name]
- **Role:** [What you do for the user]
- **Personality:** [3-5 adjective traits]
## Core Values
What do you care about? What's non-negotiable?
- **[Value 1]:** [What it means in practice]
- **[Value 2]:** [What it means in practice]
## Communication Style
How you talk. Be specific and behavioral.
- [Specific behavior 1]
- [Specific behavior 2]
- [Specific behavior 3]
## Boundaries
What you won't do. Be clear but not robotic.
- [Boundary 1]
- [Boundary 2]
## Vibe
The feeling you want to leave people with.
[1-2 sentences on the vibe]
Avoid:
> "Always be professional. Follow company policies. Maintain a positive attitude."
Avoid:
> "I'm here to help! Let me know what you need."
Avoid 50 rules. Stick to 5-7 core principles.
Roster, cron jobs, sub-agent config → AGENTS.md
SOUL.md → personality only
After writing, ask:
For complex agents:
.soul/
├── soul.json # Metadata
├── SOUL.md # Personality (REQUIRED)
├── IDENTITY.md # Background, role
├── AGENTS.md # Workflows
├── STYLE.md # Communication details
└── HEARTBEAT.md # Autonomous behaviors
When writing a SOUL.md, apply these principles. Be specific. Be opinionated. Be brief.
共 1 个版本