Agent rule pattern
Per-package AGENTS.md files with a clear order of precedence.
The root file covers the whole repository; files beside the code add local rules. Projects with overlapping files state which one wins.
Keep shared rules at the root and local rules beside the code. Explain how to find the applicable files and which one wins when they conflict.
Three instruction sources are ranked in the opening lines: explicit human instructions, then the nearest nested AGENTS.md, then this file. The conflict case is answered before any rule is given.
Source excerpt starting at line 5.Apply all relevant instruction files. If instructions conflict, resolve them inthis order: 1. Explicit human instructions2. Nearest nested `AGENTS.md`3. This file
Scope follows the responsibility being changed, including callers outside its directory. The root links channel, plugin, agent, gateway, UI, testing, release, and security documentation.
Source excerpt starting at line 6.authorization boundaries still apply. Read the nearest scoped `AGENTS.md` and thematching references below, including when changing callers outside an owner's directory.
Airflowapache/airflow
DuckDBRoute extension changes by ownership boundary
GitButlerA numbered precedence order
Mem0Route by the edited package before running tools
OpenClawRoute callers to the owner's guide
Pydantic AIUse scoped guides for implementation details
RustFSKeep local invariants distinct from shared workflow
Storybookstorybookjs/storybook
GitButler 
OpenClaw 
