Skip to main content
command CX Codex

visual · syahiidkamil — Claude Code command: what it does, how to install

The visual command turns a discussion into a self-contained HTML document with diagrams, wireframes and matrices the agent implements from in plan mode.

no license ★ 406 updated 2026-11-01

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/visual.md
Open on GitHub

What visual does

The command asks questions to clarify scope, approach and edge cases, then writes the result into plan.html — a single file that opens in a browser and is read by the agent. Inside: Mermaid diagrams for flows and data schemas, wireframes for UI, state and permission matrices, short prose where visuals fall short.

Run it with a description or without an argument — it will ask what to plan. If the codebase needs exploration first, it delegates to the built-in Explore subagent. The plan lands in docs/plans/{number}-{slug}/plan.html inside the project; if there is one project, it does not ask. Diagrams render via Mermaid CDN, no other dependencies.

What it helps with

  • capture an architectural decision as a visual artifact
  • gather questions on unclear edges before writing code
  • document a UI flow with loading and error states for plan mode
  • record a migration or refactor as a diagram with notes

Example prompts for the agent

  • run visual and plan the auth module refactor
  • visual — make a plan for adding PDF export
  • do visual for the REST to GraphQL migration

How to install visual

Manually: put the files in place

.claude/commands/visual.md

Call it with /visual. For all projects use ~/.claude/commands/

Questions about visual

How to install visual in Claude Code?

Create a .claude/commands/visual.md file at the project root and put the command content from the repository there.

What does the visual command do?

It asks questions about the task, clarifies scope and approach, then generates plan.html with diagrams, wireframes and matrices — one self-contained file the agent works from in plan mode.

Where is the plan saved after running visual?

Into docs/plans/{number}-{slug}/plan.html inside the project. The number is the next available (01, 02, 03), the slug comes from the plan subject.

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

visual by other authors comes first.

From the same set26

The whole set →
code-review code-review — a subagent for Claude Code that reviews a pull request through gh and posts a comment listing confirmed bugs. Skips closed, draft, or already-reviewed PRs without prompting. CX Codex ★ 406repo stars change-core-self change-core-self asks you about the project, works out a fitting identity for the agent from scratch, and stores it as a rule file loaded on every session. CX Codex +1 ★ 406repo stars grader grader assesses agent execution transcripts and generated files against expectations, flags superficial passes, and critiques test assertions. CX Codex ★ 406repo stars create-phase The create-phase command clarifies a development phase through Q&A, then creates an HTML wireframe with the decisions needed for implementation in Claude Code plan mode. CX Codex +1 ★ 406repo stars oneshotapp oneshotapp builds a functioning app from a brief idea in Claude Code without human intervention. It logs architecture choices and verifies implementation slices on the fly. CX Codex +1 ★ 406repo stars analyzer analyzer examines blind skill comparisons to explain the winner’s advantage and suggest changes to the losing skill. Run it after the comparator finishes. CX Codex ★ 406repo stars free-will free-will makes the agent stop at a costly fork, lay out real options, test each against evidence and pick one on purpose. CX Codex +1 ★ 406repo stars design Defines visual identity tokens and styling rationale following Google Stitch. Keeps coding agents aligned with design tokens when building user interfaces. CX Codex +1 ★ 406repo stars

Project sponsors

Companies that keep this analytics open