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
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
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
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
1 project uses a version of this
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-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
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
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
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
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
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
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
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
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
maximhq/bifrost/AGENTS.md
# AGENTS.md — Bifrost AI Gateway > Context for AI agents (Claude Code, Copilot, Cursor, etc.) working
Steady4 mentions in 2 weeks
No other project uses it yet
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
Steady4 mentions in 2 weeks
No other project uses it yet
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
Steady4 mentions in 2 weeks
1 project uses a version of this
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
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
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
cloudflare/vinext/AGENTS.md
# Agent Guidelines Instructions for AI agents working on this codebase. --- ## Project Overview **vinext** is
Steady5 mentions in 2 weeks
No other project uses it yet
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
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.