Skip to main content
Beyond the MCP server, the Spree documentation is published in formats designed for direct LLM consumption. Use these when you want to feed docs into a prompt, point a custom agent at an index, or give agents fast local file access.

llms.txt

Following the llms.txt convention, two indexes are published:

Per-page Markdown

Append .md to any docs URL to get the raw Markdown for that page — ideal for fetching a single authoritative page into context:

The @spree/docs npm package

The full developer documentation also ships as an npm package, so agents working in your repository can Read doc files locally — no network round-trips, works offline, and version-pinned to what you installed:
Projects scaffolded with create-spree-app install it automatically.
The package tracks the docs published at install time and is versioned independently of your Spree gems — run your package manager’s update to refresh it, and prefer the MCP server when you need the absolute latest.

Generated agent instructions

create-spree-app scaffolds every project with a CLAUDE.md that tells coding agents where the local docs live, which CLI commands to use (spree dev, spree migrate, spree console), and the customization patterns to follow — so an agent dropped into a fresh project is productive without any prompting. The scaffold’s next-steps also suggest installing the agent skills for the full experience.