# shadcn-ui-plan

shadcn-ui-plan turns a product requirements doc, API plan and planning session notes into a UI architecture saved to .ai/ui-plan.md.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 267 repo stars
- Author: przeprogramowani
- License: AGPL-3.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/przeprogramowani/ai-rules-builder/tree/HEAD/.claude/commands/shadcn-ui-plan.md
- Updated: 2026-02-20
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/shadcn-ui-plan

## What it does

The command reads through the product requirements document, the API plan and notes from a planning session, then pulls out the core requirements and the relevant API endpoints. From there it lists every screen the product needs, with its purpose, the main data shown, its components, and notes on UX, accessibility and security.

It also maps how a user moves between screens for the main use case, lays out the navigation structure, and names shared components reused across several views. Error states and edge cases get a mention too, so the plan isn't just the happy path.

Running it requires two files already in place, `@prd.md` and `@api-plan.md`, since the whole analysis is built on them. The output lands in `.ai/ui-plan.md`, written in Polish regardless of the project's own language.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/shadcn-ui-plan.md` — Call it with /shadcn-ui-plan. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/shadcn-ui-plan.md` — Call it with /prompts:shadcn-ui-plan. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/shadcn-ui-plan.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/shadcn-ui-plan.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/przeprogramowani/ai-rules-builder/tree/HEAD/.claude/commands/shadcn-ui-plan.md

## When to use it
- turn a PRD and API plan into a screen-by-screen UI architecture
- define the purpose and key components of each view
- map navigation and the user journey across screens
- spot shared components reused across multiple views
- account for edge cases and error states in a UI design

## Example prompts
- Run /shadcn-ui-plan against @prd.md and @api-plan.md, plus notes from today's planning session
- Build the UI architecture with /shadcn-ui-plan and save it to .ai/ui-plan.md
- Run /shadcn-ui-plan and check every user story from the PRD against the resulting screens

## Similar
- [shadcn](https://affpapa.org/en/nevibecode/skills/shadcn-ui-shadcn.md) — skill · 150100 installs
- [shadcn-svelte](https://affpapa.org/en/nevibecode/skills/shadcn-svelte.md) — skill · 7600 installs
- [shadcn-ui](https://affpapa.org/en/nevibecode/skills/nexu-io-shadcn-ui.md) — skill · 3100 installs
- [shadcn-component-review](https://affpapa.org/en/nevibecode/skills/shadcn-component-review.md) — skill · 676 installs
- [w-shadcn](https://affpapa.org/en/nevibecode/skills/w-shadcn.md) — skill · 647 installs
- [shadcn-component-discovery](https://affpapa.org/en/nevibecode/skills/shadcn-component-discovery.md) — skill · 773 installs

From the same set: [przeprogramowani/ai-rules-builder](https://affpapa.org/en/nevibecode/by/przeprogramowani/ai-rules-builder.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
