AGENTS.md examples from real projects

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

open-pencilReads credentialsAGENTS.md

open-pencil / tools

open-pencil/open-pencil/tools/AGENTS.md

rollup-plugin-license`, and fails on a license outside its allowlist (`vite/third-party-notices.ts`). The shared frontend archive refuses to form without it and the desktop Rust notices, and every stable desktop

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

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

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

maximhqReads credentialsAGENTS.md

bifrost

maximhq/bifrost/AGENTS.md

# AGENTS.md — Bifrost AI Gateway > Context for AI agents (Claude Code, Copilot, Cursor, etc.) working

No other project uses it yet

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

pacifioDeletes or force-pushesAGENTS.md

atlas

pacifio/atlas/AGENTS.md

Claude Code. Atlas is a Tauri v2 desktop app: a React 19 frontend over a Rust backend, one cargo workspace, and the agent engine under `vendor/atlas-engine/` (its crates are `atlas

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

jely2002AGENTS.md

youtube-dl-gui

jely2002/youtube-dl-gui/AGENTS.md

AGENTS ## Overview This project uses Vue 3 with TypeScript for the frontend and Rust for the backend. Vue code lives in `src/` and `src/components`, while the Rust Tauri backend lives

CloudflareReads credentialsAGENTS.md

vinext

cloudflare/vinext/AGENTS.md

# Agent Guidelines Instructions for AI agents working on this codebase. --- ## Project Overview **vinext** is

No other project uses it yet

databasusReads credentialsAGENTS.md

databasus

databasus/databasus/AGENTS.md

prose and in code - [`docs/machine-setup.md`](docs/machine-setup.md) — storage recommendations for faster local tests - [`docs/frontend-design.md`](docs/frontend-design.md) — frontend design conventions and their code owners - [`docs/frontend-localization.md`](docs/frontend-localization.md) — dictionaries, safe interpolation and regional formats - [`docs/google-drive-storage-authorization.md

databasusAGENTS.md

databasus / backend

databasus/databasus/backend/AGENTS.md

Check the work: the backend packages without the end-to-end ones and the frontend tests | | `mise run test-full` | Run all tests for the usual Docker development environment; [testing.md

databasusAGENTS.md

databasus / frontend

databasus/databasus/frontend/AGENTS.md

Frontend guidelines (React + TypeScript) This document contains coding standards for the Databasus frontend (React 19 + TypeScript + Vite + Ant Design + TailwindCSS). The rules for every module are in the root `AGENTS.md

databasusAGENTS.md

databasus / website

databasus/databasus/website/AGENTS.md

pages depend on it too: `frontend/src/shared/i18n/websitePages.ts` marks which linked pages are translated, and a frontend test (`websitePages.test.ts`) reads `TRANSLATED_PATHS` and fails when the two disagree. Adding or removing

RostislavDuginReads credentialsAGENTS.md

postgresus

RostislavDugin/postgresus/AGENTS.md

prose and in code - [`docs/machine-setup.md`](docs/machine-setup.md) — storage recommendations for faster local tests - [`docs/frontend-design.md`](docs/frontend-design.md) — frontend design conventions and their code owners - [`docs/frontend-localization.md`](docs/frontend-localization.md) — dictionaries, safe interpolation and regional formats - [`docs/google-drive-storage-authorization.md

RostislavDuginAGENTS.md

postgresus / frontend

RostislavDugin/postgresus/frontend/AGENTS.md

Frontend guidelines (React + TypeScript) This document contains coding standards for the Databasus frontend (React 19 + TypeScript + Vite + Mantine + TailwindCSS). The rules for every module are in the root `AGENTS.md`. --- ## Table