awesome-wechat-weapp
justjavac/awesome-wechat-weapp/AGENTS.md
deploy:check npm run integrations:verify npm run db:verify npm run db:import:test npm run advisor:test npm run doctor:test npm run cli:test npm run deployment
No other project uses it yet
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.
justjavac/awesome-wechat-weapp/AGENTS.md
deploy:check npm run integrations:verify npm run db:verify npm run db:import:test npm run advisor:test npm run doctor:test npm run cli:test npm run deployment
No other project uses it yet
cypress-io/cypress/AGENTS.md
Cypress Monorepo — AGENTS.md ## Overview Cypress is an open-source end-to-end and component testing framework for the modern web. This monorepo ships the Cypress desktop application and CLI (`cypress
No other project uses it yet
cypress-io/cypress/.circleci/AGENTS.md
main-branch CI — in particular: - **Windows jobs** — the `windows` workflow (`windows-v8-integration-tests`, `windows-create-build-artifacts`, etc.) - **V8 snapshot / packaging tooling** — `v8-integration-tests` on Linux, macOS
No other project uses it yet
cypress-io/cypress/cli/AGENTS.md
package — the user-facing CLI and programmatic API — plus the first-party component-testing mount adapters that ship bundled inside it. This is the top-level package users install
No other project uses it yet
cypress-io/cypress/npm/AGENTS.md
directory contains the publicly published npm packages for the Cypress ecosystem, including component testing adapters for each supported UI framework, bundler integrations that power the component testing dev server
cypress-io/cypress/packages/AGENTS.md
that make up the Cypress monorepo. These packages are the implementation of the Cypress test runner, its tooling, and supporting infrastructure. Each package is a standalone npm package (scoped under
cypress-io/cypress/scripts/AGENTS.md
electron-builder packaging), `upload.js` / `upload-build-artifact.js` (S3 upload), `move-binaries.ts` (post-release artifact moves), `smoke.js` (smoke-test the built binary), `zip.js` (zip/unzip), `util/` (packages manifest, upload helpers, CloudFlare cache purge) - `semantic-commits
cypress-io/cypress/system-tests/AGENTS.md
This workspace (`@tooling/system-tests`) contains Cypress's suite of system (integration) tests. Each test launches the real Cypress server process against a self-contained project fixture and asserts on stdout, exit
cypress-io/cypress/tooling/AGENTS.md
pattern: ```sh yarn workspace @tooling/ build # Compile TypeScript to dist/ # Run a specific unit test file (mocha packages) yarn workspace @tooling/ test-unit -- --grep " " yarn workspace @tooling/ test-unit
chenglou/pretext/AGENTS.md
breaks may be taken for speed, with a named gap. CJK stays well supported. - **Tests And Losses.** A lost pass may be luck or a wrong oracle; a true loss
No other project uses it yet
KRTirtho/spotube/AGENTS.md
Pnightly=true`. - Module checks: `:composeApp:check`, `:plugin_interfaces:check`, `:js_plugin_example:check` - Focused tests: `:composeApp:jvmTest`, `:composeApp:iosSimulatorArm64Test`, `:plugin_interfaces:jvmTest`, `:plugin_interfaces:jsTest`, `:js_plugin_example:jsTest
No other project uses it yet
TanStack/query/AGENTS.md
core change is necessary when a local correction cannot work. - Read relevant tests and previous fixes before changing behavior. Preserve intentional behavior and compatibility. Identify breaking behavior changes even when
No other project uses it yet
pandas-dev/pandas/AGENTS.md
uses Pixi and tasks defined in [pixi.toml](pixi.toml) for all workflows (building pandas, testing, type checking, building documentation, running benchmarks). Linting checks require [pre-commit](https://pre-commit.com/), installed
No other project uses it yet
mudler/LocalAI/AGENTS.md
AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]`. - **The human submitter is responsible** for reviewing, testing, and understanding every line of generated code. ## Topics | File | When to read | |------|-------------| | [.agents/ai-coding-assistants.md](.agents/ai-coding-assistants.md) | Policy
Steady3 mentions in 2 weeks
No other project uses it yet
metabase/metabase/AGENTS.md
clojure-mcp tools - **[clojure-eval](.claude/skills/clojure-eval/SKILL.md)** - Always use this to evaluate Clojure code, **run tests**, and verify edits/compile. Prefer this over shell commands. - **[clojure-write](.claude/skills/clojure-write/SKILL.md)** - Clojure/ClojureScript development with REPL
No other project uses it yet
metabase/metabase/frontend/AGENTS.md
Enterprise embedding code: `enterprise/frontend/src/embedding`, `enterprise/frontend/src/embedding-sdk-ee`, and `enterprise/frontend/src/embedding-sdk-package` - Custom visualization enterprise code: `enterprise/frontend/src/custom-viz` - Jest unit tests: colocated next to the files they test - Jest test support and mocks: `frontend/test` - Cypress
No other project uses it yet
Homebrew/brew/AGENTS.md
Agent Instructions for Homebrew/brew Run `./bin/brew lgtm --online` (style checks, type checks and tests) to verify file edits before finishing. Inline any new or existing methods or variables used only
No other project uses it yet
Homebrew/brew/docs/AGENTS.md
exec rake lint` - `HOMEBREW_NO_AUTO_UPDATE=1 brew bundle exec bundle exec rake test` Also run these from the repository root when docs content changes: - `rg --files docs
No other project uses it yet
HKUDS/nanobot/AGENTS.md
share that runtime; keep execution and policy out of the clients. WebUI/gateway support and test coverage are limited to same-version combinations, including remote gateways. Cross-version combinations may work
Steady4 mentions in 2 weeks
No other project uses it yet
calcom/cal.com/AGENTS.md
always run before pushing) yarn biome check --write . # Lint and format TZ=UTC yarn test # Run unit tests yarn prisma generate # Regenerate types after schema changes ``` ## Boundaries ### Always
1 project uses a version of this
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.