AGENTS.md

Ruby on Rails application. Replace the bracketed bits with your details.

Stack

• Ruby 3.3, Rails 7.1.
• Dependency manager: Bundler. Lint: RuboCop. Tests: RSpec.

Project Structure

• app/ — MVC code: models/, controllers/, views/, jobs/, services/.
• config/ — routes, environments, credentials; db/ — schema + migrations.
• spec/ — RSpec tests mirroring app/; Gemfile — dependencies.

Setup

bundle install               # install gems
cp .env.example .env         # local config; never commit .env
bin/rails db:setup           # create + migrate + seed the dev DB

Commands

bin/rails server                       # dev server (http://localhost:3000)
bundle exec rspec                      # run all specs
bundle exec rspec spec/models/order_spec.rb   # one spec file
bin/rails db:migrate                   # apply migrations
bin/rails g migration AddXToY x:string # generate a migration
bundle exec rubocop -A                 # lint + autocorrect

Code style

• Follow RuboCop (rails + rspec cops); run rubocop -A before committing.
• Keep controllers skinny; push logic into models, service objects, or jobs.
• Use strong parameters; never pass raw params to update/create.

Example — a service object with strong params in the controller:

class OrdersController < ApplicationController
  def create
    order = Orders::Create.call(order_params)
    render json: order, status: :created
  end

  private

  def order_params
    params.require(:order).permit(:sku, :qty)
  end
end

Testing

• Specs live under spec/, mirroring app/.
• A change is done when bundle exec rubocop and bundle exec rspec pass.
• Add a failing spec first, then make it pass (TDD).

Git & PRs

1. Branch from main: git switch -c feat/<short-name>.
2. Conventional Commits (feat:, fix:, chore:).
3. Before pushing: bundle exec rubocop && bundle exec rspec.
4. PR: one-line summary + the test command you ran + any new migrations.

Boundaries

