cli-docs
AGENTS.md1 starsChanged 5 days agoApache-2.0View on GitHub
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices. This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree…
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- blog-tagsSkill
- html-reportSkill
- release-announcementSkill
- wirecat-documentationSkill
The file
Files
<!-- BEGIN:nextjs-agent-rules -->This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices.
This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
<!-- END:nextjs-agent-rules -->Documentation work
Before writing or reviewing documentation, read docs/AUTHORING.md. Also read docs/TERMINOLOGY.md and follow docs/REVIEWING.md for every documentation PR or release update. Every user guide opens with its use case and the result the reader will get. Keep titles short, preserve reviewed release facts, and give every sidebar page a relevant decorative icon. Read docs/STRUCTURE.md for source ownership; generated messenger pages are not edited directly.
For routine local documentation edits, follow docs/DEVELOPMENT.md: use the browser smoke suite and targeted checks. Full export and browser coverage run before each deployment and monthly, not on pull requests.
Security
Security audits of this repository follow the shared security method in cli-testing; vulnerabilities are reported as the security policy says.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.