n8n
n8n-io/n8n/AGENTS.md
voice, and one instruction for each sentence - **JSDoc on `@Env(...)` config properties is public documentation.** The docs team exports these comments into the environment variable reference on docs.n8n.io. Write them
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
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.
n8n-io/n8n/AGENTS.md
voice, and one instruction for each sentence - **JSDoc on `@Env(...)` config properties is public documentation.** The docs team exports these comments into the environment variable reference on docs.n8n.io. Write them
instructkr/claude-code/AGENTS.md
file changes (path filters) - CI clippy job runs without `-D warnings` — weaker than the documented gate; known pre-existing failures recorded in docs/g002/g003 maps - `claw acp` is a status stub
3 projects use a version of this
microsoft/vscode/src/vs/platform/agentHost/AGENTS.md
Multi-Chat Architecture > Node runtime service construction is documented separately in [`node/serviceBootstrapping.md`](node/serviceBootstrapping.md). Host startup timings, process-lifetime correlation, and session workload counts are documented in [`PERFORMANCE.md`](PERFORMANCE.md). > **Status: COMPLETE
microsoft/vscode/src/vs/platform/agentHost/node/copilot/prompts/AGENTS.md
tools registered by Agent Host. This internal debugging setting assumes those values use the documented string shape. > **Launch-time freeze.** The SDK accepts a system message only at session create/resume
avelino/awesome-go/AGENTS.md
awesome-go · LLM Contribution Guide This document summarizes the project context and the conventions that language models must follow when helping on this repository. ## Project Snapshot - Purpose: maintain the curated
Significant-Gravitas/AutoGPT/AGENTS.md
autogpt_platform/frontend` – Next.js + Typescript frontend. - `autogpt_platform/docker-compose.yml` – development stack. See `docs/platform/getting-started.md` for setup instructions. ## Documentation - `docs/home/`, `docs/platform/` and `docs/integrations/` are the public docs site (agpt.co/docs). Only pages written
Steady3 mentions in 2 weeks
No other project uses it yet
Significant-Gravitas/AutoGPT/autogpt_platform/AGENTS.md
support - **Frontend** (`frontend`): Next.js React application - **Shared Libraries** (`autogpt_libs`): Common Python utilities ## Component Documentation - **Backend**: See @backend/AGENTS.md for backend-specific commands, architecture, and development tasks - **Frontend**: See @frontend/AGENTS.md
Significant-Gravitas/AutoGPT/.claude/skills/vercel-react-best-practices/AGENTS.md
React Best Practices **Version 1.0.0** Vercel Engineering January 2026 > **Note:** > This document is mainly for agents and LLMs to follow when maintaining, > generating, or refactoring React and Next.js codebases
Steady3 mentions in 2 weeks
8 projects use a version of this
Significant-Gravitas/AutoGPT/docs/AGENTS.md
Documentation Guidelines ## Where a Document Goes - **Published pages** live in `docs/home/`, `docs/platform/` and `docs/integrations/`. GitBook publishes them at agpt.co/docs, and a page appears on the site once that folder
Steady3 mentions in 2 weeks
No other project uses it yet
langgenius/dify/api/AGENTS.md
testing) when adding or moving unit tests. ## Architecture And Boundaries Read all backend architecture documentation before modifying backend code: - [Backend architecture][architecture] - [Repositories][repositories] - [SQLAlchemy][sqlalchemy] - [Database schema][db-schema
langgenius/dify/cli/AGENTS.md
commands`) own state. A plugin's `build()` closes over its own cache or loaded document; nothing outside a plugin reaches into another plugin's internals. Outside a plugin folder, import
No other project uses it yet
langgenius/dify/dify-agent/AGENTS.md
package's `uv` environment and Pydantic v2 APIs. Inspect current dependency source or official documentation before integrating, implementing, or mocking an API whose runtime contract is not established locally. ## Tests
langflow-ai/langflow/AGENTS.md
Reference any issues fixed (e.g., `Fixes #1234`) - Ensure all tests pass before submitting ## Documentation Documentation uses Docusaurus and lives in `docs/`: ```bash cd docs yarn install yarn start # Dev server
Steady6 mentions in 2 weeks
No other project uses it yet
langchain-ai/langchain/AGENTS.md
Global development guidelines for the LangChain monorepo This document provides context to understand the LangChain Python project and assist with development. ## Corridor security analysis When Corridor's `analyzePlan` tool
No other project uses it yet
comfyanonymous/ComfyUI/AGENTS.md
Avoid caller-side unwrapping such as `out = out[0]` unless the called interface is documented to return that structure. ## Autograd and Model Freezing - Do not add `torch.no_grad`, `torch.inference_mode
1 project uses a version of this
vercel/next.js/AGENTS.md
crates for Next.js SWC bindings ├── test/ # All test suites ├── examples/ # Example Next.js applications ├── docs/ # Documentation └── scripts/ # Build and maintenance scripts ``` ### Core Package: `packages/next` The main Next.js framework lives in `packages/next
vercel/next.js/test/AGENTS.md
specific to self-hosted behavior; even then, prefer an explicit deploy-mode assertion that documents the different deployed semantics. - During code review, flag any new hardcoded cache
yangshun/tech-interview-handbook/AGENTS.md
tools can be checked using `vp --version`. This is useful when researching documentation, features, and bugs. ## Common Pitfalls - **Using the package manager directly:** Do not use pnpm, npm, or Yarn
1 project uses a version of this
microsoft/PowerToys/AGENTS.md
Top-level AI contributor guidance for developing PowerToys - a collection of Windows productivity utilities
garrytan/gstack/AGENTS.md
queue. | | `/document-release` | Audit relevant docs before final verification on every ship; also supports standalone documentation updates. | | `/document-generate` | Generate Diataxis docs (tutorial / how-to / reference / explanation) from code. | | `/setup-deploy` | One-time
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.