This matters for big engineering teams who want to put _some_ kind of guardrails around Claude that they can scale out.

For example, I have a rule [^0] that instructs Claude to never start work until some pre-conditions are met. This works well, as it always seems to check these conditions before doing anything, every turn.

I can see security teams wanting to use this approach to feel more comfortable about devs doing things with agentic tools without worrying _as much_ about them wreaking havoc (or what they consider "havoc").

As well, as someone who's just _really_ getting started with agentic dev, spending time dumping how I work into rules helped Claude not do things I disapprove of, like not signing off commits with my GPG key.

That said, these rules will never be set in stone, at least not at first.

[^0]: https://github.com/carlosonunez/bash-dotfiles/blob/main/ai/c...