shadcn-plan-summary — Claude Code command: summarize UI planning
shadcn-plan-summary — a command that captures decisions from UI architecture sessions. Extracts choices about layout, flows, API integration, and state management, then compiles them into a structured report for the next development phase.
AGPL-3.0 ★ 267 updated 2026-02-20
.claude/commands/shadcn-plan-summary.mdWhat shadcn-plan-summary does
shadcn-plan-summary processes the full conversation history about interface design for an MVP: requirements, user screens, workflows, API integration strategy, and state handling. It identifies decisions by topic (responsiveness, accessibility, security), aligns them with model recommendations, and builds a structured markdown summary.
The output has four sections: enumerated decisions made during discussion, matched recommendations, a detailed planning summary (requirements, screens, integrations, gaps), and unresolved issues. This gives developers a solid starting point for implementation without losing the context of earlier design choices.
The command runs inside Claude Code and works best when your conversation history includes the product requirements document, tech stack, API plan, and the full Q&A exchange about UI architecture.
What it helps with
- extract decisions from a long UI design conversation
- align interface architecture choices with best practices
- identify gaps before coding begins
- hand off planning results to the implementation phase
Example prompts for the agent
- Run shadcn-plan-summary to pull together our UI architecture discussion into one report
- Use shadcn-plan-summary to capture all the interface design decisions we made
- Generate a structured summary of this planning session with shadcn-plan-summary
How to install shadcn-plan-summary
Manually: put the files in place
.claude/commands/shadcn-plan-summary.mdCall it with /shadcn-plan-summary. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/shadcn-plan-summary.mdCall it with /prompts:shadcn-plan-summary. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/shadcn-plan-summary.prompt.mdManually: put the files in place
.gemini/commands/shadcn-plan-summary.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about shadcn-plan-summary
How do I install shadcn-plan-summary in Claude Code?
Save the prompt to .claude/commands/shadcn-plan-summary.md in your project root. Claude Code will pick it up automatically. For other platforms: Codex uses ~/.codex/prompts/shadcn-plan-summary.md, GitHub Copilot uses .github/prompts/shadcn-plan-summary.prompt.md.
What does shadcn-plan-summary do?
It analyzes a UI planning session: pulls out design decisions, matches them to architecture recommendations, and produces a structured report covering requirements, screens, API integration strategy, and any unresolved questions.
What information does the command need to work?
Your conversation history should include the product requirements document, tech stack details, an API plan, and the recorded discussion with questions and answers. The command reads all of this and generates a markdown report.