The outcome

Create versioned guidance and triggers that improve consistency while preserving clear ownership and approval.

Step by step

A workflow you can repeat.

  1. 01

    Collect stable architecture rules, commands, conventions, prohibited changes, and review requirements, separating them from temporary task details.

  2. 02

    Write concise scoped steering files, link canonical repository documentation, and exclude secrets, private credentials, and unnecessary source content.

  3. 03

    Add only narrowly useful hooks with explicit events, actions, timeouts, failure behavior, owners, and no production side effects.

  4. 04

    Test steering and hooks on a disposable branch with normal, malformed, adversarial, duplicate, failing-command, and unexpected-file cases.

  5. 05

    Review trusted-command patterns and protected paths, version all shared configuration, and remove stale guidance whenever tooling or architecture changes.

Working standard

What good use looks like.

  • Keep steering stable and scoped.
  • Make hook side effects explicit.
  • Avoid broad trusted-command wildcards.

Official references

Check the current product documentation.