export-design-system

export-design-system is a command for Claude Code from PMDevSolutions/Aurelius. It costs 0 tokens per session (1,084 once invoked), scanned A, original, MIT.

A command that packages a project's generated components and design tokens into a publishable pnpm workspace. It creates a framework-independent token package and a library for the project's web or React Native framework.

In plain words
What is it for?
Use it to export a design system for publishing or reuse across applications, choose an output folder or package scope, preview the export, or replace an existing export.
Why use it?
It removes the manual work of turning project files into reusable packages and setting up the appropriate build output. It also checks for required tokens, components, and framework information before exporting.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/export-design-system.sh [resolved flags].

Good fit Use it to export a design system for publishing or reuse across applications, choose an output folder or package scope, preview the export, or replace an existing export.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius
agentmods
npx agentmods add commands/pmdevsolutions/aurelius/export-design-system

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.

agentmods badge for export-design-system

README.md
[![agentmods](https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/export-design-system/github.svg)](https://agentmods.dev/commands/pmdevsolutions/aurelius/export-design-system)
Your own site
<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/export-design-system"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/export-design-system/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.

agentmods 80×15 button for export-design-system

Your own site · 80×15
<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/export-design-system"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/export-design-system.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 1,084 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01084
Opus 5.5 $0.00000 $0.00434
Sonnet 5.5 $0.00000 $0.00217
Haiku 4.5 $0.00000 $0.00108

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

Security

Grade A, and why

export-design-system 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 1mo 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/export-design-system.md · 111 lines

How it starts

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

/export-design-system — Export Components as a Publishable Library

Export the generated components and design tokens from this project as a publishable pnpm workspace with a framework-agnostic token package and a framework-specific component library (Vite library mode for web, tsc for React Native).

Input

$ARGUMENTS — optional flags forwarded to the export script. Common patterns:

  • (none) — default: detect framework from build-spec.json, scope from package.json, output to dist/design-system/.
  • --scope @acme — override the npm scope.
  • --output packages/design-system — pick a different output location.
  • --framework vue — override detected framework.
  • --dry-run — preview without writing.
  • --force — overwrite existing output dir.
  • --json — machine-readable summary.

Preconditions

This command requires:

  1. design-tokens.lock.json in src/styles/ or project root (produced by the design-token-lock skill or any of the /build-from-* pipelines).
  2. At least one component in src/components/ (or pass --components-dir).
  3. Framework discoverable via build-spec.json (outputTarget), package.json deps, or --framework flag.

If any precondition is missing, stop and tell the user which one and how to fix it (run a build pipeline, pass a flag, etc.) — do not attempt to repair the project automatically.

Steps

1. Sanity check inputs

Run a quick detection pass before invoking the skill:

test -f src/styles/design-tokens.lock.json || test -f design-tokens.lock.json
ls src/components 2>/dev/null | head -1

If lockfile is missing, surface the error and recommend running /build-from-figma, /build-from-canva, or /build-from-screenshot first.

2. Confirm scope and output (only if user did not pass them)

If the user did not provide --scope or --output, ask them once via AskUserQuestion:

  • Scope: "What npm scope should the packages publish under? (e.g. @acme)" — default to the value detected from the project's package.json, or @my-app.
  • Output dir: offer dist/design-system as the default and let them confirm or override.

Read the full file on GitHub · 111 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.

  1. 1mo ago First seen · 111 lines · 0 tokens per session scan A 29b55f7644df

Subscribe to this mod's changes

export-design-system is a command published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,084 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-09-04.

Related

Other commands, from other repositories