@mastra/mcp-docs-server 1.1.9-alpha.0 → 1.1.9-alpha.2

package/.docs/docs/server/auth/simple-auth.md

@@ -1,8 +1,8 @@
-# SimpleAuth Class
+# SimpleAuth class
 
 The `SimpleAuth` class provides token-based authentication using a basic token-to-user mapping. It's included in `@mastra/core/server` and is useful for development, testing, and basic API key authentication scenarios.
 
-## Use Cases
+## Use cases
 
 - Local development and testing
 - Simple API key authentication
@@ -17,7 +17,7 @@ SimpleAuth is included in `@mastra/core`, no additional packages required.
 import { SimpleAuth } from '@mastra/core/server'
 ```
 
-## Usage Example
+## Usage example
 
 ```typescript
 import { Mastra } from '@mastra/core'
@@ -50,7 +50,7 @@ export const mastra = new Mastra({
 })
 ```
 
-## Configuration Options
+## Configuration options
 
 | Option          | Type                         | Required | Description                            |
 | --------------- | ---------------------------- | -------- | -------------------------------------- |
@@ -79,7 +79,7 @@ new SimpleAuth({
 })
 ```
 
-## Making Authenticated Requests
+## Making authenticated requests
 
 Include your token in the `Authorization` header:
 
@@ -99,7 +99,7 @@ curl -X POST http://localhost:4111/api/agents/myAgent/generate \
   -d '{"messages": "Hello"}'
 ```
 
-## Custom Authorization
+## Custom authorization
 
 Add role-based or custom authorization logic:
 
@@ -119,7 +119,7 @@ new SimpleAuth<User>({
 })
 ```
 
-## Environment Variables
+## Environment variables
 
 For production-like setups, load tokens from environment variables:
 
@@ -144,7 +144,7 @@ export const mastra = new Mastra({
 })
 ```
 
-## With MastraClient
+## With `MastraClient`
 
 Configure the client with your token:
 

package/.docs/docs/server/auth/supabase.md

@@ -1,4 +1,4 @@
-# MastraAuthSupabase Class
+# MastraAuthSupabase class
 
 The `MastraAuthSupabase` class provides authentication for Mastra using Supabase Auth. It verifies incoming requests using Supabase's authentication system and integrates with the Mastra server using the `auth` option.
 

package/.docs/docs/server/auth/workos.md

@@ -1,4 +1,4 @@
-# MastraAuthWorkos Class
+# MastraAuthWorkos class
 
 The `MastraAuthWorkos` class provides authentication for Mastra using WorkOS. It verifies incoming requests using WorkOS access tokens and integrates with the Mastra server using the `auth` option.
 

package/.docs/docs/server/auth.md

@@ -1,4 +1,4 @@
-# Auth Overview
+# Auth overview
 
 Mastra lets you choose how you handle authentication, so you can secure access to your application's endpoints using the identity system that fits your stack.
 

package/.docs/docs/server/custom-adapters.md

@@ -1,4 +1,4 @@
-# Custom Adapters
+# Custom adapters
 
 Create a custom adapter when you need to run Mastra with a framework other than Hono or Express. This might be necessary if you have specific request/response handling requirements that `@mastra/hono` and `@mastra/express` don't support.
 
@@ -38,7 +38,7 @@ These type parameters ensure type safety throughout your adapter implementation
 
 You must implement these six abstract methods. Each handles a specific part of the request lifecycle, from attaching context to sending responses.
 
-### registerContextMiddleware()
+### `registerContextMiddleware()`
 
 This method runs first and attaches Mastra context to every incoming request. Route handlers need access to the Mastra instance, tools, and other context to function. How you attach this context depends on your framework — Express uses `res.locals`, Hono uses `c.set()`, and other frameworks have their own patterns.
 
@@ -65,7 +65,7 @@ Context to attach:
 | `abortSignal`    | `AbortSignal`          | Request cancellation signal      |
 | `taskStore`      | `InMemoryTaskStore`    | A2A task storage (if configured) |
 
-### registerAuthMiddleware()
+### `registerAuthMiddleware()`
 
 Register authentication and authorization middleware. This method should check if authentication is configured on the Mastra instance and skip registration entirely if not. When auth is configured, you'll typically register two middleware functions: one for authentication (validating tokens and setting the user) and one for authorization (checking if the user can access the requested resource).
 
@@ -101,7 +101,7 @@ registerAuthMiddleware(): void {
 }
 ```
 
