Your AI agent needs an identity, not just instructions ...
Just tightened my ICM knowledge base / workspace and realized something that should have been obvious:
Most people write prompts.
Fewer people write identity.
So I made a reusable Operator Identity template for any workspace. It defines who the agent is, what loop it owns, how it should think, what it will not do, and which files are the source of truth.
The part that helped most was separating role from rules... Identity says what the Operator owns, while the rules say how work gets done.
Identity.md now has sections for:
  • Operating Posture
  • Quality Standard
  • Core Work
  • Boundaries
  • Non-Negotiables
  • Execution Sources
Do you write a separate Identity for your agents, or do you keep everything inside one big instruction file? Anything else you include in Identity?
11
24 comments
Aaron Klein
5
Your AI agent needs an identity, not just instructions ...
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by