The Bulk Markdown Export feature lets you download your entire styleguide — every page plus your linked design tokens — as a single bundle of Markdown files in one click. It's currently in beta.

If your setup allows it, the zeroheight MCP server gives agents live access to your styleguide with no manual re-export. Bulk Markdown Export is the right choice when MCP isn't an option — restricted networks or agents that only read local files — and when you want a pinned, versioned snapshot of a specific release checked into your repo.

Where the per-page Markdown Export turns one page into AI-ready context, Bulk Markdown Export packages the whole design system at once. The result is a ZIP of clean .md files, organised into folders that mirror your styleguide's navigation, ready to drop into a codebase and hand to a coding agent.

This is particularly useful for teams that cannot enable MCP but still want their full design system available to LLMs and coding agents as structured, machine-readable, local context.

The controls live on the Markdown tab in styleguide settings, alongside the per-page export options:

Generating an export

Bulk export lives in Styleguide settings → Markdown, under the Export styleguide as markdown section. (The same tab also holds the per-page Enable MD export controls and AI-tool toggles.)

1. Open Styleguide settings → Markdown and scroll to Export styleguide as markdown.
2. Under Select which release to export, pick what to export. It defaults to your styleguide’s default release — the content your viewers currently see. If you haven’t set a default release, it defaults to Latest. You can also pick a specific release (V1, V2, …) to export that instead.
3. Click Export. The export is generated in the background, so you can leave the page while it builds.
4. The export appears in the table below as a row showing Release, Status (e.g. Ready), and Last exported time, with Download and Delete actions. Click Download to get the ZIP.

💡 What gets exported. The export mirrors the content your viewers currently see.

Latest: your current live content where your latest saved edits are included automatically.

A specific release: the export is a copy of the selected release.

Completed exports appear in the table, ready to download or delete. Each one is a snapshot from when you clicked Export — it doesn’t update as your content changes. Re-export to pick up newer changes.

Each release has a single export row. Re-running an export for the same release refreshes that row rather than creating a new one, and you can delete an export at any time:

What's in the export

The download is a ZIP named markdown-export-{styleguide}.zip containing:

• A README.md at the root that orients an AI agent — it states the folder is a design system to style with (not content to search) and points the agent to tokens/ and components/ first.
• One .md file per page, placed in a folder tree that mirrors your styleguide's navigation and category hierarchy — so the structure a reader sees on the site is the structure an agent sees on disk.
• A tokens/ folder holding your linked design token sets, split one file per collection mode (the filename shows the collection and mode, e.g. tokens-<set>-<collection>-<mode>.md). Values are resolved (e.g. a hex), not raw {reference} aliases, so they're usable as-is.

Hidden tabs and hidden content are excluded from the export — the same policy that applies to per-page Markdown, MCP, and the API. Exported content only ever contains what a viewer could already see.

Using the export as local context for coding agents

The export is designed to be an AI-facing indexing surface — a plain, structured copy of your design system that a coding agent can read directly from the filesystem. It leads with a README.md that tells the agent what the export is and how to use it, so much of the orienting is handled for you. A typical workflow:

1. Download and unzip the export into your project — for example into a design-system/ or docs/design-system/ folder at the repo root.
2. Commit it (or add it to the folder your agent already reads). Because the folder tree mirrors your styleguide navigation, an agent can navigate it the same way a person navigates the docs site.
3. Point your agent at it. In tools that read a project instructions file — such as CLAUDE.md (Claude Code) or AGENTS.md — add a line telling the agent where the design system lives, e.g. "Design system docs and tokens are in design-system/. Consult them before writing UI code."
4. Refresh when the design system changes. Re-export and replace the folder to keep the local copy in sync.

This gives a coding agent grounded, offline context for tasks like:

• Summarising guidelines before applying them
• Validating UI decisions against documented standards
• Generating implementation examples aligned with your tokens and component rules
• Answering "how should this look/behave?" from the design system as the source of truth