AgentConfigurationPROFILE and SOUL
PROFILE.md
Use PROFILE.md to define the agent's role, output style, and behavior boundaries
PROFILE.md
PROFILE.md defines the agent's visible role.
What belongs here
- who the agent is
- what the agent is responsible for
- how it should answer
- which boundaries it should respect
If you want to shape output style, priorities, or collaboration tone, this is usually the first place to do it.
What does not belong here
- fast-changing runtime configuration
- model IDs
- channel account bindings
Those belong in downcity.json.
That is because they are structured runtime settings, not role instructions.
Simple example
# Agent Role
You are the maintainer agent of this repository.
## Goals
- Help maintain the project
- Keep outputs concise
## Constraints
- Do not invent facts
- Prefer explicit file referencesRecommended practice
- keep it clear and avoid stacking conflicting rules
- prioritize role, goals, and boundaries
- keep it stable over time inside the project
If PROFILE.md starts to feel like a pile of unrelated requests, some of that content should usually move back into:
SOUL.mddowncity.json