saleor
saleor/saleor/AGENTS.md
post_migrate` signal used to trigger data-migration tasks — see Data Migrations below.) # Code style - Use global import statements. Place all imports at the top of the file rather than
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.
saleor/saleor/AGENTS.md
post_migrate` signal used to trigger data-migration tasks — see Data Migrations below.) # Code style - Use global import statements. Place all imports at the top of the file rather than
pubkey/rxdb/AGENTS.md
messages in production builds. Use the error codes from `src/rx-error.ts` and add new error codes if needed like `PL1`, `PL2`. Example: `throw newRxError('PL1', { plugin });` ## Documentation Style - SHOULD use clear
marimo-team/marimo/AGENTS.md
users Being an open source library, the public API, abstractions, documentation, and the code itself are the product and deserve careful consideration. When working in this repository, you should consider
No other project uses it yet
johannesjo/super-productivity/AGENTS.md
Angular + Electron + Capacitor. ## Repo map Start with the [repository content map](docs/repository-map.md) (task keywords, code entry points, focused tests) and follow only the relevant links. Layer boundaries: [app map](src/app/README.md
oxc-project/oxc/AGENTS.md
quality or unreviewed AI content will be closed immediately All AI-generated code must be thoroughly reviewed, tested, and understood by the contributor before submission. Code should meet
czlonkowski/n8n-mcp/AGENTS.md
every code change and `npm run build` after MCP server changes. - After rebuilding server code, ask the user to reload the MCP server before testing the changed MCP behavior. - Name
Steady19 mentions in 2 weeks
No other project uses it yet
comet-ml/opik/AGENTS.md
ignore this directory and use `.agents/` as the canonical source. - `.github/copilot-instructions.md` is GitHub Copilot code review guidance only. ## Security & Configuration Tips - Keep secrets and API keys out of source control
Steady19 mentions in 2 weeks
No other project uses it yet
2025Emma/vibe-coding-cn/AGENTS.md
提示词转换:进入 `libs/external/prompts-library/` 后执行 `python main.py` 按交互提示进行转换,运行前请确认虚拟环境、依赖与输出目录,并在完成后检查生成 Markdown 是否符合 lint 规则。 ## Coding Style & Naming Conventions - 文字层:文档、注释、日志使用中文;代码符号(函数 / 变量 / 模块)统一英文且语义直白,避免晦涩缩写。 - 缩进与排版:全仓保持空格缩进
steipete/CodexBar/AGENTS.md
cold-build comparison, or maintainer-requested cleanup. - Run focused tests during development; the final code needs focused tests plus `make check`, with the full suite from
Steady11 mentions in 2 weeks
No other project uses it yet
mochajs/mocha/AGENTS.md
node runtime behavior, include smoke + targeted node suite. ### CJS to ESM migration conventions (runtime code) - Scope: prioritize runtime modules under `lib/`; do not include test fixtures unless explicitly requested
NVIDIA/NemoClaw/AGENTS.md
rerun affected checks without asking at each step. Continue into PR publication and review follow-up when requested. A first patch or lifecycle handoff is not completion. Keep local verification
NVIDIA/NemoClaw/docs/AGENTS.md
review documentation. This file owns agent-specific documentation routing and workflow. - Write clear, accurate, task-oriented documentation for developers who run NemoClaw with OpenClaw, Hermes, LangChain Deep Agents Code
Steady10 mentions in 2 weeks
No other project uses it yet
NVIDIA/NemoClaw/.dsh/tools/AGENTS.md
they matter. - Prefer a direct, focused tool over overlapping projections or orchestration layers. Ordinary code review, representative harness exercises, and repository hooks are the validation boundary. Do not add repository
Steady10 mentions in 2 weeks
No other project uses it yet
NVIDIA/NemoClaw/src/lib/messaging/AGENTS.md
messaging egress opt-in unless accepted product policy states otherwise. Load `nemoclaw-maintainer-security-code-review` when the change affects credentials, public ingress, sender authorization, network policy, or another trust
Steady10 mentions in 2 weeks
No other project uses it yet
forem/forem/AGENTS.md
repetitive events. ## Testing Standards - **Regression Tests are Mandatory**: specific regression tests to verify your code works are required for almost all PRs. - **Follow Test Patterns**: Use `create(:factory)` syntax (FactoryBot
vectordotdev/vector/AGENTS.md
avoid "Co-Authored-By: Claude" attribution) - **Pull requests:** Do NOT add "Generated with Claude Code" or similar footers — keep PR descriptions focused on the technical changes ### Preserve Open Pull Request
No other project uses it yet
openobserve/openobserve/AGENTS.md
enable repo-wide); hold the code you add to this order even though nothing enforces it yet. ## Comments STRICT, and enforced in review — a comment that breaks these is deleted
PrimeIntellect-ai/prime-agent/AGENTS.md
commit scripts or tools that no workflow, Makefile target, or other code runs (one-off review, parity, or reproduction scripts). Put their results in the PR body
jhipster/generator-jhipster/AGENTS.md
composition; blueprinted sub-generators are discovered and composed in `beforeQueue`. - `lib/` holds shared, **exported** code: `lib/jdl` (Chevrotain-based JDL parser), `lib/testing` (test harness, also importable as `#testing`), `lib/utils`, `lib/eslint`, `lib/ci
Homebrew/homebrew-cask/AGENTS.md
Agent Instructions for homebrew-cask This document helps coding agents produce high-quality PRs for Homebrew Cask contributions. ## Before Any PR 1. **Check for existing PRs** for the same cask
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.