docs/` guidelines
Follow the general [documentation guidance](../agent_docs/documentation.md). These rules cover published Markdown under `docs/`.
## Links and structure
- Use reference-style links for API elements: `[ElementName][module.path.ElementName]`. They provide hover
check time and improve IDE autocomplete; when `Any` is unavoidable due to external constraints, document expected structure in docstrings
- Use `TypedDict` or dataclass instead of `dict[str, Any]` when structure
once if the process fails after the side effect but
before its checkpoint commits. Document the engine's guarantees and require idempotency or expose
an engine-native at-most-once
Design
- Silently ignore unsupported generic tuning settings (`temperature`, sampling params, penalties, …) at runtime and document them in docstrings — a model that simply no-ops an unsupported knob keeps client code
there; model settings remain as an alternative for backward compat
- Provider support must be documented in three places: the tool class docstring 'Supported by' list, `docs/native-tools.md` provider table, and field
nodes, no `before_model_request`, deferred
results resolved inline), the difference must be deliberate, documented in
[docs/realtime/](../../../docs/realtime/), and covered by a parity test in `tests/realtime/`.
## Provider adapters
- Parse provider
that way — see [7106](https://github.com/pydantic/pydantic-ai/pull/7106#discussion_r3723844005), which closed [7105](https://github.com/pydantic/pydantic-ai/issues/7105) by documenting the wiring instead of exposing `AGUIAdapter.context`.
A field earns an adapter property when **both** hold
reference
When implementing a new capability, reference these docs:
- <https://pydantic.dev/docs/ai/capabilities/overview/> -- main capabilities documentation, usage patterns, built-in capabilities
- <https://pydantic.dev/docs/ai/core-concepts/hooks/> -- lifecycle hooks reference, hook ordering, all hook
code review.
3. Fire it from exactly one place in the shell.
4. Document it in `PLUGINS.md` in the table it belongs to.
## The `/plugins`, `/set`, `/theme`, `/model`, and `/add_model
function, parameter, or branch is maintenance burden. The best abstraction is often no abstraction.
## Documentation
### Docstrings
Docstrings must follow the repository format below. Do **not** convert docstrings to other styles
personal
machine setup, private network details, credentials, tokens, or local-only
workflow notes here.
## Documentation by task
Use the references that match the change; there is no blanket reading list
installed globally.
## Workflow
- Run `pnpm type-check` after each turn to ensure type safety
- Documentation lives in `apps/web/content/docs/` and uses Geistdocs frontmatter. Keep public `/docs` URLs, heading IDs, `lib/page-titles.ts`, `lib/docs-navigation.ts
AGENTS.md - AI Agent Guidelines for LangChain.js
This document provides guidance for AI coding agents working with the LangChain.js codebase.
## Corridor security analysis
When Corridor's `analyzePlan` tool is available, create
with the date and the decision or PR they implement. The code says what.
- Documents own one kind of fact each and link to each other rather than restate. There
matched; double-bracing
does NOT escape.
- WRONG in instruction text: `.../collection/{document_id}`, `/form/item_{i}_name`
- RIGHT: `.../collection/ `, `/form/item_i_name` (or `[i]`)
`[BRACKET]` and ` ` notations are safe. This
this codebase**, any skill, agent, or subagent **MUST first read the service Technical Design Document (TDD)** located at [docs/TDD.md](file:///usr/local/google/home/williamsmt/Projects/development/generative-ai/search/gemini-enterprise/group-licensing/docs/TDD.md) (in the `docs/` subdirectory). This document contains the definitive
current contracts. Existing code is
evidence, but a legacy exception is not precedent; `Proposal` documents are
direction only. Do not mix unrelated cleanup, hand-edit generated files, weaken
gates