A command that creates a Markdown design specification for a web page in the design/pages folder. It describes the page instead of generating its code.

Use it to specify landing, pricing, signup, about, blog, portfolio, shop, product, or careers pages before building them.

It turns a page idea into a checked design brief before implementation and stops when the required design foundation files are missing.

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

Your own site

<a href="https://agentmods.dev/commands/app-builders-club/design-builder/design_page"><img src="https://agentmods.dev/badge/commands/app-builders-club/design-builder/design_page/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/app-builders-club/design-builder/design_page"><img src="https://agentmods.dev/badge/commands/app-builders-club/design-builder/design_page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 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,946 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.00032	$0.02946
Opus 5	$0.00016	$0.01473
Sonnet 5	$0.00006	$0.00589
Haiku 4.5	$0.00003	$0.00295

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

Security

Grade A, and why

design_page 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 9d 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/design_page.md · 182 lines

How it starts

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

/design-builder:design_page — generate a web page spec

You produce a design specification (markdown) for a web page. The spec lands in design/pages/<name>.md. You do NOT emit code — that's /design-builder:build's job. Activate the design skill (skills/design/SKILL.md).

The user's argument names the page — e.g. landing, pricing, about, signup. Map natural language to a page_type value from the 11 valid inspiration_pages page_types (marketing_landing, pricing, signup, about, blog_index, blog_post, portfolio, ecommerce_home, product_listing, product_page, careers).

Phase 1 — System check (BLOCKING)

Read these three files from design/:

design/design-system.md
design/style-guide.md
design/content-library.md

If any of the three is missing → stop. Single message:

"Missing foundation files. Run /design-builder:setup first — it produces the three files this command depends on."

If all three exist: read them fully. Capture for use later in this run:

Stack (from design-system.md ## Stack).
Palette role mappings, typography, motion dial, anti-pattern bans (from design-system.md).
Contrast rules, touch targets, platform constraints (from style-guide.md).
Voice & tone principles, state patterns (from content-library.md).

Also read design/.cache/interview.json for dial values (DENSITY, MOTION_INTENSITY, VARIANCE).

Phase 2 — Documentation check

One free-form question to the user:

"Got documentation / PRD / brief for this page? (paste / file path / Figma URL / Notion URL / nothing)"

Branch on the response:

File path: Read the path. Capture the full content as the page's source-of-truth for purpose, features, content.
Pasted text: Capture verbatim from chat.
Figma URL: Call mcp__plugin_design-builder_figma__get_design_context and get_screenshot. Capture metadata + screenshot.
Notion / external URL: if the URL is not Figma, ask user to paste the relevant content (we don't have generic web-fetch in this command's allowed tools).
Nothing: proceed to Phase 2b (content interview).

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

9d ago First seen · 182 lines · 32 tokens per session scan A ee79f2cdef51

Subscribe to this mod's changes

design_page is a command published in the GitHub repository app-builders-club/design-builder (4 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 2,946 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.

Design and UX claude-code-plugin design-skill

design_page

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:design_page — generate a web page spec

Phase 1 — System check (BLOCKING)

Phase 2 — Documentation check

What this file has done since we first saw it

Other commands, from other repositories

octo-design-ui-ux

verify

design-tutorial

figma-component-library

anti-slop-designer

theme