# shadcn-status-checkpoint

shadcn-status-checkpoint — a command that documents implementation progress for UI components in a structured markdown file. Keeps your work history clear when developing complex views across multiple AI conversations.

- 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-status-checkpoint.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-status-checkpoint

## What it does

The command writes a markdown snapshot to `.ai/{task-name}-implementation-status.md`, listing completed steps and next actions. This matters when UI work spans several Claude interactions—instead of re-explaining what's done, you hand off a clear checkpoint.

When invoked, Claude collects your progress notes, formats them into the file, and signals completion. The file stays in your repo as part of the project record.

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/shadcn-status-checkpoint.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-status-checkpoint.md

## When to use it
- Keep a record of component implementation progress across multiple sessions
- Document which steps are finished and what work remains
- Preserve context in a structured format for the next development phase

## Example prompts
- Save the current state of the Button component implementation as a checkpoint
- Record which parts of the login form are complete before moving forward
- Create a status snapshot before switching to the next UI section

## 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-vue](https://affpapa.org/en/nevibecode/skills/shadcn-vue.md) — skill · 6300 installs
- [shadcn-component-discovery](https://affpapa.org/en/nevibecode/skills/shadcn-component-discovery.md) — skill · 773 installs
- [shadcn-component-boundaries](https://affpapa.org/en/nevibecode/skills/shadcn-component-boundaries.md) — skill · 5700 installs
- [status](https://affpapa.org/en/nevibecode/commands/seth-hobson-status.md) — command · 348 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