-### registerRoute()
+### `registerRoute()`
 
 Register a single route with your framework. This method is called once for each Mastra route during initialization. It receives a `ServerRoute` object containing the path, HTTP method, handler function, and Zod schemas for validation. Your implementation should wire this up to your framework's routing system.
 
@@ -148,7 +148,7 @@ async registerRoute(
 }
 ```
 
-### getParams()
+### `getParams()`
 
 Extract URL parameters, query parameters, and request body from the incoming request. Different frameworks expose these values in different ways—Express uses `req.params`, `req.query`, and `req.body`, while other frameworks may use different property names or require method calls. This method normalizes the extraction for your framework.
 
@@ -172,7 +172,7 @@ async getParams(
 }
 ```
 
-### sendResponse()
+### `sendResponse()`
 
 Send the response back to the client based on the route's response type. Mastra routes can return different response types: JSON for most API responses, streams for agent generation, and special types for MCP transports. Your implementation should handle each type appropriately for your framework.
 
@@ -207,7 +207,7 @@ async sendResponse(
 }
 ```
 
-### stream()
+### `stream()`
 
 Handle streaming responses for agent generation. When an agent generates a response, it produces a stream of chunks that should be sent to the client as they become available. This method reads from the stream, optionally applies redaction to hide sensitive data, and writes chunks to the response in the appropriate format (SSE or newline-delimited JSON).
 

package/.docs/docs/server/custom-api-routes.md

@@ -1,4 +1,4 @@
-# Custom API Routes
+# Custom API routes
 
 By default, Mastra automatically exposes registered agents and workflows via its server. For additional behavior you can define your own HTTP routes.
 
@@ -61,7 +61,7 @@ export const mastra = new Mastra({
 })
 ```
 
-## OpenAPI Documentation
+## OpenAPI documentation
 
 Custom routes can include OpenAPI metadata to appear in the Swagger UI alongside Mastra server routes. Pass an `openapi` option with standard OpenAPI operation fields.
 

package/.docs/docs/server/mastra-client.md

@@ -1,4 +1,4 @@
-# Mastra Client SDK
+# Mastra client SDK
 
 The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/mastra-server) from your client environment.
 

package/.docs/docs/server/mastra-server.md

@@ -1,4 +1,4 @@
-# Server Overview
+# Server overview
 
 Mastra runs as an HTTP server that exposes your agents, workflows, and other functionality as API endpoints. The server handles request routing, middleware execution, authentication, and streaming responses.
 

package/.docs/docs/server/request-context.md

@@ -1,4 +1,4 @@
-# Request Context
+# Request context
 
 Agents, tools, and workflows can all accept `RequestContext` as a parameter, making request-specific values available to the underlying primitives.
 
@@ -6,7 +6,7 @@ Agents, tools, and workflows can all accept `RequestContext` as a parameter, mak
 
 Use `RequestContext` when a primitive's behavior should change based on runtime conditions. For example, you might switch models or storage backends based on user attributes, or adjust instructions and tool selection based on language.
 
-> **Note:** **Note:** `RequestContext` is primarily used for passing data into specific requests. It's distinct from agent memory, which handles conversation history and state persistence across multiple calls.
+> **Note:** `RequestContext` is primarily used for passing data into specific requests. It's distinct from agent memory, which handles conversation history and state persistence across multiple calls.
 
 ## Setting values
 

package/.docs/docs/server/server-adapters.md

@@ -1,4 +1,4 @@
-# Server Adapters
+# Server adapters
 
 Server adapters let you run Mastra with your own HTTP server instead of the Hono server generated by `mastra build`. They provide more control over the server setup, including custom middleware ordering, authentication, logging, and deployment configuration. You can still integrate Mastra into any Node.js application without changing how agents or workflows execute.
 

package/.docs/docs/streaming/events.md

@@ -1,4 +1,4 @@
-# Streaming Events
+# Streaming events
 
 Streaming from agents or workflows provides real-time visibility into either the LLM’s output or the status of a workflow run. This feedback can be passed directly to the user, or used within applications to handle workflow status more effectively, creating a smoother and more responsive experience.
 

