AGENTS.md examples from real projects

fossasiaAGENTS.md

visdom

fossasia/visdom/AGENTS.md

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

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

No other project uses it yet

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

hyperdxioReads credentialsAGENTS.md

hyperdx

hyperdxio/hyperdx/AGENTS.md

place. ## Architecture (WHAT) This is a **monorepo** with six packages: - `packages/app` - Next.js frontend (TypeScript, Mantine UI, TanStack Query) - `packages/api` - Express backend (Node.js 22+, MongoDB for metadata, ClickHouse for telemetry). Also

No other project uses it yet

CloudflareReads credentialsAGENTS.md

moltworker

cloudflare/moltworker/AGENTS.md

types if needed in `src/types.ts` 3. Update client API in `src/client/api.ts` if frontend needs it 4. Add tests ### Adding a New Environment Variable 1. Add to `MoltbotEnv` interface in `src/types.ts

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

pocket-idReads credentialsAGENTS.md

pocket-id

pocket-id/pocket-id/AGENTS.md

GORM, [ory/fosite fork](#backend-go)). Its own toolchain, not part of the repository. - `frontend/` — SvelteKit 5 SPA. Builds into `backend/frontend/dist` and is embedded via `go:embed`. - `tests/` — Playwright

No other project uses it yet

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

fastreplReads credentialsAGENTS.md

anarlog

fastrepl/anarlog/AGENTS.md

reproducible job, including setup and generated-file checks. | Changed component | Validation and source | | --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Desktop frontend and shared UI/editor packages | Build `@anlg/ui`, then `pnpm -F @anlg/desktop typecheck`, `pnpm -F @anlg/desktop test

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

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

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

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

SentryReads credentialsAGENTS.md

self-hosted

getsentry/self-hosted/AGENTS.md

operating surface. Product bugs belong upstream: | Problem area | Upstream repo | |---|---| | Sentry application behavior (especially frontend) | [getsentry/sentry](https://github.com/getsentry/sentry) | | Event ingestion, PII scrubbing, etc. | [getsentry/relay](https://github.com/getsentry/relay) | | Long-term

ghostfolioReads credentialsAGENTS.md

ghostfolio / nestjs-best-practices

ghostfolio/ghostfolio/.agents/skills/nestjs-best-practices/AGENTS.md

# NestJS Best Practices **Version 1.1.0** NestJS Best Practices January 2026 > **Note:** > This document is

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

open-pencilAGENTS.md

open-pencil / desktop

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

menu entry with a `feature` in the schema is built only while the frontend names that feature through `set_native_menu_features` (`src/app/shell/menu/features.ts`); every rebuild keeps the check states

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

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