What is export-product?

A command for packaging a Design OS product design for implementation, including the files needed for a developer handoff.

Use it when exporting a product's designs, roadmap, interface sections, data definitions, design tokens, and application shell for development.

It checks that the product overview, roadmap, and at least one designed section exist before producing the package, while warning about useful optional files that are missing.

How buildermethods/design-os configures Claude Code

About the project

Design OS is a product-planning and interface-design tool that guides an idea through product definition, data modeling, design-system choices, screen design, and implementation handoff. Teams use it to give coding agents a clear specification before development begins. Its catalogue add-ons support the guided planning and design workflow.

buildermethods/design-os · 1,876 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to buildermethods/design-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/buildermethods/design-os/main/.claude/commands/design-os/export-product.md

Clone the repo

git clone --depth 1 https://github.com/buildermethods/design-os

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/buildermethods/design-os/export-product/github.svg)](https://agentmods.dev/commands/buildermethods/design-os/export-product)

Your own site

<a href="https://agentmods.dev/commands/buildermethods/design-os/export-product"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/export-product/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/buildermethods/design-os/export-product"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/export-product.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 7,640 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.07640
Opus 5.5	$0.00000	$0.03056
Sonnet 5.5	$0.00000	$0.01528
Haiku 4.5	$0.00000	$0.00764

Measured 2mo ago against content hash 33d131dcaef7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

export-product scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/design-os/export-product.md · 1,029 lines

How it starts

The opening of the file, as written. The whole thing — 1,029 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Export Product

You are helping the user export their complete product design as a handoff package for implementation. This generates all files needed to integrate the UI designs into a real codebase.

Step 1: Check Prerequisites

Verify the minimum requirements exist:

Required:

/product/product-overview.md — Product overview
/product/product-roadmap.md — Sections defined
At least one section with screen designs in src/sections/[section-id]/

Recommended (show warning if missing):

/product/data-shape/data-shape.md — Product entities
/product/design-system/colors.json — Color tokens
/product/design-system/typography.json — Typography tokens
src/shell/components/AppShell.tsx — Application shell

If required files are missing:

"To export your product, you need at minimum:

A product overview (/product-vision)
A roadmap with sections (/product-roadmap)
At least one section with screen designs

Please complete these first."

Stop here if required files are missing.

If recommended files are missing, show warnings but continue:

"Note: Some recommended items are missing:

Product entities — Run /data-shape for consistent entity naming
Design tokens — Run /design-tokens for consistent styling
Application shell — Run /design-shell for navigation structure

You can proceed without these, but they help ensure a complete handoff."

Step 2: Gather Export Information

Read all relevant files:

/product/product-overview.md — Product name, description, features
/product/product-roadmap.md — List of sections in order
/product/data-shape/data-shape.md (if exists)
/product/design-system/colors.json (if exists)
/product/design-system/typography.json (if exists)
/product/shell/spec.md (if exists)
For each section: spec.md, data.json, types.ts
List screen design components in src/sections/ and src/shell/

Step 3: Create Export Directory Structure

Create the product-plan/ directory with this structure:

Read the full file on GitHub · 1,029 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 1,029 lines · 0 tokens per session scan A 33d131dcaef7

Subscribe to this mod's changes

export-product is a command published in the GitHub repository buildermethods/design-os (1,876 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,640 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Design and UX

export-product next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
export-productbuildermethods/design-os	Command	1.9k	1mo ago	MIT	A	0	Claude Code
profilecathrynlavery/diagram-design	Command	65k	3d ago	MIT	A	16	Claude Code
erne-animateJubaKitiashvili/everything-react-native-expo	Command	50	29d ago	MIT	A	21	Claude Code
ui-flow-reviewMRCalderon3D/everything-game-dev-code	Command	104	28d ago	MIT	A	15	Claude Code
responsive-design-specialistimsaif/design-with-claude	Command	11	yesterday	MIT	A	36	Claude Code
design-auditw2ur/claude-code-setup	Command	2	3d ago	MIT	A	30	Claude Code
ppt-image2-editable-rebuildwwe-dog/ppt-image2-editable-rebuild	Command	204	5mo ago	Unlicense	A	15	Claude Code

design-os: Command for Claude Code