Borrowing it
Nothing to install: this file belongs to karlng279/ai-ready-product-workflow-v2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/karlng279/ai-ready-product-workflow-v2/main/.claude/commands/design-pipeline.mdgit clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2Wrote 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.
[](https://agentmods.dev/commands/karlng279/ai-ready-product-workflow-v2/design-pipeline)<a href="https://agentmods.dev/commands/karlng279/ai-ready-product-workflow-v2/design-pipeline"><img src="https://agentmods.dev/badge/commands/karlng279/ai-ready-product-workflow-v2/design-pipeline/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.
<a href="https://agentmods.dev/commands/karlng279/ai-ready-product-workflow-v2/design-pipeline"><img src="https://agentmods.dev/badge/commands/karlng279/ai-ready-product-workflow-v2/design-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01118 |
| Opus 5 | $0.00000 | $0.00559 |
| Sonnet 5 | $0.00000 | $0.00224 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
design-pipeline 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-pipeline
Generate wireframes and component specs from User Story Details (USD) for a feature.
Usage
/design-pipeline [feature-name]
If feature-name is omitted, ask for it before starting. The USD files for the feature must already exist (features/{feature-name}/po/usd/ST-XXX.md).
What This Command Does
Executes the 2-stage design artifact pipeline for a feature. Each stage produces traceable design artifacts stored in features/{feature-name}/design/.
| Stage | Skill | Input | Output |
|---|---|---|---|
| 1 | design-wireframe |
usd/ST-XXX.md (AC-XXX) |
design/WF-XXX.md per screen |
| 2 | design-component-spec |
design/WF-XXX.md |
design/COMP-XXX.md per component |
Pre-flight Checks
Before starting, verify:
features/{feature-name}/po/usd/exists and contains at least oneST-XXX.mdfilefeatures/{feature-name}/design/folder exists (create if not)- Ask the user: "Which theme? (mds / corporate / ecommerce / erp) — default: mds"
- Ask: "Generate wireframes for all stories, or specific ones? (all / ST-001, ST-002, ...)"
If USD files are missing, stop and tell the user to run /po-pipeline first.
Execution Steps
Step 1 — Wireframes (design-wireframe)
For each selected story:
- Read
features/{feature-name}/po/usd/ST-XXX.md - Activate
design-wireframeskill - Identify the screens implied by the ACs (one wireframe per distinct screen or major view)
- Assign sequential WF-XXX IDs across all stories in this feature
- Generate
features/{feature-name}/design/WF-XXX.mdfor each screen
Each WF-XXX file must include:
- Metadata header (ID, screen name, story, ACs, theme)
- Text description (purpose, layout structure, key elements, interactions)
- ASCII wireframe (60–80 chars wide, using standard symbol set)
- Component list (ShadCN + custom + Tanstack if table present)
- Responsive behavior (desktop, tablet, mobile)
- AC Mapping table (every AC from the USD accounted for)
- YAML frontmatter
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.
- 12d ago First seen · 120 lines · 0 tokens per session scan A ce665243317e
design-pipeline is a command published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,118 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-31.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
team-ui
Orchestrate UI/UX design team.