package/.docs/docs/streaming/overview.md

@@ -1,4 +1,4 @@
-# Streaming Overview
+# Streaming overview
 
 Mastra supports real-time, incremental responses from agents and workflows, allowing users to see output as it’s generated instead of waiting for completion. This is useful for chat, long-form content, multi-step workflows, or any scenario where immediate feedback matters.
 

package/.docs/docs/streaming/tool-streaming.md

@@ -114,11 +114,11 @@ for await (const chunk of stream) {
 }
 ```
 
-## Tool Lifecycle Hooks
+## Tool lifecycle hooks
 
 Tools support lifecycle hooks that allow you to monitor different stages of tool execution during streaming. These hooks are particularly useful for logging or analytics.
 
-### Example: Using onInputAvailable and onOutput
+### Example: Using `onInputAvailable` and `onOutput`
 
 ```typescript
 import { createTool } from '@mastra/core/tools'

package/.docs/docs/voice/overview.md

@@ -2,7 +2,7 @@
 
 Mastra's Voice system provides a unified interface for voice interactions, enabling text-to-speech (TTS), speech-to-text (STT), and real-time speech-to-speech (STS) capabilities in your applications.
 
-## Adding Voice to Agents
+## Adding voice to agents
 
 To learn how to integrate voice capabilities into your agents, check out the [Adding Voice to Agents](https://mastra.ai/docs/agents/adding-voice) documentation. This section covers how to use both single and multiple voice providers, as well as real-time interactions.
 
@@ -588,7 +588,7 @@ await voiceAgent.voice.send(micStream)
 
 Visit the [Google Gemini Live Reference](https://mastra.ai/reference/voice/google-gemini-live) for more information on the Google Gemini Live voice provider.
 
-## Voice Configuration
+## Voice configuration
 
 Each voice provider can be configured with different models and options. Below are the detailed configuration options for all supported providers:
 
@@ -945,7 +945,7 @@ const voice = new CompositeVoice({
 
 For more information on the CompositeVoice, refer to the [CompositeVoice Reference](https://mastra.ai/reference/voice/composite-voice).
 
-## More Resources
+## More resources
 
 - [CompositeVoice](https://mastra.ai/reference/voice/composite-voice)
 - [MastraVoice](https://mastra.ai/reference/voice/mastra-voice)

package/.docs/docs/voice/speech-to-speech.md

@@ -1,4 +1,4 @@
-# Speech-to-Speech Capabilities in Mastra
+# Speech-to-Speech capabilities in Mastra
 
 ## Introduction
 

package/.docs/docs/voice/speech-to-text.md

@@ -24,7 +24,7 @@ const voice = new OpenAIVoice({
 const voice = new OpenAIVoice()
 ```
 
-## Available Providers
+## Available providers
 
 Mastra supports several Speech-to-Text providers, each with their own capabilities and strengths:
 
@@ -42,7 +42,7 @@ Each provider is implemented as a separate package that you can install as neede
 pnpm add @mastra/voice-openai@latest  # Example for OpenAI
 ```
 
-## Using the Listen Method
+## Using the listen method
 
 The primary method for STT is the `listen()` method, which converts spoken audio into text. Here's how to use it:
 

package/.docs/docs/voice/text-to-speech.md

@@ -29,7 +29,7 @@ const voice = new OpenAIVoice({
 const voice = new OpenAIVoice()
 ```
 
-## Available Providers
+## Available providers
 
 Mastra supports a wide range of Text-to-Speech providers, each with their own unique capabilities and voice options. You can choose the provider that best suits your application's needs:
 
@@ -50,7 +50,7 @@ Each provider is implemented as a separate package that you can install as neede
 pnpm add @mastra/voice-openai@latest  # Example for OpenAI
 ```
 
-## Using the Speak Method
+## Using the speak method
 
 The primary method for TTS is the `speak()` method, which converts text to speech. This method can accept options that allows you to specify the speaker and other provider-specific options. Here's how to use it:
 

package/.docs/docs/workflows/agents-and-tools.md

@@ -1,4 +1,4 @@
-# Agents and Tools
+# Agents and tools
 
 Workflow steps can call agents to leverage LLM reasoning or call tools for type-safe logic. You can either invoke them from within a step's `execute` function or compose them directly as steps using `createStep()`.
 

package/.docs/docs/workflows/control-flow.md

@@ -1,4 +1,4 @@
-# Control Flow
+# Control flow
 
 Workflows run a sequence of predefined tasks, and you can control how that flow is executed. Tasks are divided into **steps**, which can be executed in different ways depending on your requirements. They can run sequentially, in parallel, or follow different paths based on conditions.
 

package/.docs/docs/workflows/error-handling.md

@@ -1,4 +1,4 @@
-# Error Handling
+# Error handling
 
 Mastra workflows support error handling through result status checks after execution, retry policies for transient failures, and lifecycle callbacks for centralized error logging or alerting.
 
@@ -58,7 +58,7 @@ if (result.status === 'failed') {
 
 For scenarios where you need to handle workflow completion without awaiting the result—such as background jobs, fire-and-forget workflows, or centralized logging—you can use lifecycle callbacks.
 
-### onFinish
+### `onFinish`
 
 Called when a workflow completes with any status (success, failed, suspended, or tripwire):
 
@@ -100,7 +100,7 @@ The `onFinish` callback receives:
 - `logger` - The workflow's logger instance
 - `state` - The workflow's current state object
 
-### onError
+### `onError`
 
 Called only when a workflow fails (status is `'failed'` or `'tripwire'`):
 

package/.docs/docs/workflows/suspend-and-resume.md

@@ -1,4 +1,4 @@
-# Suspend & Resume
+# Suspend and resume
 
 Workflows can be paused at any step to collect additional data, wait for API callbacks, throttle costly operations, or request [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) input. When a workflow is suspended, its current execution state is saved as a snapshot. You can later resume the workflow from a [specific step ID](https://mastra.ai/docs/workflows/snapshots), restoring the exact state captured in that snapshot. [Snapshots](https://mastra.ai/docs/workflows/snapshots) are stored in your configured storage provider and persist across deployments and application restarts.
 

package/.docs/docs/workflows/time-travel.md

@@ -1,4 +1,4 @@
-# Time Travel
+# Time travel
 
 Time travel allows you to re-execute a workflow starting from any specific step, using either stored snapshot data or custom context you provide. This is useful for debugging failed workflows, testing individual steps with different inputs, or recovering from errors without re-running the entire workflow. You can also use time travel to execute a workflow that hasn't been run yet, starting from any specific step.
 

package/.docs/docs/workflows/workflow-state.md

@@ -1,4 +1,4 @@
-# Workflow State
+# Workflow state
 
 Workflow state lets you share values across steps without passing them through every step's inputSchema and outputSchema. This is useful for tracking progress, accumulating results, or sharing configuration across the entire workflow.
 

package/.docs/docs/workspace/filesystem.md

@@ -103,7 +103,7 @@ const workspace = new Workspace({
 
 When read-only, write tools (`write_file`, `edit_file`, `delete`, `mkdir`) aren't added to the agent's toolset. The agent can still read and list files.
 
-## Mounts and CompositeFilesystem
+## Mounts and `CompositeFilesystem`
 
 When you use the `mounts` option on a workspace, Mastra creates a `CompositeFilesystem` that routes file operations to the correct provider based on path prefix.
 

package/.docs/docs/workspace/overview.md

@@ -265,7 +265,7 @@ const workspace = new Workspace({
 await workspace.init()
 ```
 
-### What init() does
+### What `init()` does
 
 Initialization runs setup logic for each configured provider:
 

package/.docs/docs/workspace/search.md

@@ -1,4 +1,4 @@
-# Search and Indexing
+# Search and indexing
 
 **Added in:** `@mastra/core@1.1.0`
 

package/.docs/docs/workspace/skills.md

@@ -1,4 +1,4 @@
-# Workspace Skills
+# Workspace skills
 
 **Added in:** `@mastra/core@1.1.0`
 
@@ -24,7 +24,7 @@ A skill is a folder containing:
 
 When skills are configured on a workspace, agents can discover and activate them during conversations.
 
-## SKILL.md format
+## `SKILL.md` format
 
 Follow the official [skill specification](https://agentskills.io/specification) when creating your skill. Here is an example `SKILL.md` for a code review skill:
 

package/.docs/guides/build-your-ui/ai-sdk-ui.md

@@ -6,7 +6,7 @@
 
 > **Tip:** Want to see more examples? Visit Mastra's [**UI Dojo**](https://ui-dojo.mastra.ai/) or the [Next.js quickstart guide](https://mastra.ai/guides/getting-started/next-js).
 
-## Getting Started
+## Getting started
 
 Use Mastra and AI SDK UI together by installing the `@mastra/ai-sdk` package. `@mastra/ai-sdk` provides custom API routes and utilities for streaming Mastra agents in AI SDK-compatible formats. This includes chat, workflow, and network route handlers, along with utilities and exported types for UI integrations.
 
@@ -40,7 +40,7 @@ bun add @mastra/ai-sdk@latest @ai-sdk/react ai
 
 You're now ready to follow the integration guides and recipes below!
 
-## Integration Guides
+## Integration guides
 
 Typically, you'll set up API routes that stream Mastra content in AI SDK-compatible format, and then use those routes in AI SDK UI hooks like `useChat()`. Below you'll find two main approaches to achieve this:
 

package/.docs/guides/build-your-ui/assistant-ui.md

@@ -6,7 +6,7 @@
 
 > **Tip:** Visit Mastra's [**"UI Dojo"**](https://ui-dojo.mastra.ai/) to see real-world examples of Assistant UI integrated with Mastra.
 
-## Integration Guide
+## Integration guide
 
 Run Mastra as a standalone server and connect your Next.js frontend (with Assistant UI) to its API endpoints.
 

package/.docs/guides/build-your-ui/copilotkit.md

@@ -8,7 +8,7 @@ Visit the [CopilotKit documentation](https://docs.copilotkit.ai/) to learn more
 
 > **Tip:** Visit Mastra's [**"UI Dojo"**](https://ui-dojo.mastra.ai/) to see real-world examples of CopilotKit integrated with Mastra.
 
-## Integration Guide
+## Integration guide
 
 Run Mastra as a standalone server and connect your Next.js frontend (with CopilotKit) to its API endpoints.
 

package/.docs/guides/deployment/digital-ocean.md

@@ -10,7 +10,7 @@ You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quic
 
 The **App Platform** uses an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
 
-## App Platform
+## App platform
 
 After setting up your project, push it to your remote Git provider of choice (e.g. GitHub).
 

package/.docs/guides/getting-started/astro.md

@@ -123,7 +123,7 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 
 You'll call `weather-agent.ts` from your Astro routes in the next steps.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/getting-started/electron.md

@@ -109,7 +109,7 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 
 You'll call `weather-agent.ts` from your chat UI in the next steps.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/getting-started/next-js.md

@@ -95,7 +95,7 @@ You'll call `weather-agent.ts` from your Next.js routes in the next steps.
 >
 > Relative paths resolve based on each process's working directory, which differs between `next dev` and `mastra dev`.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/getting-started/vite-react.md

@@ -166,7 +166,7 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 
 You'll call `weather-agent.ts` from your chat UI in the next steps.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/guide/ai-recruiter.md

@@ -1,4 +1,4 @@
-# Building an AI Recruiter
+# Building an AI recruiter
 
 In this guide, you'll learn how Mastra helps you build workflows with LLMs.
 
@@ -10,7 +10,7 @@ You'll create a workflow that gathers information from a candidate's resume, the
 - An API key from a supported [Model Provider](https://mastra.ai/models)
 - An existing Mastra project (Follow the [installation guide](https://mastra.ai/guides/getting-started/quickstart) to set up a new project)
 
-## Building the Workflow
+## Building the workflow
 
 Set up the Workflow, define steps to extract and classify candidate data, and then ask suitable follow-up questions.
 
@@ -176,7 +176,7 @@ Set up the Workflow, define steps to extract and classify candidate data, and th
    })
    ```
 
-## Testing the Workflow
+## Testing the workflow
 
 You can test your workflow inside [Studio](https://mastra.ai/docs/getting-started/studio) by starting the development server:
 

package/.docs/guides/guide/chef-michel.md

@@ -1,4 +1,4 @@
-# Building an AI Chef Assistant
+# How to build an AI chef assistant
 
 In this guide, you'll create a "Chef Assistant" agent that helps users cook meals with available ingredients.
 
@@ -12,7 +12,7 @@ You'll learn how to create the agent and register it with Mastra. Next, you'll i
 - An API key from a supported [Model Provider](https://mastra.ai/models)
 - An existing Mastra project (Follow the [installation guide](https://mastra.ai/guides/getting-started/quickstart) to set up a new project)
 
-## Creating the Agent
+## Create the agent
 
 To create an agent in Mastra use the `Agent` class to define it and then register it with Mastra.
 
@@ -42,7 +42,7 @@ To create an agent in Mastra use the `Agent` class to define it and then registe
    })
    ```
 
-## Interacting with the Agent
+## Interact with the agent
 
 Depending on your requirements you can interact and get responses from the agent in different formats. In the following steps you'll learn how to generate, stream, and get structured output.
 
@@ -169,7 +169,7 @@ Depending on your requirements you can interact and get responses from the agent
    }
    ```
 
-## Running the Agent Server
+## Run the agent server
 
 Learn how to interact with your agent through Mastra's API.
 

package/.docs/guides/guide/code-review-bot.md

@@ -1,4 +1,4 @@
-# Building a Code Review Bot
+# Building a code review bot
 
 In this guide, you'll build a code review bot that automatically reviews pull requests using workspace skills. The bot loads coding standards from skill files and provides structured feedback. You'll learn how to create a workspace with a skills directory, define an [Agent Skill](https://agentskills.io) with review instructions and reference files, and connect it to an agent that performs automated reviews.
 
@@ -75,7 +75,7 @@ Inside `workspace/skills/code-standards`, create a `references` folder to hold r
 - Files: `kebab-case.ts`
 - Booleans: Start with `is`, `has`, `should`
 
-## Code Organization
+## Code organization
 
 ```typescript
 // 1. Imports
@@ -96,7 +96,7 @@ function doSomething() {}
 export { doSomething }
 ```
 
-## Error Handling
+## Error handling
 
 Always handle errors explicitly - never silently catch.
 

package/.docs/guides/guide/dev-assistant.md

@@ -1,4 +1,4 @@
-# Building a Dev Assistant
+# Building a dev assistant
 
 In this guide, you'll build a complete development assistant that combines all workspace features:
 
@@ -123,7 +123,7 @@ description: Project coding standards and testing guidelines
 
 # Coding Standards
 
-## Code Quality
+## Code quality
 
 - Functions under 50 lines
 - Use descriptive variable names
@@ -135,7 +135,7 @@ description: Project coding standards and testing guidelines
 - Use AAA pattern: Arrange, Act, Assert
 - Cover happy paths and edge cases
 
-## Before Committing
+## Before committing
 
 1. Write implementation
 2. Write comprehensive tests
@@ -148,7 +148,7 @@ Create a reference file at `workspace/skills/coding-standards/references/testing
 ````markdown
 # Testing Guide
 
-## AAA Pattern
+## AAA pattern
 
 ```typescript
 it('descriptive test name', () => {
@@ -163,7 +163,7 @@ it('descriptive test name', () => {
 })
 ```
 
-## What to Test
+## What to test
 
 - Happy paths (normal inputs)
 - Edge cases (empty, null, boundary values)

package/.docs/guides/guide/docs-manager.md

@@ -1,4 +1,4 @@
-# Building a Docs Manager
+# Building a docs manager
 
 In this guide, you'll build a documentation manager that maintains your project's docs. It creates well-structured markdown files, keeps documentation organized, and prevents accidental overwrites. You'll learn how to set up a workspace filesystem, create an agent with document management instructions, and use it to generate and update documentation through conversational prompts.
 
@@ -65,7 +65,7 @@ Quick start guide for the project.
 npm install example-package
 ```
 
-## Quick Example
+## Quick example
 
 ```typescript
 import { Example } from 'example-package'
@@ -193,7 +193,7 @@ export const authConfig = {
 }
 ```
 
-## Basic Example
+## Basic example
 
 ```typescript
 import { createAuth } from '@example/auth'