AdvisedUse the shared design system
Noah + Cursor
New form component proposed
Session · Customer settings redesign · v3Reused the shared form and approved spacing tokens.
Duplicate UI implementation avoided.ENFORCE / RULEBOOK
Agents ignoring your rules?
Turn repeated fixes into team standards.
All teammates Shared rulesSee your project rules in a Rulebook demo
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.
Same rule. Less rework.
Watch the same task play out. See where the extra tokens and time go.
Without XTraceinvoices-api
✳Working…
Tokens used0
Elapsed time0:00 min
› Add an overdue invoices endpoint. Keep the change lean.
I’ll add the route and response schema.
● Edit routes/invoices.py + GET /invoices/overdue
The endpoint is ready. I’ll leave the documentation for later.
● Run endpoint tests ✓ Passed. Task marked complete.
3 hrs later… during review “Where are the docs? We have a rule for this.”
You’re right. I’ll update the docs and run the checks again.
● Edit openapi.json + summary, description, responses
● Verify route + documentation ✓ Both updated. Ready for review.
With XTraceinvoices-api
XTrace caught it. Rule fired.
Document every new route in OpenAPI: summary, description, responses.✳Working…
Tokens used0
Elapsed time0:00 min
› Add an overdue invoices endpoint. Keep the change lean.
I’ll add the route and response schema.
● Edit routes/invoices.py + GET /invoices/overdue
XTrace caught it. Rule fired. Document every new route in OpenAPI: summary, description, responses.
I’ll update the OpenAPI docs before marking this complete.
● Edit openapi.json + summary, description, responses
● Verify route + documentation ✓ Both updated. Ready for review.
ADVISE → GATE → BLOCK
The right check.
At the right moment.
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
Bring one recurring agent mistake.
Show us a rule your agents keep missing. Request a Rulebook demo and we will email you to arrange a walkthrough with your workflow in mind.
Request a Rulebook demo →