AGENTS.md examples from real projects

utmappAGENTS.md

UTM

utmapp/UTM/AGENTS.md

platform/arch names, schemes, and signing: `Documentation/iOSDevelopment.md`. ## Architecture Layered: platform-independent backend (`Services/`, `Configuration/`) + SwiftUI frontend (`Platform/`). Full picture: `Documentation/Architecture.md`. Load-bearing gotchas: - **Two VM backends** behind the `UTMVirtualMachine` protocol — `UTMQemuVirtualMachine

No other project uses it yet

pingdotggReads credentialsAGENTS.md

t3code

pingdotgg/t3code/AGENTS.md

that works on the path you tested and is missing everywhere else. Before calling frontend work done, walk this list and say which entries applied: - **Entry points.** A behavior reachable

BlockReads credentialsAGENTS.md

sprout

block/sprout/AGENTS.md

cannot run in a plain browser. Use `just desktop-screenshot` to capture screenshots (builds frontend, starts preview server, runs Playwright automatically): ```bash just desktop-screenshot --name home just desktop-screenshot

cjpaisAGENTS.md

Handy

cjpais/Handy/AGENTS.md

VERSION_MINIMUM=3.5 bun run tauri dev # Build for production bun run tauri build # Frontend only development bun run dev # Start Vite dev server bun run build # Build frontend (TypeScript

No other project uses it yet

jdxReads credentialsAGENTS.md

mise

jdx/mise/AGENTS.md

libraries; those live in `packaging/e2e/Dockerfile`. `apt-get` is invoked as `sudo -n env DEBIAN_FRONTEND=noninteractive apt-get …` so the frontend reaches apt when elevation is required - installs and defaults

backstageAGENTS.md

backstage

backstage/backstage/AGENTS.md

prefixed `@backstage/`) - `/plugins`: Plugin packages (prefixed `@backstage/plugin-*`) - `/packages/app`: Main example app using the new frontend system - `/packages/app-legacy`: Example app using the old frontend system - `/packages/backend`: Example backend for local development

qarminAGENTS.md

czkawka

qarmin/czkawka/AGENTS.md

drawing diagrams are the only exception). Exception: `czkawka_core` is a library - every frontend in this workspace depends on it, and so do external consumers who only read its public

qarminAGENTS.md

czkawka / czkawka_core

qarmin/czkawka/czkawka_core/AGENTS.md

core – Architecture Guide ## Overview `czkawka_core` is the shared scanning engine used by all frontends. It has no UI dependency. Every scanning tool is implemented here; frontends only configure

No other project uses it yet

qarminAGENTS.md

czkawka / czkawka_gui

qarmin/czkawka/czkawka_gui/AGENTS.md

fixes that keep it compatible with `czkawka_core` API changes are accepted. --- ## Overview GTK4 frontend using XML UI files authored in Cambalache. All scanning tools available in `czkawka_core

No other project uses it yet

anywhere-labsAGENTS.md

dsh-desktop

anywhere-labs/dsh-desktop/AGENTS.md

check:next` validates it without a graphical application. Next uses the official published Web frontend and the recorded upstream Desktop presentation, with product capabilities composed as a separate bundle. - Develop

alibabaAGENTS.md

nacos

alibaba/nacos/AGENTS.md

control, AI pipeline, AI storage - **console / console-ui**: Web UI backend (Spring Boot) and frontend (React) - **ai / copilot / ai-registry-adaptor**: AI Agent support, Copilot integration, and AI registry adaptor

No other project uses it yet

onyx-dot-appReads credentialsAGENTS.md

onyx

onyx-dot-app/onyx/AGENTS.md

resolved, ask the user rather than skipping tests. - If using `playwright` to explore the frontend, log in with username `admin_user@example.com` and password `TestPassword123!` (the admin user created by the playwright

onyx-dot-appReads credentialsAGENTS.md

onyx / backend

onyx-dot-app/onyx/backend/AGENTS.md

Onyx running, _including_ the Web Server. Use these tests for anything that requires significant frontend <-> backend coordination. Tests are located at `web/tests/e2e`. Tests are written in TypeScript. Spec-writing rules

onyx-dot-appAGENTS.md

onyx / web

onyx-dot-app/onyx/web/AGENTS.md

Frontend Standards Standards for `web/` and `desktop/`. Every Opal component and layout has a `README.md` beside it. Read that README instead of guessing props. ## Where components come from

topoteretesReads credentialsAGENTS.md

cognee

topoteretes/cognee/AGENTS.md

server exposing cognee as MCP tools (SSE/HTTP/stdio). Contains its own README and Dockerfile. - `cognee-frontend/`: Next.js UI for local development and demos. - `distributed/deploy/`: One-click deployment templates (Modal, Fly.io, Railway

k1tbyteReads credentialsAGENTS.md

Wand-Enhancer

k1tbyte/Wand-Enhancer/AGENTS.md

invariants. ## Remote Web Panel - The default local remote port is `3223`. Keep bridge and frontend constants aligned; C# must not duplicate the presentation URL or port. - The embedded panel must

lbjlaqAGENTS.md

Antigravity-Manager

lbjlaq/Antigravity-Manager/AGENTS.md

testing on your own. Self-test only when four or more core backend or frontend interaction files are involved; hardcoded-only edits do not count as core-file changes

No other project uses it yet

filamentphpAGENTS.md

filament

filamentphp/filament/AGENTS.md

capturing documentation screenshots. ## Testing and Documentation Requirements **Introduce new tests only for actual frontend or backend behavior changes.** Styling changes and bug fixes that restore existing intended behavior should

hasuraAGENTS.md

graphql-engine

hasura/graphql-engine/AGENTS.md

dependencies (name, version, license) shipped by the Haskell server, the Go CLI and the frontend console. Whenever you add, remove or upgrade a dependency in any of these, update

hasuraReads credentialsAGENTS.md

graphql-engine / frontend

hasura/graphql-engine/frontend/AGENTS.md

AGENTS.md (frontend) This covers the `frontend/` workspace only. See the repo-root `AGENTS.md` for Haskell build/PR instructions that apply to the whole `graphql-engine-mono` repo. ## What this