ccprompt

A complete AI coding workflow in 8 slash commands. Not a template collection. A session lifecycle that turns Claude Code into a repeatable production system.

npx @ccprompt/cli install-generic .

The Problem

Most developers use AI like autocomplete: type a prompt, accept the output, move on. Then they wonder why their code has subtle bugs, their context gets lost between sessions, and they spend more time fixing AI mistakes than they save.

The data backs this up:

• Developers believe AI makes them 24% faster. They're actually 19% slower without a methodology (METR, randomized controlled trial)
• 96% don't trust AI code, but only 48% verify it. The gap is where bugs live (Sonar, 1,100+ developers)

The missing piece isn't better prompts. It's a workflow.

The Session Lifecycle

ccprompt installs 33 slash commands into Claude Code. Eight of them form a loop that runs every session:

/read-handover          Pick up where the last session left off
       |
/strategic-next         Decide what matters most right now
       |
/creative-brainstorm    Explore approaches before committing to one
       |
    [BUILD]             /feature-build, /quick-task, /debug-rootcause...
       |
/verify-thorough        Prove correctness: 5 verification layers
       |
/visual-verify          Prove it visually: screenshots, console, responsive
       |
/principles-check       Audit against your engineering standards
       |
/housekeeping           Clean up, consolidate, leave it better
       |
/low-context-handover   Save state for the next session

Every session starts at the top. Every session ends at the bottom. The middle adapts to whatever you're building. The handover connects one session to the next, so you never lose context.

Start simple, add layers

Week 1: Just use /kickoff to start and /low-context-handover to end. That alone puts you ahead.

Week 3: Add /read-handover and /verify-thorough. Now you're preserving context and catching bugs.

Month 2: Add /strategic-next and /visual-verify. Now you're building the right things and proving they work.

Month 4: The full 8-command loop. Plus multiple IDEs running parallel sessions.

The Parallelism Multiplier

The loop works for one project. It scales across projects: one project per IDE, multiple IDEs open simultaneously.

• IDE 1: Building a website
• IDE 2: Writing an ebook
• IDE 3: Developing a CLI tool
• IDE 4: Preparing marketing content

Each project runs its own lifecycle. Each produces its own handover. When you switch back to a project, /read-handover picks up exactly where you left off. Ten projects progressing simultaneously, zero context loss.

One developer. Portfolio-level output.

All 33 Commands

Session lifecycle (the core loop)

Building

Debugging and fixing

Quality and security

Thinking and planning

Operations

Setup

Every template supports $ARGUMENTS for passing context directly:

/debug-rootcause TypeError in UserService.create()
/feature-build add dark mode toggle
/refactor extract auth logic from UserController

How It Works

Templates are plain markdown files installed to .claude/commands/. Claude Code reads them as slash commands. No API key, no account, no setup beyond the one-liner.

Want project-specific prompts? ccprompt can scan your project and individualize each template with your actual file paths, commands, and conventions. This optional feature requires an Anthropic API key.

npm install -g @ccprompt/cli
ccprompt scan .
ccprompt generate myproject    # requires ANTHROPIC_API_KEY
ccprompt install myproject

Individualization example

Generic template:

## Step 2: Reproduce It
- Find the exact steps to trigger the issue
- Find the minimal reproduction
- Document the reproduction steps

After individualization (React + Remotion + Express project):

## Step 2: Reproduce It
- Find the exact steps to trigger the issue
- Find the minimal reproduction
- Document the reproduction steps

Project-specific reproduction workflow:
  # For video generation issues
  npm run dev                    # Open Remotion Studio
  npx remotion render video/index.ts CompositionName output/test.mp4

  # For web UI issues
  cd web && npm run dev          # Start frontend

  # For API issues
  npm run api:dev                # Start Express server

  # For test failures
  npm test                       # Run Vitest

The generic template is 113 lines. The individualized version is 191 lines, all project-specific.

CLI Commands

ccprompt install-generic [path]  # Instant setup, free, no API key needed
ccprompt templates               # List all 33 templates
ccprompt scan <path>             # Auto-detect and register project
ccprompt generate <project>      # Individualize (requires API key)
ccprompt install <project>       # Install as slash commands
ccprompt refresh <project>       # Rescan + regenerate + install (one step)
ccprompt install-all             # Install into all projects
ccprompt regenerate-all          # Refresh all after template changes
ccprompt list                    # List registered projects
ccprompt stats                   # Overview dashboard
ccprompt rescan <project>        # Re-scan (preserves manual edits)
ccprompt update <project>        # Update context fields
ccprompt copy <proj> <tmpl>      # Copy prompt to clipboard
ccprompt show <proj> <tmpl>      # View in terminal
ccprompt diff <proj> <tmpl>      # Compare original vs individualized
ccprompt new-template <name>     # Create custom template scaffold
ccprompt remove <project>        # Delete project

Keeping Prompts Up to Date

When your project evolves (new deps, new files, new conventions):

ccprompt refresh myproject    # rescan + regenerate + install in one step

Or for all projects:

ccprompt regenerate-all -y && ccprompt install-all

Troubleshooting

"command not found: ccprompt"

Global install didn't link properly. Use npx instead:

npx @ccprompt/cli install-generic .

Or reinstall globally:

npm install -g @ccprompt/cli

Slash commands don't appear in Claude Code

Make sure you ran install (or install-generic) in the right project directory. Claude Code reads from .claude/commands/ relative to your project root.

ls .claude/commands/    # should list .md files

Templates look generic after install-generic

That's expected. install-generic copies templates as-is. For project-specific prompts, use scan + generate + install (requires API key).

FAQ

Do I need an API key? No. install-generic works with zero configuration and is completely free. An API key is only needed for the optional individualization feature (generate).

Does this work with Cursor / other AI editors? The slash commands are specific to Claude Code's .claude/commands/ convention. The template markdown files themselves work anywhere. Copy and paste them into any AI assistant.

Can I edit templates after installation? Yes. They're plain markdown in .claude/commands/. Edit freely. Running install or install-generic again will overwrite them, so keep custom edits in a separate copy if needed.

Where can I learn the full methodology? The session lifecycle is part of the Paranoid Verification methodology. Learn more at codewithrigor.com.

Requirements

• Node.js 18+
• Claude Code (for using slash commands)
• Anthropic API key (optional, only for individualization)

License

MIT. See LICENSE.