How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
magnitudedevAGENTS.mdmagnitudedev/magnitude/design/AGENTS.md
Design ## Design Content These design documents are the high-level source of truth for Magnitude's product and code. They describe definitions, models, and policies that represent the desired semantic
NVIDIAAGENTS.mdNVIDIA/cuml/cpp/agents.md
internal_stream(idx)` - Concurrent operations (multi-GPU, async ops) must have dedicated streams - Clearly document stream lifecycle (who creates, who destroys) **Threading**: - Only OpenMP is allowed for host threading - Algorithms
NVIDIAAGENTS.mdNVIDIA/cuml/python/agents.md
pickle.loads`) - Insufficient error handling exposing internal details - Missing bounds checking allowing resource exhaustion ### Documentation - Missing or incorrect docstrings for public methods - Hyperparameters not documented - Missing scikit-learn compatibility notes
CloudflareAGENTS.mdcloudflare/cloudflare-docs/AGENTS.md
developers.cloudflare.com](https://developers.cloudflare.com). It is an **Astro** site using the **Nimbus** (`nimbus-docs`) documentation framework. Content is authored in **MDX** (Markdown + JSX). The site is deployed as a Cloudflare Worker
tinyplexAGENTS.mdtinyplex/tinybase/agents.md
runtime dependencies, and maintains 100% test coverage. - **Website**: https://tinybase.org - **Repository**: https://github.com/tinyplex/tinybase - **Documentation**: https://tinybase.org/api/ - **License**: MIT - **Author**: James Pearce (@jamesgpearce) ## Using TinyBase In An Application When
iflytekAGENTS.mdiflytek/skillhub/AGENTS.md
schema.d.ts # Generated OpenAPI types (CHECKED IN) │ │ ├── app/ # Router, layout, global providers │ │ ├── docs/ # In-app documentation pages │ │ ├── entities/ # Domain entity display logic │ │ │ ├── skill/ # Skill card, detail components │ │ │ ├── user/ # User profile components
Model Context ProtocolAGENTS.mdmodelcontextprotocol/go-sdk/AGENTS.md
comments to the code unless they are really necessary: - Prefer self-documenting code. - Focus on the "why" not the "what" in comments. ### Documentation - **README.md**: Do NOT edit `README.md` directly
aipochAGENTS.mdaipoch/open-science/AGENTS.md
status-info` / `status-warning` / `status-failure` token families registered in `main.css` and documented in `docs/design.md` — do not reintroduce inline `oklch()`/hex values. - `title`, `description`, `errorCode` - `help` — `{ whyLabel, why, howLabel
tiannAGENTS.mdtiann/hapi/AGENTS.md
change's impact, not by the number of workflow steps: | Change | Verification | |--------|--------------| | Documentation only | Check edited content, local links, and diff; no code test suite. | | Package-local code | Relevant tests
clideyAGENTS.mdclidey/whodb/AGENTS.md
dbType ==` in shared code. All database-specific logic goes in plugins. See `.agents/docs/plugin-architecture.md` 4. **Documentation requirements** - All exported Go functions/types need doc comments. All exported TypeScript functions/components need JSDoc
MistralAGENTS.mdmistralai/mistral-vibe/AGENTS.md
feature changes or additions. - Keep the builtin Vibe Skill (`vibe/core/skills/builtins/vibe.py`) up-to-date. It documents the CLI's features, such as args, flags, config options and persistence, commands, built
WaishnavAGENTS.mdWaishnav/devspace/AGENTS.md
tool-surface filtering; - widgets, artifacts, and review checkpoints; - persistence and migrations; - packaged entry points, documentation, and examples. This is a map, not a requirement to touch every surface on every
MicrosoftAGENTS.mdmicrosoft/poml/AGENTS.md
JS/TS code. - **python/** – Python SDK and CLI implementation. - **examples/** – Sample POML files. - **docs/** – Project documentation. ## Environment Setup - **Node.js**: version 22.x (20.x should also work) - **Python**: version
qixing-jkAGENTS.mdqixing-jk/all-api-hub/AGENTS.md
language. - Sponsor catalog changes or audits use the project `sponsor-catalog` skill, not ordinary documentation edits. - Development setup, test harnesses, or hook troubleshooting: [CONTRIBUTING.md](CONTRIBUTING.md). Commands and versions belong
nguyenphutrongAGENTS.mdnguyenphutrong/quotio/AGENTS.md
owning app directory. ## Commands Run commands from the repository root unless a project document says otherwise. ```bash swift test --package-path Packages/QuotioCore ./apps/macos/scripts/check_architecture.sh xcodebuild -project apps/macos/Quotio.xcodeproj -scheme Quotio -configuration Debug
AWSAGENTS.mdawslabs/aidlc-workflows/AGENTS.md
docs/guide/` (User Guide), `docs/harness-engineering/` (Harness Engineer Guide), and `docs/reference/` (Developer Reference) for full documentation ## Test Suite Run `bash tests/run-tests.sh --help` for levels and flags. See `docs/reference/09-testing.md` for full strategy. ## Utility
homeassistant-aiAGENTS.mdhomeassistant-ai/ha-mcp/AGENTS.md
only. - This root file owns repository-wide behavior, permissions, scope, and testing policy. Linked documents own topic-specific detail. - Before working, read every applicable `AGENTS.md` from the repository root through
MicrosoftAGENTS.mdmicrosoft/fluentui-blazor/AGENTS.md
Main Package**: `Microsoft.FluentUI.AspNetCore.Components` - **Target Framework**: .NET 8+ - **License**: MIT - **Language**: C# with Razor components - **Documentation**: https://www.fluentui-blazor.net ## Repository Structure ``` src/ ├── Core/ # Main component library ├── Core.Scripts/ # TypeScript/JavaScript for web components └── Extensions
Agenta-AIAGENTS.mdAgenta-AI/agenta/web/AGENTS.md
line?" — if not, cut it. Longer comments only for a genuinely surprising constraint (documented bug, race, ordering requirement), and even then a sentence or two max. ## Packages, entities, and code
jakubkrehelAGENTS.mdjakubkrehel/skills/AGENTS.md
Claude Code plugin `interfaces` served by the marketplace in this same repository. It is documentation-only; there is no build, lint, or test tooling. `.claude-plugin/plugin.json` and `.claude-plugin
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.
