A command that turns written design specifications into source code. It can process one specification, several specifications, or all matching specifications in a project.

Use it to generate code for pages and screens from files in the project's design/pages or design/screens folders.

It removes the need to manually translate approved page or screen descriptions into the initial code structure.

build — Command for Claude Code by app-builders-club

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/app-builders-club/design-builder

Made for: Claude Code.

Or install design-builder, the plugin that ships this one along with the rest of its 9 skills, 7 commands, 1 agent, 2 MCP servers.

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/app-builders-club/design-builder/build.svg)](https://agentmods.dev/commands/app-builders-club/design-builder/build)

Your own site

<a href="https://agentmods.dev/commands/app-builders-club/design-builder/build"><img src="https://agentmods.dev/badge/commands/app-builders-club/design-builder/build.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 2,911 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.00033	$0.02911
Opus 5	$0.00016	$0.01456
Sonnet 5	$0.00007	$0.00582
Haiku 4.5	$0.00003	$0.00291

Measured 6d ago against content hash a85e4df6a199, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

build 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 6d 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.

commands/build.md · 169 lines

How it starts

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

/design-builder:build — generate code from spec(s)

You read one or more design specs (design/pages/<name>.md and/or design/screens/<name>.md) and emit code to the user's source tree. You do NOT design — that's /design-builder:design_page and /design-builder:design_screen. Activate the design skill.

Phase 1 — Resolve target

Parse $ARGUMENTS:

Empty arg: list all spec files in design/pages/ and design/screens/. Present multi-select prompt:
"Available specs:
- pages/landing
- pages/pricing
- screens/onboarding Pick one or more (numbers, comma-separated; or all)"
Single name (e.g. landing): search design/pages/<name>.md first, then design/screens/<name>.md. If both exist: prefer pages/, warn user that screens/<name>.md was also found.
Explicit path (pages/landing or screens/onboarding): treat as the path.
all: glob design/pages/*.md + design/screens/*.md.
Glob (pages/onboarding-*): literal glob.

If 0 spec files resolved: stop with:

"No specs found. Run /design-builder:design_page <name> or /design-builder:design_screen <name> first."

If exactly 1 spec: single-spec mode. If N > 1: batch mode (Phase 4 batch behavior).

Phase 2 — Stack & system check (BLOCKING)

Read in order:

design/.cache/stack.json (Phase 0.5 of /setup).
design/design-system.md (## Stack section if .cache/stack.json is missing — fallback for migrated v2.0 projects, but log a warning that stack.json was missing).
design/style-guide.md (tokens, contrast rules, motion rules, anti-patterns full prose).
design/content-library.md (voice & tone, state patterns).

If stack.json says project_initialized: false:

"Project not initialized. Per design-system.md ## Stack, run the scaffold command first (it was suggested in /setup Phase 0.4). Re-run /build after scaffolding."

If foundation files (design-system, style-guide, content-library) are missing → stop and point to /setup.

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

6d ago First seen · 169 lines · 33 tokens per session scan A a85e4df6a199

Subscribe to this mod's changes

build is a command published in the GitHub repository app-builders-club/design-builder (4 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,911 once invoked, about $0.0002 per session on Opus 5. 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-31.

Building agents claude-code-plugin design-skill

build

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/design-builder:build — generate code from spec(s)

Phase 1 — Resolve target

Phase 2 — Stack & system check (BLOCKING)

What this file has done since we first saw it

Other commands, from other repositories

learn

init

brand-generate

genshijin-compress

standup

check-dev