• Always: edit app/**, read .env.example for required config, and run rubocop -A plus rspec before pushing.
• Always: generate a new migration for schema changes and re-run db:migrate.
• Always: use strong parameters and parameterized queries (where(id: id)).
• Ask first: before changing the Gemfile, initializers, or routes that affect auth or external integrations.
• Never: edit an already-applied migration — add a new one instead.
• Never: skip strong parameters or interpolate user input into SQL.
• Never commit secrets, master.key, or .env.

More

• Domain/service layout: docs/architecture.md.

agents-md-cookbook

The tested, tool-agnostic AGENTS.md kit.

Copy a battle-tested AGENTS.md into your repo, lint it in CI, and migrate your old CLAUDE.md / .cursorrules in one command. Every template is short on purpose, leads with runnable commands, and is checked by our own linter.

AGENTS.md is a single Markdown file at your repo root that tells coding agents how to build, test, and behave in your project. It is stewarded by the Linux Foundation's Agentic AI Foundation, lives in 60,000+ repositories, and is read natively by 24+ tools. One file, every agent.

---

30-second value prop

• Tool-agnostic. One AGENTS.md works across Cursor, Codex, Copilot, Windsurf, Cline, Zed, Jules, Amp, and more. See the full compatibility matrix.
• Tested, not vibes. Templates follow evidence from GitHub's 2,500-repo study, ETH Zurich's AGENTbench, and Augment's golden-PR eval — and CI lints every template with our own agents-md-lint.
• Short by design. 60-150 lines, commands first, real code snippets, explicit boundaries. No platitudes, no architecture essays, no token bloat.
• Migrate in one command. Turn an existing CLAUDE.md, .cursorrules, or GEMINI.md into a clean AGENTS.md with agents-md-migrate.

Quick start

1. Copy a template for your stack into your repo root as AGENTS.md (filename must be exactly AGENTS.md — uppercase AGENTS, lowercase .md):

   curl -fsSL \
     https://raw.githubusercontent.com/Taiizor/agents-md-cookbook/main/templates/typescript-node/AGENTS.md \
     -o AGENTS.md
   

   Browse the full template index for other stacks.

2. Already have agent instructions? Migrate them instead of starting over:

   bunx agents-md-migrate          # or: npx agents-md-migrate
   

   This detects CLAUDE.md, .cursorrules, GEMINI.md, and friends, then produces a single AGENTS.md. (Published by the agents-md-migrate package.)

3. Lint it in CI so the file stays accurate as your project grows:

   # .github/workflows/ci.yml
   - name: Lint AGENTS.md
     run: bunx agents-md-lint AGENTS.md   # or: npx agents-md-lint AGENTS.md
   

   Prefer a one-line GitHub Action? Use the bundled action.yml:

   # .github/workflows/ci.yml
   - uses: Taiizor/agents-md-cookbook@v1
     with:
       path: AGENTS.md
   

Compatibility at a glance

Tool	Reads AGENTS.md?
Cursor	NATIVE
OpenAI Codex	NATIVE
GitHub Copilot (coding agent)	NATIVE
Windsurf / Cascade	NATIVE
Cline	NATIVE
Zed	NATIVE (first-match)
Amp	NATIVE
Google Jules	NATIVE
opencode / RooCode	NATIVE
Claude Code	ADAPTER (symlink / @AGENTS.md)
Aider	ADAPTER (--read AGENTS.md)
Gemini CLI	CONFIG (opt-in)
Copilot (VS Code chat)	CONFIG (experimental)

Full mechanism, nesting behavior, own-file fallbacks, and sources are in COMPATIBILITY.md (with a dated last-verified line).

Templates

Each template is a complete, copy-pasteable AGENTS.md for one stack.

Stack	Path
TypeScript + Node	templates/typescript-node/AGENTS.md
Python	templates/python/AGENTS.md
Go	templates/go/AGENTS.md
Rust	templates/rust/AGENTS.md
Java + Spring Boot	templates/java-spring/AGENTS.md
.NET / C#	templates/dotnet-csharp/AGENTS.md
Next.js	templates/nextjs/AGENTS.md
React + Vite	templates/react-vite/AGENTS.md
Django	templates/django/AGENTS.md
FastAPI	templates/fastapi/AGENTS.md
Ruby on Rails	templates/rails/AGENTS.md
Monorepo (root)	templates/monorepo/AGENTS.md
Data / ML	templates/data-ml/AGENTS.md
React Native / Expo	templates/react-native/AGENTS.md
Minimal starter	templates/minimal/AGENTS.md

Why AGENTS.md

Coding agents auto-execute the commands you list, so a single file that is accurate, short, and command-first beats scattered per-tool config. The research is blunt about what works:

• Lead with commands and flags. GitHub's review of 2,500+ repos found the best files put build/test commands early with exact flags, prefer code examples over prose, and pair every boundary with a "do."
• Keep it short and non-inferable. ETH Zurich's AGENTbench found auto-generated /init files reduce task success ~3% and raise cost ~20-23%; agents follow files faithfully, so every wrong line is executed. Limit content to what an agent cannot infer (custom tooling, unusual builds).
• Aim for 100-150 lines. Augment's golden-PR eval found a 100-150 line sweet spot, numbered workflows (+25% correctness), decision tables, and 3-10 line real-code examples (+20% reuse); gains reverse beyond ~300 lines.

Read the full handbook: anatomy · best practices · nesting & monorepos · common mistakes.

Tooling

Published to npm so you can run them with bunx or npx (no install needed):

• agents-md-lint — scores an AGENTS.md against the evidence-based rules and fails CI on regressions.
• agents-md-migrate — converts existing CLAUDE.md / .cursorrules / GEMINI.md into a clean AGENTS.md.

These CLIs live under packages/ and are released by separate plans; this repo dogfoods agents-md-lint on its own templates in CI.

Contributing

Templates and matrix updates are the lifeblood of this repo. To add a stack, fix a command, or correct a tool's support status, read CONTRIBUTING.md and open an issue from one of our templates. Every PR is link-checked and content-linted automatically.

Credits & sources

• The AGENTS.md standard: https://agents.md/
• GitHub Blog — How to write a great agents.md: Lessons from over 2,500 repositories (Matt Nigh, 2025-11-25).
• ETH Zurich — Evaluating AGENTS.md (arXiv:2602.11988, Feb 2026), benchmark AGENTbench.
• Augment Code — AuggieBench golden-PR evaluation.
• philschmid — practical AGENTS.md length/structure guidance.

License

MIT © 2026 Taiizor