AGENTS.md examples from real projects

MudBlazorAGENTS.md

MudBlazor

MudBlazor/MudBlazor/AGENTS.md

changes, run a normal scoped build without `SkipBunCompile` for the affected project so the frontend asset pipeline runs. ### Default local loop for C# or Razor component changes - For a single

yugabyteAGENTS.md

yugabyte-db

yugabyte/yugabyte-db/AGENTS.md

functions | | `cloud/` | Docker, Kubernetes, and Grafana deployment configurations | | `yugabyted-ui/` | Yugabyted web UI (React frontend + Go API server) | | `architecture/` | Internal design documents and architecture specs | | `troubleshoot/` | Troubleshooting framework backend

No other project uses it yet

woocommerceAGENTS.md

woocommerce

woocommerce/woocommerce/AGENTS.md

tests/php/ # PHPUnit tests │ ├── includes/ # Tests for legacy code │ └── src/ # Tests for modern code └── client/ # Frontend applications └── admin/ # Admin React app ``` ### Key Architectural Concepts **Modern vs Legacy Code:** - `plugins/woocommerce/src/` - Modern

chaitinAGENTS.md

PandaWiki

chaitin/PandaWiki/AGENTS.md

Repository Layout - `backend/`: Go backend services, APIs, workers, migrations, docs. - `web/`: pnpm workspace for frontend apps. - `web/admin/`: React + Vite admin console. - `web/app/`: Next.js user-facing web app. - `sdk/`: SDK-related

jeffvliAGENTS.md

feishin

jeffvli/feishin/AGENTS.md

/shared/hooks`. Read `docs/agents/mantine.md` only when debugging those wrappers or adding a new wrapped component/hook. ### Frontend Renderer UI (imports, composition, CSS Modules, theme, i18n/icons/toasts/modals, Zustand): read `docs/agents/frontend.md` when writing or changing

hackjutsuAGENTS.md

Lepton

hackjutsu/Lepton/AGENTS.md

tagging, markdown/Jupyter notebook support, and GitHub Enterprise integration. ## Tech Stack - **Framework**: Electron (desktop app) - **Frontend**: React 19 + Redux (with Redux Thunk for async actions) - **Build System**: Webpack + Babel (ES6 transpilation

fossasiaAGENTS.md

visdom

fossasia/visdom/AGENTS.md

AGENTS instructions Visdom: Python client + Tornado server + React frontend for live data visualization. Version `0.3.1` · Python >= 3.12 · Apache 2.0 ## Setup - Install Python: `pip install -e . && pip install -r test-requirements.txt` - Build

greatfrontendAGENTS.md

top-javascript-interview-questions

greatfrontend/top-javascript-interview-questions/AGENTS.md

Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite

zhouxiaokaAGENTS.md

autoclip

zhouxiaoka/autoclip/AGENTS.md

release requires all groups and the exact tag's CI. - Python correctness lint, frontend lint/types/tests/build, backend tests, version/readme contracts and release-gate regressions are blocking. Existing general Python style warnings

pycaretAGENTS.md

pycaret

pycaret/pycaret/AGENTS.md

server suite: `uv run --package pycaret-server pytest services/api/tests/ -q`. ### Add a new frontend screen 1. Add the typed endpoint(s) to `apps/web/src/api/endpoints.ts` and the response types to `apps/web/src/api/types.ts

spinnakerAGENTS.md

spinnaker

spinnaker/spinnaker/AGENTS.md

unified development. ## Architecture - **Type:** Monorepo with Gradle composite builds - **Backend:** Java/Kotlin (Spring Boot microservices) - **Frontend:** TypeScript/React (Deck, including `deck/packages/kayenta`) - **Build System:** Gradle (backend), pnpm/Webpack (frontend) - **Storage:** Redis (queues/caching), MySQL/SQL (persistence

francescopaceAGENTS.md

espectre

francescopace/espectre/AGENTS.md

capability schemas; engine-level semantic parity alone is insufficient. - Enforce the dependency direction `Frontend -> Runtime -> Core`; lower layers must not include, query, or call higher layers. - Do not modify

No other project uses it yet

francescopaceAGENTS.md

espectre

francescopace/espectre/docs/AGENTS.md

owner instead of repeating mutable formulas, metrics, commands, or corpus data. - Keep frontend-specific setup and firmware workflows in the local frontend README files; link to `API.md` and `DISCOVERY.md

No other project uses it yet

open-pencilAGENTS.md

open-pencil / desktop

open-pencil/open-pencil/desktop/AGENTS.md

WebView sees the key, so plain and Shift-only keys stay with the frontend's shortcuts, which skip text fields (`menu::tests` in `desktop/src/menu/mod.rs`). - A menu or menu entry with

xorbitsaiAGENTS.md

inference

xorbitsai/inference/AGENTS.md

tests. - `xinference/api/`: API server and OpenAI-compatible routes. - `xinference/client/`: sync and async Python clients. - `frontend/`: Next.js Web UI. - `doc/source/`: Sphinx documentation. - `.github/workflows/python.yaml`: main lint and test CI. ## Working Rules - Prefer

cadence-workflowAGENTS.md

cadence

cadence-workflow/cadence/AGENTS.md

CONTRIBUTING.md](CONTRIBUTING.md). ## Repository layout A Cadence server cluster is composed of four different services: Frontend, Matching, History and Worker(system). Here's what's in each top-level directory

No other project uses it yet

LearningCircuitAGENTS.md

local-deep-research

LearningCircuit/local-deep-research/AGENTS.md

Local Deep Research is a Python/PDM application with a FastAPI backend and a Vite frontend. Backend source is in `src/local_deep_research/`; web code is in `src/local_deep_research/web/`; tests are in `tests/`. `src/local_deep_research/web/app.py

risingwavelabsAGENTS.md

risingwave

risingwavelabs/risingwave/AGENTS.md

Stream compute engine 4. `batch` - Batch compute engine for queries against materialized views 5. `frontend` - SQL query planner and scheduler 6. `storage` - Cloud native storage engine 7. `meta` - Meta engine

wealthfolioAGENTS.md

wealthfolio

wealthfolio/wealthfolio/AGENTS.md

instructions for agents working on Wealthfolio, a local-first finance app with a React frontend, Tauri desktop/mobile runtime, and Axum web server. ## Working agreements - Resolve routine implementation choices from nearby

caorushiziAGENTS.md

mediago

caorushizi/mediago/AGENTS.md

apps/` (`core` for the Go backend, `electron` for desktop, `ui` for the shared frontend, `player-ui` for playback). Reusable logic stays in `packages/`, including `common`, `core-sdk`, `electron-preload