Laravel · AGENTS.md

The Laravel AGENTS.md, done right.

Copy a production-ready example below, or generate one tuned to your exact Laravel setup in about thirty seconds — free, in your browser.

 AGENTS.md
# your-laravel-app

> Laravel project.

Instructions for AI coding agents working in this repository.

## Setup

- Install dependencies: `composer install`
- Start dev server: `php artisan serve`
- Run tests: `php artisan test`

## Code style

- Follow PSR-12; format with Pint.
- Use Eloquent; avoid raw queries unless necessary.
- Validate input with Form Requests.

## Guardrails

Things agents get wrong here. Follow these strictly:

- Never edit migration files after they have run in production.
- Don’t put logic in controllers — use actions or services.

Why Laravel projects need this

Dropped into a Laravel repo with no context, an AI agent guesses: it reaches for the wrong package manager, ignores your structure, and edits files it shouldn’t. AGENTS.md is the briefing it reads first — so the very next prompt behaves like a teammate who already knows your conventions.

What to put in it

The example above covers the three sections that matter most for Laravel: the real setup commands (composer install, php artisan serve, php artisan test), your code-style conventions, and the guardrails agents reliably get wrong. The generator fills these in from your actual manifest so the commands match your project, not a generic template.

Frequently asked

What is an AGENTS.md file in a Laravel project?

It is a markdown file at your repo root that tells AI coding agents how your Laravel project works — setup commands, code style and guardrails — so they follow your conventions instead of guessing.

Which tools read this file?

AGENTS.md is a shared convention read by Cursor, Claude Code, OpenAI Codex, GitHub Copilot, Gemini, Windsurf, Zed and others. For tools with their own filename you can export that format or symlink it to AGENTS.md.

What should a Laravel AGENTS.md include?

At minimum: install/dev/test commands (composer install, php artisan serve, php artisan test), your code-style conventions, and the guardrails agents get wrong — like Never edit migration files after they have run in production.

Other stacks

Generate your Laravel AGENTS.md

Detect your stack, tune the guardrails, export to every agent format. Free.

Open the generator