Claude Code Slash Commands · page 2

ux-designer agent

Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".

Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"

Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"

Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"

Edit an existing PRD. Use when the user says "edit this PRD".

Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"

Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".

Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"

Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"

Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"

Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".

Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose

Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure

Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now

Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder

Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.

Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something

Run code quality checks on a directory

Check if documentation is in sync with code

Review a pull request using project standards

Generate a summary for the current branch changes

Work on a JIRA/Linear ticket end-to-end

Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.

Commit changes following Conventional Commits format (local only, no push).

Create a new project from template with uv and Git initialization

Archive, detach, purge, or rename KB objects while keeping registry, index, and links consistent.

Refresh the auto index block inside 02-Index.md without overwriting curated content.

Ingest external material into Sources/* inside the bound project KB, then update registry, index, and daily note as needed.

Initialize or rebuild a vault-first, project-scoped Obsidian KB under Research/{project-slug}/ for the current repository.

Repair or strengthen wikilinks among canonical KB notes without generating extra artifact sprawl.

Run deterministic KB health checks and rewrite _system/lint-report.md.

Run the project-scoped literature workflow from Sources/Papers into Knowledge, Writing, and Maps/literature.canvas.

Update the current project Daily note and, when needed, the plan, hub, and runtime binding summary.

Generate or repair derived KB artifacts such as literature.canvas, optional Bases, or other explicit map outputs.

Promote durable content from Daily or source notes into canonical Knowledge, Experiments, Results, Results/Reports, or Writing notes.

Summarize the current bound project KB status, including registry counts and key project note paths.

Run deterministic KB maintenance to refresh scaffold integrity, registry, index, daily note, and runtime binding summary.

Read one or more papers and update the active installed paper-miner writing memory with reusable writing patterns, structure signals, reusable phrasing, venue-specific signals, and rebuttal-friendly language.

Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.

Design academic poster for conference

Create conference presentation slides quickly

Draft research promotion content and optionally publish approved X posts

Start systematic review response workflow for professional rebuttal writing

Initialize a research project with Zotero-integrated literature review. Creates or audits project-scoped sources, generates research question cards, and only writes a research proposal when the evidence gate passes.

Configure your preferred package manager (npm/pnpm/yarn/bun)

Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.

Commit changes with Conventional Commits format and push to GitHub remote repository.

Check and update CLAUDE.md memory based on changes to skills, commands, agents, and hooks.

Update README documentation and push changes to GitHub.

Batch read papers from Zotero and create/update detailed reading notes, preferably inside the bound Obsidian project knowledge base

Read and analyze papers from a Zotero collection, then synthesize them into the bound Obsidian project knowledge base or markdown review outputs

Sweep a corrected fact through the vault — finds every note restating it, applies the correction at the single source, replaces restatements with links, and preserves notes that correctly record what was believed at the time.

Freeform capture mode. Dump anything — conversations, decisions, incidents, wins, thoughts — and I'll route it all to the right notes with proper templates, frontmatter, and wikilinks.

Voice-calibrated editing — makes Claude-drafted text sound like you wrote it, not like AI wrote it.

Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.

Prep for any meeting by topic — subject-forward briefing with open tasks, blockers, and brainstormed considerations the user may not have thought of yet.

Prep for an upcoming 1:1 — load person context, surface open items, suggest agenda based on vault state.

Morning kickoff. Load today's context, review yesterday, surface open tasks, and identify priorities.

Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits oversized notes, reports stale open loops, fixes links. Safe by construction: never deletes, never commits, zero content loss.

Weekly synthesis — cross-session review of vault activity, North Star alignment, patterns, uncaptured wins, and forward priorities.

Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo]

Build an exploit chain — given bug A, finds B and C to combine for higher severity and payout. Knows common chain patterns: IDOR→ATO, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth. Usage: /chain

Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt *.target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome]

On-demand intelligence fetch for a target — CVEs, disclosed reports, new features. Pulls NVD/GitHub-Advisory CVEs + bundled disclosed reports + hunt memory context. Usage: /intel target.com

Inspect or rotate the autopilot ledger JSONL files (findings.jsonl, negatives.jsonl). Caps file size and keeps N rotated backups so memory does not grow unbounded.

Pick up a previous hunt on a target — shows hunt history and untested surface from the autopilot ledger. Usage: /pickup target.com

Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/<target>/ directory. Usage: /recon target.com

Optional manual note on a target or the last confirmed finding. Capture is automatic during autopilot; this is for extra context. Usage: /remember

Write a submission-ready bug bounty report. Generates H1/Bugcrowd/Intigriti/Immunefi format with CVSS 3.1 score, proof of concept, impact statement, and remediation. Run /validate first. Usage: /report

Show ranked attack surface for a target from its recon manifest + hunt memory. Deterministic backing is `cbh surface <target>` (reads recon/<target>/manifest.json); LLM layer adds ledger signal. Usage: /surface target.com

Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan <contract_path_or_dir> [--chain solana]

Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage

Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate

Smart contract security audit — runs through 10 bug class checklist (accounting desync, access control, incomplete path, off-by-one, oracle errors, ERC4626, reentrancy, flash loan, signature replay, proxy/upgrade). Applies pre-dive kill signals first. Generates Foundry PoC template for confirmed findings. Usage: /web3-audit <contract.sol>

Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope <asset> [<asset> ...]

Create a new obsidian-second-brain command via interview - zero markdown editing required

Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is worth working on next

Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep (which is open-web via Perplexity).

Generate a decision record when the vault structure changes - the vault knows why it knows what it does

Read Google Calendar and write an AI-first snapshot to the vault - today, week, next week, or a custom range

Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits

Show or update a kanban board - flags overdue items, updates from conversation

One calendar command with four modes - agenda (read a snapshot), reconcile (vault vs calendar gaps), meeting (event to note), schedule (task to event)

Quick idea capture - zero friction, saves to your ideas folder and mentions in daily note

Red-team your current idea against your own vault history - finds contradictions, past failures, and flawed assumptions

Bridge two unrelated domains using your vault's link graph - forces creative friction to spark new ideas