Draft project rules for a coding agent
A short rules file (e.g. AGENTS.md) that records your project's commands, limits and conventions.
- Type
- Rules file
- Level
- Advanced
- Time
- about 20 min
Results depend on the tool, the model and what you enter.
Result preview
Example: written by our editors, not real AI output.
## Commands - Tests: python3 -m pytest - Build: python3 build.py ## Never - Do not read or print secrets, because they end up in logs. - No force push, because other people's commits get lost. ## Ask first - before adding dependencies …
Fill in
What you type stays in this browser window. We store and send nothing.
- static website generator in Python
- online shop with a React front end
- REST API for a mobile app
- internal dashboard for sales figures
- command-line tool for converting files
- Python 3.12, pytest
- Node 22, TypeScript, Vitest
- React, Vite, Playwright
- Go 1.23, go test
- Java 21, Maven, JUnit 5
- python3 -m pytest
- npm test
- pnpm test
- go test ./...
- cargo test
- python3 build.py
- npm run build
- pnpm build
- go build ./...
- cargo build --release
- do not read secrets, no force push, no new dependencies without asking
- never change the database schema without asking
- never edit generated files by hand
- no changes to payment code without a review
- keep the public API backwards compatible
Your prompt
Draft a rules file for an AI coding agent in my project. Project: [Project] Stack: [Stack] Commands: tests with [Test command], build with [Build command]. Hard limits: [Limits] Outline: 1. Project overview in three sentences. 2. Commands. 3. Code style and conventions. 4. What the agent must never do. 5. When it must ask first. No more than 60 lines, in Markdown, concrete rules instead of general advice.
Matching tools
Tools from our catalog that this prompt works well with.
- Claude Code Prices and limits
- OpenAI Codex Prices and limits
- Cursor Prices and limits
How to use it
- Fill in the fields with your project's real commands.
- Generate the draft and delete anything that is wrong or too generic.
- Save the file under the name your agent reads; the tool's documentation tells you which.
- After a few tasks, check which rule is missing or ignored and add it.
Works in these tools
Prompts work in many chat and generator tools. This selection comes from our catalog; prices as shown on the tool page.
- Claude Code Prices on the tool page
- OpenAI Codex Free plan
- Cursor Free planfrom 8 USD per month
- GitHub Copilot Free planfrom $10
Why does this work?
Agents work more reliably with a few checkable rules than with long prose. Commands and limits up front prevent the most common mistakes.
Tips
- Write rules as an instruction with a reason: “Never X, because Y.” That helps the agent with edge cases.
- Link to existing documents instead of copying them into the rules file.