@spree/docs 0.1.86 → 0.1.88

package/dist/developer/agentic/mcp.md

@@ -1,7 +1,7 @@
 ---
 title: "Docs MCP Server"
 sidebarTitle: MCP
-description: "Connect your AI agent to the Spree documentation MCP server to search and read the latest docs while building."
+description: "Connect Claude, Cursor, or any MCP-compatible AI agent to the Spree docs MCP server to search and read the latest documentation while building."
 ---
 
 Spree hosts a [Model Context Protocol](https://modelcontextprotocol.io) server on top of this documentation. Once connected, your agent can search the docs and read full pages on demand — answering questions from the latest published documentation instead of stale training data.
@@ -72,4 +72,4 @@ Any MCP client that supports remote servers over streamable HTTP can connect —
 | **[`@spree/docs` npm package](llm-docs.md)** | Fast local reads inside a project — no network round-trip, works offline, pinned to what you installed |
 | **[Agent skills](agent-skills.md)** | Conventions and how-to knowledge the agent should apply without searching at all |
 
-> **NOTE:** In create-spree-app projects the generated `CLAUDE.md` already points agents at the local `@spree/docs` package first — MCP complements it for anything newer than your installed docs version.
+> **NOTE:** In create-spree-app projects the generated `AGENTS.md` and `CLAUDE.md` already points agents at the local `@spree/docs` package first — MCP complements it for anything newer than your installed docs version.

package/dist/developer/agentic/overview.md

@@ -1,16 +1,17 @@
 ---
 title: "Agentic Development"
 sidebarTitle: Overview
-description: "Build, customize, and upgrade Spree with AI coding agents — agent skills, a docs MCP server, and LLM-ready documentation."
+description: "Build, customize, and upgrade Spree stores with AI coding agents using installable agent skills, a documentation MCP server, and LLM-ready docs."
 ---
 
 Spree ships first-class tooling for AI-assisted development. Whether you use Claude Code, Cursor, Codex, Copilot, or any other coding agent, your agent can learn Spree's conventions, read the right docs at the right time, and run the project safely.
 
 ## Why Spree works well with AI agents
 
-- **Strong conventions** — everything is namespaced under `Spree::`, models follow predictable patterns (prefixed IDs, `Spree.base_class`, service objects, events), and the v3 REST API uses flat request/response shapes. Conventions are what agents are best at following.
+- **Strong conventions** — everything is namespaced under `Spree`, models follow predictable patterns (prefixed IDs, `Spree.base_class`, service objects, events), and the v3 REST API uses simple response/request shapes. Conventions are what agents are best at following.
+- **Fully Typed APIs** — both Store API and Admin API have OpenAPI specs and official TypeScript SDKs, so agents can generate code with confidence instead of guessing from training data.
 - **Docs designed for machine consumption** — the full documentation is available as [llms.txt, per-page Markdown, and a local npm package](llm-docs.md), so agents read authoritative content instead of guessing from training data.
-- **A guided project workflow** — [create-spree-app](../create-spree-app/quickstart.md) scaffolds projects with a generated `CLAUDE.md`, local docs, and the [Spree CLI](../cli/quickstart.md), so an agent can boot, migrate, generate code, and run tests without bespoke setup.
+- **A guided project workflow** — [create-spree-app](../create-spree-app/quickstart.md) scaffolds projects with a generated `AGENTS.md` and `CLAUDE.md`, local docs, and the [Spree CLI](../cli/quickstart.md), so an agent can boot, migrate, generate code, and run tests without bespoke setup.
 
 ## The toolbox
 

package/dist/developer/contributing/developing-spree.md

@@ -1,6 +1,6 @@
 ---
 title: Developing Spree
-description: Set up a Spree development environment with Docker, run the test suite, and submit pull requests to contribute to Spree Commerce.
+description: Set up a Spree Commerce development environment with Docker, run the RSpec test suite, follow coding conventions, and submit pull requests upstream.
 ---
 
 Please read our [Code of Conduct](https://github.com/spree/spree/blob/main/CODE_OF_CONDUCT.md) before contributing.

package/dist/developer/customization/api.md

@@ -1,7 +1,6 @@
 ---
-title: API
-description: >-
-  Add new Store API endpoints and customize existing API responses
+title: Customizing the Spree API
+description: Add new Store API endpoints, customize existing JSON responses with serializer decorators, and extend Spree's REST API to fit your storefront needs.
 ---
 
 Before you start customizing Spree API endpoints, make sure you reviewed all existing API endpoints in the [Spree API docs](/api-reference).

package/dist/developer/getting-started/quickstart.md

@@ -1,7 +1,7 @@
 ---
 title: "Installing Spree"
 sidebarTitle: Installation
-description: "Follow the instructions below to learn how to build and deploy your Spree application."
+description: "Install Spree Commerce locally with Docker or Ruby on Rails, run your first store, and deploy it to production with the official starter template."
 ---
 
 ## Installation options

package/dist/developer/sdk/extending.md

@@ -1,7 +1,7 @@
 ---
 title: Custom Endpoints
 sidebarTitle: Custom Endpoints
-description: Call custom Store API endpoints using the SDK's built-in request method
+description: Call your own custom Store API endpoints from the Spree TypeScript SDK using the built-in request method, with typed responses and shared auth handling.
 ---
 
 The client exposes a `request` method — the same function that powers all built-in resources. Use it to call any Store API endpoint, including ones you've added yourself.

package/dist/developer/sdk/quickstart.md

@@ -1,6 +1,6 @@
 ---
 title: Quickstart
-description: Install and start using the Spree SDK in your project
+description: Install the Spree TypeScript SDK, configure your Store API client, and make your first calls to products, carts, checkout, and customer endpoints.
 ---
 
 ## Installation

package/dist/developer/tutorial/admin.md

@@ -1,6 +1,6 @@
 ---
 title: Admin Dashboard
-description: Scaffold the admin UI for Brands, then add the rich text editor, logo upload, and a custom table column
+description: Scaffold the Spree admin UI for the Brands resource and add a rich text description editor, an Active Storage logo upload, and a custom table column.
 ---
 
 Now that we've created the `Brand` model, let's create an Admin Dashboard interface so admins can manage brands — including editing the rich text description and uploading the logo.

package/dist/developer/tutorial/api.md

@@ -1,6 +1,6 @@
 ---
 title: API
-description: Expose your Brand model through the Store and Admin APIs with serializers, controllers, and routes
+description: Expose your custom Brand model through the Spree Store and Admin REST APIs with serializers, controllers, routes, and the spree:api_resource generator.
 ---
 
 In this tutorial, we'll expose our Brand model through Spree's v3 API — the customer-facing **Store API** that storefronts read from, and the back-office **Admin API** with full CRUD for apps and integrations. We'll also extend the existing Product serializer to include brand data.

package/dist/developer/tutorial/events.md

@@ -1,6 +1,6 @@
 ---
 title: Events & Webhooks
-description: React to store activity and connect Spree to external systems — an OMS, a warehouse, an ERP — with subscribers and webhooks
+description: React to Spree store activity and connect to external systems like an OMS, warehouse, or ERP using event subscribers, the subscriber generator, and webhooks.
 ---
 
 > **INFO:** This guide assumes you've completed the [Model](model.md) and [API](api.md) tutorials — we'll reuse the Brand serializer created there.

package/dist/developer/tutorial/introduction.md

@@ -1,7 +1,7 @@
 ---
 title: Tutorial
 sidebarTitle: Introduction
-description: Build a complete custom feature — model, admin UI, Store API, and TypeScript storefront integration — the Spree way.
+description: Build a complete custom Brands feature in Spree — model, admin UI, Store and Admin APIs, events, and TypeScript storefront integration — end to end.
 ---
 
 This tutorial walks you through creating a complete Spree feature from scratch: a "Brands" feature that lets admins manage [Product](../core-concepts/products.md) brands, exposes them through the Store API, and consumes them from TypeScript.

package/dist/developer/tutorial/model.md

@@ -1,6 +1,6 @@
 ---
 title: Model
-description: Create the Brand model — columns, rich text description, and logo upload — with a single generator command
+description: Create a custom Brand model in Spree with database columns, a rich text description, and an Active Storage logo upload using a single generator command.
 ---
 
 In this step we'll create the `Spree::Brand` model with everything it needs: a `name` column, a rich text `description`, and an uploadable `logo`.

package/dist/developer/tutorial/sdk.md

@@ -1,6 +1,6 @@
 ---
 title: SDK
-description: Use the TypeScript SDK to consume your custom Brand endpoints and extended Product data
+description: Use the Spree TypeScript SDK to consume your custom Brand endpoints, fetch extended Product data, and surface the new resource in your headless storefront.
 ---
 
 In this tutorial, we'll use the `@spree/sdk` TypeScript SDK to consume the Brand API endpoints we created in the [API tutorial](api.md), and work with the extended Product data that now includes brand information.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.86",
+  "version": "0.1.88",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",