AGENTS.md examples from real projects

avelinoAGENTS.md

awesome-go

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

No other project uses it yet

Significant-GravitasAGENTS.md

AutoGPT

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

No other project uses it yet

Significant-GravitasAGENTS.md

AutoGPT / vercel-react-best-practices

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

Significant-GravitasAGENTS.md

AutoGPT

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

No other project uses it yet

langgeniusAGENTS.md

dify / api

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

No other project uses it yet

langgeniusAGENTS.md

dify / cli

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

langgeniusAGENTS.md

dify / dify-agent

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-aiAGENTS.md

langflow

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

comfyanonymousAGENTS.md

ComfyUI

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

VercelAGENTS.md

next.js / test

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

No other project uses it yet

yangshunAGENTS.md

tech-interview-handbook

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

MicrosoftAGENTS.md

PowerToys

microsoft/PowerToys/AGENTS.md

Top-level AI contributor guidance for developing PowerToys - a collection of Windows productivity utilities

No other project uses it yet

ggml-orgAGENTS.md

llama.cpp

ggml-org/llama.cpp/AGENTS.md

human-written code - Mechanical tasks: formatting, repetitive patterns, completing code from established designs - Documentation drafts for components the contributor already understands - Writing code from a design the contributor owns Agents

No other project uses it yet

OpenAIAGENTS.md

codex / bottom_pane

openai/codex/codex-rs/tui/src/bottom_pane/AGENTS.md

explanation of the current behavior. - Keep implementations/docstrings aligned unless a divergence is intentional and documented. Practical check: - After edits, sanity-check that docs mention only APIs/behavior that exist in code

No other project uses it yet

rustdeskAGENTS.md

rustdesk

rustdesk/rustdesk/AGENTS.md

restructure, and the code already fails cleanly there or behaves as master does, document it as a known limit in the PR instead. Anything beyond the easy fix needs

No other project uses it yet

reactAGENTS.md

react-native

react/react-native/AGENTS.md

declare export`. Declare only the surface the repo calls, typed as the package documents it, never `any`. - Check with `yarn flow-check`, and drop the libdef with the last

rust-langAGENTS.md

rust

rust-lang/rust/AGENTS.md

first edit under this exemption, state once that the resulting code, comments, and documentation are LLM-generated and cannot later be contributed without arranging with a reviewer, and cite

stablyaiAGENTS.md

orca

stablyai/orca/AGENTS.md

src/renderer/src/components/ui/`. Don't invent new color values, font sizes, or shadow tiers when a documented one already covers the role. # Electron UI Validation - Always run tests and agent-launched apps

No other project uses it yet

JuliusBrusseeAGENTS.md

caveman / proxy

JuliusBrussee/caveman/proxy/AGENTS.md

# proxy — the byte-safe standalone `caveman` proxy (commercial, binary-distributed) A base-URL-swap

No other project uses it yet

MicrosoftAGENTS.md

v8-jsi / nodejs

microsoft/v8-jsi/deps/nodejs/AGENTS.md

Agents and Automated Tools This document outlines rules and requirements for AI automation agents and automated tooling that interact with the Node.js project. Existing Node.js collaborators (as listed