Use the docs with coding agents
Give an agent a small, versioned source set and keep documentation lookup separate from action authority.
Source and verification context ⌄
Source-guided
Inspect the source ↗Repository links may require access. Source inspection is separate from a clean public-package installation.
Get the shape of this guide.
Move through the ideas, inspect their relationships, or make a focused reading path. The complete guide stays below.
Start with a focused context packet
Give the agent the task, selected package versions or source commit, the relevant guide, and the exact contract or runtime reference. A small coherent source set is easier to verify than the entire monorepo corpus.
Read the supporting context
Ask it to identify which behavior is declared, which code implements it and which host dependency supplies authority. This encourages it to preserve the same boundaries a human reviewer would inspect.
Explore a section, then continue with the complete article below.
Start with a focused context packet
Give the agent the task, selected package versions or source commit, the relevant guide, and the exact contract or runtime reference. A small coherent source set is easier to verify than the entire monorepo corpus.
Ask it to identify which behavior is declared, which code implements it and which host dependency supplies authority. This encourages it to preserve the same boundaries a human reviewer would inspect.
Give an agent a coherent slice of the system.Trace the mechanism · 3 ways to look closer＋
An agent is asked to change one operation. A useful context packet keeps the task, source identity and execution responsibilities together.
Start with orientation and a bounded reference.
The task names a capability but not the package that owns it.
Read the relevant area and task context.
An area overview and package overview narrow the source set.
A package listing does not establish registry availability or permission to edit it.
Choose the relevant package and source identity, then follow the exact manual or structured source data.
Where this explanation comes from
An authored situation, grounded in the linked source guides. Choosing a case explores its expected responsibilities; it does not execute an operation.
Choose the smallest useful entry point
This review site offers an area index, a complete package index and a bounded agent overview for every package. Start with the overview, then read the relevant package manual or structured source data. Package and area evidence is pinned to bcc79fcc; the MCP source discussed below retains its stated d58fa5b7 context.
The Copy agent overview control provides purpose, source identity, declared capabilities and a limited import selection, with links to deeper evidence. Full Markdown and JSON remain available when the task needs them. Package presence, a version string and a declared import do not establish registry availability or successful execution.
| Need | Entry point in this review | What to inspect |
|---|---|---|
| Orientation | /llms.txt | Choose a core guide, area or package |
| All packages | /docs/packages/index.json | Exact package identity and retrieval locations |
| One package, bounded context | /docs/packages/[slug].context.md | Source pin, purpose, runtime and selected imports |
| Full package evidence | /docs/packages/[slug].md or .json | README, capabilities, targets, dependencies and scripts |
| Area relationships | /docs/areas/index.json | Entry points and related technical areas |
Understand the lookup tools
The inspected authoring MCP source defines documentation search, get, route resolution, contract lookup and facet listing. These are documentation operations. Their presence in source is not a claim that a public hosted MCP endpoint has been qualified.
Documentation lookup does not authorize editing a repository, executing a provider action or deploying an application. Keep the agent's work permissions separate from the information it can read.
A plugin, MCP server or skill should retrieve the same versioned documentation records and keep task instructions separate from retrieved evidence. This static review supplies the web, Markdown and JSON projections; the proposed shared DocSpec compiler and retrieval service are described in the . It does not expose a new MCP endpoint or install a coding-agent skill.
Review the generated answer
Require links to the exact sources behind proposed APIs or commands. Check that examples use the same release channel, and ask for an explicit statement when a snippet is illustrative rather than executed.
For an implementation task, verify the result through the owning source checks and a meaningful runtime case. A confident answer that quotes documentation is still a proposal until the relevant behavior is tested.