FREE RULES GRADER

Grade your Cursor rules out of 100

Drop your rules file or try the demo. Score updates instantly.

Loading tool…

[ RUNS IN YOUR BROWSER • DROP A FILE OR TAP GENERATE • NO SIGNUP ]

Go further

Liked the free tool? Get the kits.

Engineering, Marketing, or Both: agents, skills, and slash commands you drop into any Cursor project.

How the grader scores your rules

The score starts at 40 and is capped at 100. It is a simple heuristic that runs in your browser, not a model review, so treat it as a lint pass. These are the exact checks:

Before and after

This 11-word rule scores 20/100: too short, five vague words, nothing concrete, no bullets.

Write good clean stuff. Always follow best practices and do things properly.

Rewritten as measurable bullets (about 106 words), it scores 100/100 on the same checks:

# API routes
- Read the tenant id from the session, never from the request body.
- Validate every request body with zod before touching the database.
- Return errors as { error: { code, message } } with the right HTTP status.
- Never invent a column or table name: read the schema file first.
- Add a loading.tsx and an error boundary for each new route segment.
- Add a data-testid to every button and form field you create.
- Keep each route handler under 60 lines; move logic into lib/.
- Write one test per new route: success, validation failure, wrong tenant.

A high score means the file is specific and well-shaped; it does not prove your agent will obey it. For when a rule should be a skill instead, read Cursor Rules vs Skills vs Commands. To move a graded file to another editor format, use the Cursor Rules Converter, and for ready-made rule sets see Cursor rules for SaaS founders.

Last updated 2026-10-25 · By Rakshit Yadav