Prompt file imported from YoavLax/agent-compass (.github/prompts/add-rule.prompt.md). Copyright stays with the author.

Add a new scoring rule to AgentCompass following CONTRIBUTING.md's "Adding a rule" section and the determinism contract:

Ask for (or infer from context) the pillar, the rule id, the spec/failure mode it's derived from, and its severity/effort.
Add a pure @rule(...)-decorated function to the matching src/airx/rules/<pillar>.py module. Never call datetime.now(), time.time(), unseeded randomness, environment variables, network calls, or depend on filesystem iteration order or path separators/case.
Extend model.py/patterns.py/discovery.py first if the rule needs a new ArtifactKind or ArtifactIndex field.
Add pass/fail/not-applicable unit tests in tests/test_rules_<pillar>.py using tmp_path-built micro-repos.
Regenerate docs/RULES.md via airx rules --format md and bump RULESET_VERSION in src/airx/rules/registry.py.
Run pytest -v and show the passing output before finishing.

Add a new scoring rule to AgentCompass following [`CONTRIBUTING.md`](../../CONTRIBUTING.md)'s "Adding a rule" section and the determinism contract: 1. Ask for (or infer from context) the pillar, the rule id, the spec/failure mode it's derived from, and its severity/effort. 2. Add a pure `@rule(...)`-decorated function to the matching `src/airx/rules/<pillar>.py` module. Never call `datetime.now()`, `time.time()`, unseeded randomness, environment variables, network calls, or depend on filesystem iteration order or path separators/case. 3. Extend `model.py`/`patterns.py`/`discovery.py` first if the rule needs a new `ArtifactKind` or `ArtifactIndex` field. 4. Add pass/fail/not-applicable unit tests in `tests/test_rules_<pillar>.py` using `tmp_path`-built micro-repos. 5. Regenerate `docs/RULES.md` via `airx rules --format md` and bump `RULESET_VERSION` in `src/airx/rules/registry.py`. 6. Run `pytest -v` and show the passing output before finishing.

Install add-rule and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

add-rule

About

Use it

Install add-rule and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews