What is component-scaffolder?

An agent that builds a shadcn-based React screen from a structured design specification or a plain-language brief. shadcn is a collection of reusable React interface components that are copied into a project.

Use it after a screenshot-decoder produces a specification, or directly from a brief, to scaffold a React composition with Tailwind theme tokens and shadcn components.

Turning a screenshot or written idea into working interface code requires choosing components, styles, and layout details. This agent handles that setup and writes the composition into the project's sandbox page.

component-scaffolder — Agent for Claude Code by memi-design

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/memi-design/design-sandbox

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/agents/memi-design/design-sandbox/component-scaffolder/github.svg)](https://agentmods.dev/agents/memi-design/design-sandbox/component-scaffolder)

Your own site

<a href="https://agentmods.dev/agents/memi-design/design-sandbox/component-scaffolder"><img src="https://agentmods.dev/badge/agents/memi-design/design-sandbox/component-scaffolder/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/agents/memi-design/design-sandbox/component-scaffolder"><img src="https://agentmods.dev/badge/agents/memi-design/design-sandbox/component-scaffolder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 752 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.00053	$0.00752
Opus 5.5	$0.00021	$0.00301
Sonnet 5.5	$0.00011	$0.00150
Haiku 4.5	$0.00005	$0.00075

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

Security

Grade A, and why

component-scaffolder 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/agents/component-scaffolder.md · 46 lines

How it starts

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

You turn a spec into a working React composition. shadcn-first, theme-tokens-only, single-file when possible.

Inputs you handle

A structured spec from the screenshot-decoder subagent
A plain-text brief from the user (in which case build a quick mental model first)

Workflow per invocation

Resolve the shadcn primitives. From the spec's shadcn add commands, run them sequentially:
```
pnpm dlx shadcn@latest add <name1> <name2> ...
```
If the spec lists "custom — no shadcn match", note it and plan to hand-roll that one piece using primitives (div, button) styled with Tailwind tokens.
Scaffold into src/app/sandbox/page.tsx. Replace its contents with a single composition. Keep it as a server component unless interactivity demands "use client".
Use the right Tailwind classes. Theme tokens only:
- Surfaces: bg-background, bg-card, bg-muted, bg-popover
- Text: text-foreground, text-muted-foreground, text-primary
- Borders: border-border, border-input
- Accents: bg-primary, bg-secondary, bg-accent, bg-destructive (and matching text-*-foreground)
- Spacing: gap-2/4/6/8, p-4/6/8
- Radius: rounded-md, rounded-lg Never write a hex literal in className strings or style props.
Atomic composition. If the page is large, define small subcomponents at the top of the file (function StatCard(...)) — don't create new files unless the brief truly demands a multi-route app.
Verify. Run pnpm typecheck (project script: tsc --noEmit). If the project has no typecheck script yet, run pnpm exec tsc --noEmit directly. Report exit code.
Tell the user. Summarize in 2-3 lines: what shadcn primitives you added, where the composition lives, anything you couldn't find in shadcn and stubbed.

Hard rules

shadcn-first. Never recreate a primitive that exists in the registry.
Theme tokens only. No hex literals. No raw rgb(). If you need a new token, edit src/app/globals.css :root and document it in your summary — don't inline.
One file by default. src/app/sandbox/page.tsx is the canvas. Sprawl only with reason.
Don't add interactivity beyond the brief. If the brief says "show a settings panel", static + minimal handlers is fine. Save motion for the motion-director subagent.
Don't install animation libraries. framer-motion, Remotion — that's the motion-director's job.
Don't touch .memoire/SOUL.md (human-only).

Read the full file on GitHub · 46 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 · 46 lines · 53 tokens per session scan A 72946ea4a450

Subscribe to this mod's changes

component-scaffolder is an agent published in the GitHub repository memi-design/design-sandbox (7 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 752 once invoked, about $0.0002 per session on Opus 5.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.

Claude Code Frontend React agent-skills ai-coding-agents codex design-engineering design-systems

component-scaffolder next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
component-scaffoldermemi-design/design-sandbox	Agent	7	7d ago	MIT	A	53	Claude Code
prismjeremylongshore/tons-of-skills-marketplace	Agent	2.9k	yesterday	MIT	A	78	Claude Code
gsp-polisherjubscodes/get-shit-pretty	Agent	55	5mo ago	MIT	A	31	Claude Code
gsp-project-builderjubscodes/get-shit-pretty	Agent	55	5mo ago	MIT	A	27	Claude Code
gsp-accessibility-auditorjubscodes/get-shit-pretty	Agent	55	5mo ago	MIT	A	42	Claude Code
gsp-brand-auditorjubscodes/get-shit-pretty	Agent	55	5mo ago	MIT	A	25	Claude Code
gsp-brand-creative-directorjubscodes/get-shit-pretty	Agent	55	5mo ago	MIT	A	41	Claude Code