Your training data may be outdated — these docs match your installed version.
## Installed Package Documentation
- [@alloy-js/core](./packages/http-server-csharp/node_modules/@alloy-js/core/docs/index.md)
- [@alloy-js/cli](./packages/http-server-csharp/node_modules/@alloy-js/cli/docs/index.md) — Alloy
Avoid `any`; if a registry or boundary needs it, keep the escape local and documented.
- Use top-level `import` statements; do not use `require()`.
- Never re-export as a shortcut
React Best Practices
**Version 1.0.0**
Vercel Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React and Next.js codebases. Humans
Diátaxis **explanation** quadrant: architecture rationale, tradeoffs, and alternatives considered.
## Two kinds of document
### Design docs
Living documents that describe how a concept or subsystem works **right now**. Named by topic
AGENTS.md — docs/
User-facing documentation for the Agents SDK monorepo. Each package owns the directory under `docs/` matching its unscoped package name. These markdown files are manually synced to [developers.cloudflare.com
Agent Instructions
This document provides instructions for agents on how to perform common development tasks in this repository.
## Initial Setup
This project uses `asdf` to manage tool versions. Before
Agent Guidelines
This document provides context for AI agents working on the Tokscale project.
## Maintaining AGENTS.md Files
When updating AGENTS.md files, follow these principles:
- **No hardcoded counts** — Don't write
regressions.
Before pushing eval changes, run `python eng/eval-quality/check_eval_quality.py`. It blocks eleven
structural defect classes documented in `eng/eval-quality/README.md` that can corrupt a real
evaluation result.
The distilled quality rules — what makes
make lint-swift`.
Keep `.editorconfig`, Ruff, pre-commit, Swift format scripts, Make targets, documentation, and CI in sync when changing lint policy. A lint policy change should explain the local
README](./README.md) for the full overview and
[`docs/`](./docs) for user-facing documentation.
Always style the framework name as `eve`, lowercase, in user-facing copy,
docs, prompts, comments, and headings
implementation.
- `examples/`: small runnable programs and packages.
- `conformance/`: language and CLI fixtures.
- `docs/`: public documentation site.
- `scripts/`: validation and release support tooling.
## Public Docs Policy
Docs should describe current user
swallow; don't log-and-continue on request path. The one documented exception is a **best-effort, off-request-path fire-and-forget** — always wrapped in [`observability.SafeGo`](internal/observability/safego.go) (bounded timeout
path is
something someone has to understand, maintain, and keep compatible.
## Comments and Documentation
Don't write comments explaining what code does, the code should speak for itself. Instead, focus
targeted type checks per package — do not run project-wide `tsc -b`
## Project Documents
When significant bug is being reported or a large spec is being created, place under `bugs/YY-MM-DD
from the authoritative product resource.
- Validate command syntax before acquiring runtime capabilities. Help, version, documentation, and rejected syntax must not start the application or mutate user configuration.
- Keep runtime imports