Skip to content

Agent-Ready Rules Bundle

Getting started

Agent-Ready Rules Bundle

You can read this before you buy. After checkout, unzip agent-ready-rules. There is no app to start. You copy one stack folder into a repository you already have. The eight stacks are nextjs, astro, fastapi, node-api, expo, go, rust and tauri.

Want to try two stacks first? The free Next.js and FastAPI download is on the Free rules page.

What you need installed

The first 15 minutes

  1. Pick one stack

    Open README.md in the unzipped folder. Choose one directory under stacks/. Each one contains AGENTS.md, a CLAUDE.md that imports it, .cursor/rules/<stack>.mdc, and .cursor/rules/core-quality-safety.mdc.

  2. Copy it into the repo root, including the hidden folder

    The commands below use Next.js. Swap nextjs for astro, fastapi, node-api, expo, go, rust or tauri. On Windows, the first Copy-Item skips the hidden .cursor directory, so the README includes a second command.

    # macOS and Linux
    cp -r stacks/nextjs/. /path/to/your-repo/
    
    # Windows PowerShell
    Copy-Item -Recurse -Force stacks\nextjs\* C:\path\to\repo\
    Copy-Item -Recurse -Force stacks\nextjs\.cursor C:\path\to\repo\
  3. Keep an AGENTS.md you already have

    If the repo already has an AGENTS.md, paste in the "Stack rules" and "Safety" sections from the kit file. The README says to do that instead of replacing your file blindly. In a monorepo, put a root AGENTS.md at the top and a stack AGENTS.md in each package. The README says agents use the nearest one.

  4. Match the check commands to this repo

    Open the copied AGENTS.md and edit "Checks to run before finishing". The defaults are: Next.js, npm run lint && npx tsc --noEmit && npm test && npm run build; Astro, npx astro check && npm run build; FastAPI, ruff check . && ruff format --check . && mypy . && pytest -q; Node API, npm run lint && npx tsc --noEmit && npm test; Expo, npx expo lint && npx tsc --noEmit && npm test; Go, gofmt -l . && go vet ./... && go test -race ./...; Rust, cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo test; Tauri, npm run build, then the cargo fmt, clippy and test commands in src-tauri. The README says matching these to your real scripts is the change that matters most.

  5. Ask the agent what it will run

    Open a new chat in that repo and ask which checks it will run before it says the work is done. You want the commands you just edited. CLAUDE.md pulls in AGENTS.md with @AGENTS.md, and it adds Claude Code notes: plan mode for changes that touch more than three files, and a prompt before a command that deletes data, pushes, deploys or spends money.

Common problems

Cursor rules never show up
On Windows, Copy-Item of stacks\nextjs\* skips the hidden .cursor folder. Run the second command from the README so .cursor\rules\ is in the repo. Each stack has a file-scoped rule and core-quality-safety.mdc.
The agent is not following the rules
AGENTS.md needs to be in the repo, or in a parent folder for agents that walk upward. Claude Code reads CLAUDE.md. Cursor reads the .mdc files under .cursor/rules/. A copy that left .cursor behind only covers the Markdown files.
A check fails because that script does not exist
The Checks block is a default for that stack. Change it to the scripts in your package.json, pyproject, go.mod or Cargo.toml. The file already tells the agent to use the nearest equivalent and to say so.
Go, Rust or Tauri rules are missing from a download
The free zip linked from the Free page is Next.js and FastAPI. The paid zip is the eight-stack folder described above, with stacks/ at the top.

Back to Agent-Ready Rules Bundle for what's included and checkout.