ENFORCE / RULEBOOK · BETA

Your team’s playbook.
Built into every agent’s work.

Turn lessons from real coding sessions into a living rulebook. Carry design principles, engineering conventions, and working procedures to every teammate’s agents—with reviewed guidance, approval gates, and blocking checks in supported workflows.

Turn lessons from real coding sessions into a living rulebook. Carry design principles, engineering conventions, and working procedures to every teammate’s agents—with reviewed guidance, approval gates, and blocking checks in supported workflows.

Book a demo

All teammates Shared rulesUpload CLAUDE.md or AGENTS.md to generate rules
Rule fires314 active rules
Blocked415 advised · 12 gated
Rule adherence91%Up from 60%
Judge tokens0.4MTracked separately
Advise GuidanceGate Human approvalBlock Required check
Rule · sourceCheckModeFires
Use the shared design systemDesign principles · Component reuse · v3JudgeAdvise8
Ask before destructive Git commandsAGENTS.md · Git safety · v3HookGate12
Use TypeScript in source files.claude/rules/typescript.md · v1LinterAdvise7
Run tests before calling it doneCLAUDE.md · Completion checks · v2HookBlock4

Protect the work.
Scale your best judgment.

Reduce repeat corrections

Turn a recurring mistake into a rule that reaches the next agent before the same correction is needed. Protect review cycles, senior attention, and delivery time.

Enforce the way your team builds

Apply shared design principles, coding conventions, and architectural decisions to every teammate’s connected agents. Review the rule, set its scope, and keep a consistent standard across your team.

Trace the rule back to the work

Keep the source session or written standard behind every rule. See what fired and what followed, then review interventions alongside rework, human effort, and task outcomes.

ADVISE → GATE → BLOCK

The right check.
At the right moment.

Sync current standards when a session opens and check relevant actions before they run. New rules start advisory. A reviewer can promote them to a gate that requests human approval, or a blocker that stops an action until its requirements pass, in supported integrations.

Sync current standards when a session opens and check relevant actions before they run. New rules start advisory. A reviewer can promote them to a gate that requests human approval, or a blocker that stops an action until its requirements pass, in supported integrations.

LINTER

Check code conventions

Use deterministic checks for rules the code can prove: TypeScript in source files, naming conventions, approved design tokens, or security boundaries. Catch matching violations in the diff.

HOOK

Control critical moments

Require tests before an agent calls a task done, or pause a destructive command for human approval. Hooks apply the rule at a supported step in the session.

JUDGE

Apply design and architecture principles

Use an agent judge when a rule needs context: reuse approved components, follow the design system, or build on existing architecture. The judge advises or escalates according to the reviewed rule.

CLOSE THE LOOP / OBSERVE

See the work your rules protect.

Connect each firing to the action, session, and outcome. Review repeated corrections, rework, and human effort in Observe to see which rules help and what needs changing.

Return to Observe →