> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stacknext.space/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> StackNext documentation is written for developers using StackNext in a Next.js App Router project. Use the getting-started and guides sections to install and operate the product, and the reference section for CLI, configuration, MCP and package surfaces. Version-matched package API reference ships inside each npm package under node_modules/@stacknext/<package>/docs/ and is preferred over this site for installed-version APIs. Diagnostic findings are evidence, not confirmed root causes; regression comparisons are deterministic and report-only. Contributor and repository-maintenance documentation is not part of this site.

# AI agent support

> How StackNext gives coding agents version-matched docs, evidence-first workflows and read-only runtime access.

StackNext is designed for agents that need runtime evidence before changing
code, and for agents that must use the APIs of the installed version rather than
the latest documentation on the internet.

## The four pieces

| Piece | What it gives the agent | Where it lives |
| - | - | - |
| Package docs | Version-matched API reference in installed packages | `node_modules/@stacknext/*/docs/` |
| Managed `AGENTS.md` | A pointer to local docs and evidence rules | Project `AGENTS.md`, installed by `stacknext init --agents` |
| Agent Skill | Debugging, diagnostics, regression and snapshot workflows | Client skill directory, installed by `stacknext skill install` |
| MCP server | Read-only access to live telemetry and saved records | `stacknext mcp` over stdio |

The pieces are intentionally separate. Package docs contain technical
reference; the skill contains procedures; the MCP server contains runtime data;
`AGENTS.md` carries the short project-level rules.

## The evidence contract

An agent using StackNext must:

1. Start with `get_project_summary` and confirm the app is connected.
2. Cite routes, trace ids, error ids, spans, durations, statuses or finding ids.
3. Treat diagnostic findings as evidence, not confirmed root causes.
4. Treat `inconclusive` comparisons as inconclusive, not passes.
5. Say when a result comes from a snapshot instead of the live sample.
6. Respect the redaction boundary and never try to recover removed values.
7. Never claim support for an API, config key or package that is not in the
   installed docs.

## Start here

* [Setup](https://docs.stacknext.space/ai-agents/setup.md) — install instructions, the skill and MCP clients.
* [Evidence-first workflows](https://docs.stacknext.space/ai-agents/workflows.md) — the shared investigation
  loop.
* [Local documentation](https://docs.stacknext.space/ai-agents/local-docs.md) — version-matched files and
  AI-readable endpoints.
* [MCP server](https://docs.stacknext.space/mcp.md) — start the server and review its security model.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.