What is design-screen?

A command for designing a product screen as a reusable React component. It checks for the written requirements, sample data, type definitions, and available product sections before starting.

Use it to create a screen design for a product section that already has its specification, sample data, and TypeScript types.

It prevents screen design work from starting without the information needed to make the component fit the product.

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/design-screen.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/design-screen/github.svg)](https://agentmods.dev/commands/buildermethods/design-os/design-screen)

Your own site

<a href="https://agentmods.dev/commands/buildermethods/design-os/design-screen"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/design-screen/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/design-screen"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/design-screen.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 2,443 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.02443
Opus 5.5	$0.00000	$0.00977
Sonnet 5.5	$0.00000	$0.00489
Haiku 4.5	$0.00000	$0.00244

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

Security

Grade A, and why

design-screen 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/design-screen.md · 310 lines

How it starts

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

Design Screen

You are helping the user create a screen design for a section of their product. The screen design will be a props-based React component that can be exported and integrated into any React codebase.

Step 1: Check Prerequisites

First, identify the target section and verify that spec.md, data.json, and types.ts all exist.

Read /product/product-roadmap.md to get the list of available sections.

If there's only one section, auto-select it. If there are multiple sections, use the AskUserQuestion tool to ask which section the user wants to create a screen design for.

Then verify all required files exist:

product/sections/[section-id]/spec.md
product/sections/[section-id]/data.json
product/sections/[section-id]/types.ts

If spec.md doesn't exist:

"I don't see a specification for [Section Title] yet. Please run /shape-section first to define the section's requirements."

If data.json or types.ts don't exist:

"I don't see sample data for [Section Title] yet. Please run /sample-data first to create sample data and types for the screen designs."

Stop here if any file is missing.

Step 2: Check for Design System and Shell

Check for optional enhancements:

Design Tokens:

Check if /product/design-system/colors.json exists
Check if /product/design-system/typography.json exists

If design tokens exist, read them and use them for styling. If they don't exist, show a warning:

"Note: Design tokens haven't been defined yet. I'll use default styling, but for consistent branding, consider running /design-tokens first."

Shell:

Check if src/shell/components/AppShell.tsx exists

If shell exists, the screen design will render inside the shell in Design OS. If not, show a warning:

"Note: An application shell hasn't been designed yet. The screen design will render standalone. Consider running /design-shell first to see section screen designs in the full app context."

Step 3: Analyze Requirements

Read and analyze all three files:

Read the full file on GitHub · 310 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 · 310 lines · 0 tokens per session scan A 5cf8a3270997

Subscribe to this mod's changes

design-screen 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 2,443 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 Frontend React

design-screen next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
design-screenbuildermethods/design-os	Command	1.9k	1mo ago	MIT	A	0	Claude Code
design-importyonatangross/orchestkit	Command	299	yesterday	MIT	A	47	Claude Code, Cursor
gen-videoAdityaraj0421/naksha-studio	Command	353	19d ago	MIT	A	56	Claude Code
design-reviewjezweb/claude-skills	Command	1.1k	28d ago	MIT	A	14	Claude Code
color-palettejezweb/claude-skills	Command	1.1k	28d ago	MIT	A	9	Claude Code
icon-set-generatorjezweb/claude-skills	Command	1.1k	28d ago	MIT	A	9	Claude Code
ux-extractjezweb/claude-skills	Command	1.1k	28d ago	MIT	B	16	Claude Code

design-os: Command for Claude Code