MultiClaude: Command for Claude Code

.claude/commands/ipa/bd.md

bd is a command for Claude Code from nguyennguyenit/MultiClaude. It costs 17 tokens per session (2,597 once invoked), scanned A, original, MIT.

A command that creates a UI specification document from an existing system requirements document. It adapts the design details to the project's type, such as a web app, desktop app, CLI tool, or chatbot.

In plain words
What is it for?
Use it to create docs/UX_SPEC.md, including screen or command details, responsive behaviour, platform conventions, and optional design references. It requires docs/SRD.md.
Why use it?
It turns approved requirements into a focused description of screens, interactions, and user journeys. This is useful when you need only the UI document instead of the full design-document sequence.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is nguyennguyenit/MultiClaude's own configuration. It tells Claude Code how to work on MultiClaude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MultiClaude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nguyennguyenit/MultiClaude. 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/nguyennguyenit/MultiClaude/master/.claude/commands/ipa/bd.md
Clone the repo
git clone --depth 1 https://github.com/nguyennguyenit/MultiClaude

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.

agentmods badge for bd

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/bd.svg)](https://agentmods.dev/commands/nguyennguyenit/multiclaude/bd)
Your own site
<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/bd"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/bd.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 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,597 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.02597
Opus 5 $0.00009 $0.01299
Sonnet 5 $0.00003 $0.00519
Haiku 4.5 $0.00002 $0.00260

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

Security

Grade A, and why

bd 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.

.claude/commands/ipa/bd.md · 394 lines

How it starts

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

💡 TIP: Use /ipa:spec instead to generate both SRD.md + UI_SPEC.md in one step.

This command is kept for granular control when you only need UI_SPEC.md.

Prerequisite: docs/SRD.md must exist.


Purpose

Generate Basic Design (外部設計) following IPA standard with:

  • Customer Journey Experience (CJX)
  • Design reference support (URL/image)
  • Platform-specific UX patterns

Output: docs/UX_SPEC.md


Project Type Detection

Project Type UX Spec Focus CJX Adaptation
Web App Screens, components, responsive Visual journey
Desktop App Windows, dialogs, menus Productivity journey
CLI Tool Commands, output, prompts Task completion journey
MCP Server Tool descriptions, prompts Developer journey
Chatbot/RAG Conversation flows, responses Query resolution journey
Library/SDK API docs, examples Integration journey

Input

Required:

  • docs/SRD.md

Optional:

  • $ARGUMENTS = Reference URL or image path for design inspiration
  • docs/tech-stack.md

User Research Integration

Before starting UI design, check for USER_RESEARCH.md:

if docs/USER_RESEARCH.md exists:
  1. Read personas and journey maps
  2. Map journey stages to screens
  3. Add "Design Rationale" to each screen
  4. Apply emotional design (CJX)
else:
  Proceed with UI design (without rationale)

For each screen, add Design Rationale section:

### S-XX: [Screen Name]

**Journey Stage:** [Discovery/Onboarding/Usage/Retention/Advocacy]
**User Emotion:** [From journey map]
**Persona:** [Which persona uses this screen]

**Design Rationale:**
- Decision 1: [Why] (addresses [pain point/goal from persona])
- Decision 2: [Why]

[Rest of screen spec...]

Example:

### S-02: Dashboard

**Journey Stage:** Usage (Engaged → Productive)
**User Emotion:** Focused, wants efficiency
**Persona:** Sarah (SaaS PM)

**Design Rationale:**
- Quick actions prominent: Sarah values speed (persona behavior)
- Data visualization: Sarah is data-driven, needs metrics at a glance
- Minimal navigation: Reduce tool-switching overhead (persona pain point)

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

  1. 6d ago First seen · 394 lines · 17 tokens per session scan A 3bc98e9cd734

Subscribe to this mod's changes

bd is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 25d ago), licensed MIT. It adds 17 tokens to every session and 2,597 once invoked, about $0.0001 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-30.