AGENTS.md examples from real projects

promptfooReads credentialsAGENTS.md

promptfoo

promptfoo/promptfoo/AGENTS.md

team integration tests npm run test:app -- src/pages/path/to/test.test.tsx --run # Run a specific frontend test file from repo root npx vitest path/to/test # Run a specific backend test file # Development

No other project uses it yet

promptfooReads credentialsAGENTS.md

promptfoo / test

promptfoo/promptfoo/test/AGENTS.md

failures - Use `--sequence.seed=12345` to reproduce a specific order ## Writing Tests **Reference files:** - **Vitest (frontend)**: `src/app/src/hooks/usePageMeta.test.ts` - explicit imports - **Vitest (backend)**: `test/assertions/contains.test.ts` - explicit imports All tests require explicit imports from vitest

No other project uses it yet

goauthentikAGENTS.md

authentik

goauthentik/authentik/AGENTS.md

docs live under `website/docs/developer-docs/` and are published at <https://docs.goauthentik.io/docs/developer-docs/>: - `setup/full-dev-environment.mdx` — full backend + frontend dev environment. - `setup/frontend-dev-environment.mdx` — web-only setup. - `setup/debugging.mdx` — attaching a debugger (VS Code config included). - `docs/style-guide.mdx

No other project uses it yet

goauthentikAGENTS.md

authentik / web

goauthentik/authentik/web/AGENTS.md

i18n (do not edit manually) packages/ core/ # Monorepo utilities (paths, environment, version) sfe/ # Standalone Frontend Engine (Rollup-based) test/ unit/ # Node.js unit tests (*.test.ts) browser/ # Playwright browser tests (*.browser.test.ts

No other project uses it yet

zulipAGENTS.md

zulip

zulip/zulip/AGENTS.md

what to test for UI changes (the file loads automatically when you work on frontend files). The right attitude is: "What could go wrong, and how do I verify that

activepiecesDeletes or force-pushesAGENTS.md

activepieces

activepieces/activepieces/AGENTS.md

bash npm start # Setup dev + start all npm run dev # Frontend + backend npm run lint-dev # Lint with auto-fix (ALWAYS before done) npx turbo run lint --filter= # Lint

tursodatabaseAGENTS.md

turso

tursodatabase/turso/AGENTS.md

here are for upstream syncs or harness maintenance. - `postgres/conformance/pg-sqltests/` - `.sqltest` coverage for the PostgreSQL frontend. Tests are meant to pass on both tursopg (`run`) and real PostgreSQL (`run-postgres`). - `testing/cli_tests

nocobaseAGENTS.md

nocobase

nocobase/nocobase/AGENTS.md

including the application's base path. Vite's port (normally 5173) serves the frontend development process and is not the user-facing application entry. This applies to every application, including

No other project uses it yet

argoprojAGENTS.md

argo-cd

argoproj/argo-cd/AGENTS.md

strictly enforced. You must use `go modules` for dependency management. * **UI (React/TypeScript):** The frontend is written in React and TypeScript. * **Kubernetes Manifests:** Argo CD heavily relies on Kubernetes manifests

plotlyAGENTS.md

dash

plotly/dash/AGENTS.md

directory: - [COMMANDS.md](.ai/COMMANDS.md) - Build, test, lint - [ARCHITECTURE.md](.ai/ARCHITECTURE.md) - Backend, callbacks, layout - [RENDERER.md](.ai/RENDERER.md) - Frontend, React, Redux - [COMPONENTS.md](.ai/COMPONENTS.md) - Component system - [TESTING.md](.ai/TESTING.md) - Testing patterns - [TROUBLESHOOTING.md](.ai/TROUBLESHOOTING.md) - Common issues

temporalioAGENTS.md

temporal

temporalio/temporal/AGENTS.md

/schema`: database schema definitions for core databases store and visibility store - `/service`: main services (frontend, history, matching, worker, etc.) - `/service/frontend`: frontend service implementation - `/service/history`: history service implementation - `/service/matching`: matching service

kriasoftAGENTS.md

react-starter-kit

kriasoft/react-starter-kit/AGENTS.md

runtime:** Cloudflare Workers (workerd) – not Bun. Code that ships must run on Workers APIs. - **Frontend:** React 19, TanStack Router, TanStack Query, Jotai, shadcn/ui (new-york), Tailwind CSS v4 - **Backend:** Hono

marimo-teamAGENTS.md

marimo

marimo-team/marimo/AGENTS.md

marimo Development Guidelines marimo is a reactive notebook for Python with a modern web frontend. ## Your primary responsibility is to the project and its users Being an open source library

marimo-teamAGENTS.md

marimo / frontend

marimo-team/marimo/frontend/AGENTS.md

Frontend Guidelines ## Key Principles - Write clear, maintainable code over clever/short syntax - Use TypeScript with proper typing for all code - Use functional programming patterns; avoid classes - Favor composition over inheritance - Reduce

No other project uses it yet

Skyvern-AIAGENTS.md

skyvern

Skyvern-AI/skyvern/AGENTS.md

service layers - `/utils`: Common utility functions - `/webeye`: Web interaction and browser automation - `/skyvern-frontend`: Frontend application - `/integrations`: Third-party service integrations - `/alembic`: Database migrations - `/scripts`: Utility and deployment scripts ## Coding Conventions

comet-mlReads credentialsAGENTS.md

opik

comet-ml/opik/AGENTS.md

codebase. Main areas: - `apps/opik-backend`: Java backend (source in `src/main/java`, tests in `src/test/java`). - `apps/opik-frontend`: React/TypeScript frontend (`src` and related assets/config). - `apps/opik-documentation`: documentation website and generated API docs. - `sdks/python`, `sdks/typescript`, `sdks/opik_optimizer

No other project uses it yet

1Panel-devReads credentialsAGENTS.md

MaxKB

1Panel-dev/MaxKB/AGENTS.md

agentic workflows, and MCP tool-use. Backend is Python 3.11 / Django 5.2 / LangChain; frontend is Vue 3 / Vite. Data layer is PostgreSQL + pgvector and Redis; Celery for async work

openobserveReads credentialsAGENTS.md

openobserve

openobserve/openobserve/AGENTS.md

clippy::too_many_lines -W clippy::cognitive_complexity -W clippy::excessive_nesting -D warnings`. ## Frontend (web/) - After every change under `web/`, run `npm run format:check` from `web/` before considering

foremAGENTS.md

forem

forem/forem/AGENTS.md

Follow Test Patterns**: Use `create(:factory)` syntax (FactoryBot) and standard RSpec expectations. - **Frontend vs Backend**: We are currently focused on robust backend regression tests. Frontend changes require more manual user

No other project uses it yet

mediar-aiAGENTS.md

screenpipe

mediar-ai/screenpipe/AGENTS.md

cargo test -p `, or `cargo test --workspace --exclude screenpipe-rfdetr-mlx` as CI does. Frontend is `cd apps/screenpipe-app-tauri && bun run test`. `src-tauri` is excluded from the workspace