Cursor Rules Pack

24 focused Cursor project rules (.mdc) for the stacks people actually use, an installer that detects your stack and copies only the rules you need into .cursor/rules/, an AGENTS.md exporter for Claude Code / Codex / other agents, and a rules linter.

Every rule follows Cursor's documented format and best practices: frontmatter with description / globs / alwaysApply, one topic per rule, under 20 lines each (Cursor recommends < 500), concrete instructions instead of "write clean code". Only one rule is always applied (13 lines); the rest attach by file pattern or when the Agent decides they're relevant, so they don't fill your context.

python3 tools/install_rules.py --detect ~/code/my-app        # what stacks does it use?
python3 tools/install_rules.py ~/code/my-app --auto          # core rules + detected stacks -> .cursor/rules/
python3 tools/install_rules.py ~/code/my-app --stack core,python,docker --dry-run
python3 tools/install_rules.py ~/code/my-app --auto --agents-md   # also write AGENTS.md

Existing files are never overwritten unless you add --force. Or skip the installer: copy any rules/*.mdc into .cursor/rules/ yourself.

As a Cursor plugin: copy this folder to ~/.cursor/plugins/local/cursor-rules-pack and reload the window (manifest: .cursor-plugin/plugin.json). That loads all 24 rules in every project, so most people prefer the per-project install above.

Detection looks at package.json dependencies (next, react, tailwindcss, typescript, express/fastify/koa/nest/hono, supabase), pyproject/requirements/.py files, go.mod, Cargo.toml, pom.xml/build.gradle, pubspec.yaml, Dockerfiles/compose files, .github/workflows, *.tf, *.sql and migrations folders.

python3 tools/lint_rules.py .cursor/rules --project .
python3 tools/lint_rules.py examples/broken-rules     # see what it catches

Flags plain .md files Cursor ignores, missing or unclosed frontmatter, alwaysApply: yes, misspelled keys (always_apply), globs ignored because alwaysApply: true, ./ or absolute globs, globs that match no file in your project, @file references that don't exist, empty rules, duplicates, rules over 500 lines, too many always-applied lines, and vague instructions. Exit code 1 on errors, --json for CI.

./tools/demo.sh     # detect + install + lint on examples/sample-app (Next.js + Supabase), in a temp copy
./run_tests.sh      # 14 test groups

Python 3.9+, standard library only, offline.

Rules are starting points: open the installed .mdc files and change them to match your team (Cursor: add a rule when you see the Agent repeat the same mistake). Globs are written unquoted and comma-separated, the way Cursor's own editor writes them.

• Rules guide the model; they don't enforce anything. Use linters, tests and CI for hard requirements.
• Framework advice targets current stable versions (e.g. Next.js App Router, Pydantic v2 style). Check against the versions in your project; the rules tell the Agent to do the same.
• The linter checks structure and references against Cursor's documented format; it can't tell whether a rule's advice is right for your codebase.
• Detection is file-based and can miss monorepo sub-packages: run it on each package folder or use --stack.