Skip to main content
Agent rules

Resolve the AGENTS.md you already have

Most of what is in that file does nothing. Here is what to cut and what to keep.

Cut these

Cut these

01

Style rules

The linter enforces them. The file only suggests them.

02

Restated defaults

“Write tests for new code” is what the model already does.

03

Project descriptions

The agent reads the repo. It does not need the pitch.

04

Directory layouts and dependency lists

Derivable from the codebase.

05

“Double-check your work.”

Current models self-verify. This causes over-checking.

06

Any rule nobody can trace to a real failure

If no incident produced it, no incident depends on it.

Keep these

Keep these

01

Names a real thing

A rule that names a command or a path binds. One that names a virtue does not.

Format with ruff format before committing
02

Does not fight another rule

When two rules disagree, the model picks one silently and the other reads as flakiness.

Line length 100 — and nowhere else says 80
03

Loads where it applies

Scope a rule to the directory it oversees instead of loading it on every request.

.cursor/rules/payments.mdc → src/payments/**
04

Behavior, not documentation

Enforce only what differs from the default; the rest is context the model already has.

Never call the billing API from a client component
27%

of the average instruction file actually instructs

62%

of files leak style rules the linter already enforces

20%

added inference cost, with no measured gain in task success

Start free

Build what you're proud to ship.

Bring a Codebase Architect to your AI-native engineering workflow.

Start free

Hyrax is free to start. Full product, $30 starter credit, $10/month of credits. No credit card.