onnxruntime
microsoft/onnxruntime/AGENTS.md
that is not clear from the immediate context. Do not narrate obvious code or document the sequence of approaches taken to reach the current implementation; that history belongs
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
microsoft/onnxruntime/AGENTS.md
that is not clear from the immediate context. Do not narrate obvious code or document the sequence of approaches taken to reach the current implementation; that history belongs
google/adk-python/AGENTS.md
invocation lifecycle, please refer to the `adk-architecture` skill and the referenced documentation therein. ## ADK Knowledge, Architecture, and Style Skills related to ADK development are in `.agents/skills/`. ## Project Architecture
github/docs/content/copilot/responsible-use/agents.md
agent can implement incremental feature requests, develop additional test suites, and create or update documentation. * **Prototyping new projects**: The cloud agent and Copilot CLI can greenfield new concepts, helping developers
JetBrains/intellij-community/AGENTS.md
www.asd-ste100.org/), and keep it short. This covers a comment, KDoc, a commit message, documentation, a spec, and a report to the user. Use the active voice and a simple
google/filament/AGENTS.md
Filament AI Coding & Agent Guidelines This document defines machine-readable instructions and technical guardrails for AI coding assistants, agents, and LLMs working on the Filament repository. All AI-generated code
microsoft/fluentui/AGENTS.md
docs/architecture/design-tokens.md). 2. **Never use `React.FC`.** Always use `ForwardRefComponent` with `React.forwardRef`. 3. **Never access `window`, `document`, or `navigator` directly.** In v9 components, use `useFluent_unstable()` to get `targetDocument` and `targetDocument.defaultView` instead
pydantic/pydantic-ai/AGENTS.md
project and its users Being an open source library, the public API, abstractions, documentation, and the code itself _are_ the product and deserve careful consideration, as much as the functionality
pydantic/pydantic-ai/docs/AGENTS.md
docs/` guidelines Follow the general [documentation guidance](../agent_docs/documentation.md). These rules cover published Markdown under `docs/`. ## Links and structure - Use reference-style links for API elements: `[ElementName][module.path.ElementName]`. They provide hover
pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/AGENTS.md
check time and improve IDE autocomplete; when `Any` is unavoidable due to external constraints, document expected structure in docstrings - Use `TypedDict` or dataclass instead of `dict[str, Any]` when structure
pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/durable_exec/AGENTS.md
once if the process fails after the side effect but before its checkpoint commits. Document the engine's guarantees and require idempotency or expose an engine-native at-most-once
pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/models/AGENTS.md
Design - Silently ignore unsupported generic tuning settings (`temperature`, sampling params, penalties, …) at runtime and document them in docstrings — a model that simply no-ops an unsupported knob keeps client code
pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/native_tools/AGENTS.md
there; model settings remain as an alternative for backward compat - Provider support must be documented in three places: the tool class docstring 'Supported by' list, `docs/native-tools.md` provider table, and field
pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/ui/AGENTS.md
that way — see [7106](https://github.com/pydantic/pydantic-ai/pull/7106#discussion_r3723844005), which closed [7105](https://github.com/pydantic/pydantic-ai/issues/7105) by documenting the wiring instead of exposing `AGUIAdapter.context`. A field earns an adapter property when **both** hold
pydantic/pydantic-ai/src/pydantic_ai_harness/AGENTS.md
reference When implementing a new capability, reference these docs: - <https://pydantic.dev/docs/ai/capabilities/overview/> -- main capabilities documentation, usage patterns, built-in capabilities - <https://pydantic.dev/docs/ai/core-concepts/hooks/> -- lifecycle hooks reference, hook ordering, all hook
pydantic/pydantic-ai/src/pydantic_clai2/AGENTS.md
code review. 3. Fire it from exactly one place in the shell. 4. Document it in `PLUGINS.md` in the table it belongs to. ## The `/plugins`, `/set`, `/theme`, `/model`, and `/add_model
huggingface/trl/.ai/AGENTS.md
function, parameter, or branch is maintenance burden. The best abstraction is often no abstraction. ## Documentation ### Docstrings Docstrings must follow the repository format below. Do **not** convert docstrings to other styles
nukeop/nuclear/AGENTS.md
demos - `@nuclearplayer/videos` - Remotion videos rendered from UI components - `@nuclearplayer/tools` - Build and maintenance utilities - `@nuclearplayer/docs` - Documentation - `@nuclearplayer/website` - Project website (Astro) ## Commands ```bash # Development pnpm dev # Run player in dev mode pnpm
rowboatlabs/rowboat/AGENTS.md
with the date and the decision or PR they implement. The code says what. - Documents own one kind of fact each and link to each other rather than restate. There
AgriciDaniel/claude-seo/AGENTS.md
docs.x.ai/build/features/skills-plugins-marketplaces). | | **OpenAI Codex CLI** | Reads `AGENTS.md` from project root. Bash tools work as documented; some Claude-specific tool names (Read/Write/Edit) are aliased to Codex equivalents transparently. | | **Cline** | Loads `AGENTS.md
GoogleCloudPlatform/generative-ai/search/gemini-enterprise/group-licensing/AGENTS.md
this codebase**, any skill, agent, or subagent **MUST first read the service Technical Design Document (TDD)** located at [docs/TDD.md](file:///usr/local/google/home/williamsmt/Projects/development/generative-ai/search/gemini-enterprise/group-licensing/docs/TDD.md) (in the `docs/` subdirectory). This document contains the definitive
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.