JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 69
  • Score
    100M100P100Q95391F
  • License MIT

39 structured AI coding prompts, installed as Claude Code slash commands.

Package Exports

  • @ccprompt/cli
  • @ccprompt/cli/promptm.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@ccprompt/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

ccprompt

npm version Tests License: MIT Node.js

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

npx @ccprompt/cli install .

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 39 slash commands into Claude Code. Eight of them form a core loop:

/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, /debug-rootcause, /refactor...
       |
/verify-thorough        7-layer falsification stack. Try to BREAK it.
       |
/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 39 Commands

New in 2.4.0: /verify-thorough rewritten as 7-layer falsification stack (was 5-layer). New /deep-scan — AI pattern recognition audit for large codebases. KNOWLEDGEBASE.md with research from formal methods, cognitive science, aviation, and AI/LLM studies.

Session Lifecycle (the core loop)

Command Phase What it does
/read-handover Resume Pick up where a previous session left off via HANDOVER.md
/strategic-next Plan Find what to build next with research, evaluation, prioritization
/creative-brainstorm Explore Think laterally, explore wild ideas, converge on the best one
/verify-thorough Verify 7-layer falsification stack. Try to BREAK it, not confirm it
/visual-verify Verify Visual and browser verification: screenshots, console, Playwright
/principles-check Audit Systematic audit against your engineering principles
/housekeeping Clean Cleanup, organize, consolidate. Leave it better
/low-context-handover Save Save session state for the next session to pick up

Building

Command What it does
/kickoff Start session: read everything, understand context first
/feature-build Structured feature implementation with incremental steps
/architect Design before you build. Constraints first, then options, then decide
/refactor Safe restructuring: characterization tests first, small steps

Debugging and Fixing

Command What it does
/debug-rootcause Find the REAL cause. 5 WHYs technique. Fix cause, not symptom

Code Review

Command What it does
/change-review PR/MR/diff analysis — correctness, security, data, tests, readability
/code-review Full senior engineer codebase audit — architecture to observability
/crm-review CRM-specific codebase audit (NestJS, Angular, TypeORM, PostgreSQL)

Deep Technical Analysis

Command What it does
/resilience-audit How the system handles failure — timeouts, retries, circuit breakers, cascading failures
/database-audit Schema design, index strategy, query patterns, transactions, migrations, data integrity
/api-audit Contract consistency, error responses, versioning, pagination, idempotency
/observability-audit Logging, metrics, tracing, health checks, alerting quality, SLOs
/tech-debt-analysis Hotspot mapping, debt quantification (principal/interest/risk), paydown roadmap

Security and Quality

Command What it does
/security-audit Full OWASP Top 10 mapped security review
/best-practices Deep research on best practices for your specific tech stack
/test-audit Find fake, hollow, and silently passing tests
/dependency-audit Supply chain health: vulnerabilities, abandoned packages, license risks
/accessibility-audit WCAG compliance and inclusive design audit

Performance

Command What it does
/performance-hunt Proactive performance bug hunting — O(n²), memory leaks, N+1, missing indexes
/bug-hunt Proactive logic bug hunting — data corruption, race conditions, silent failures
/deep-scan AI pattern recognition audit — cross-file inconsistencies, convention drift, implicit contracts

Testing

Command What it does
/flow-tester Systematically test every logical flow end-to-end
/game-tester Play and test games with Playwright MCP, find bugs and UX issues
/asset-quality-audit Audit game asset quality, consistency, AI art defects

Thinking and Planning

Command What it does
/think-first Developer plans first, AI independently, compare blind spots
/plan-certain Stop, understand fully, plan precisely, then act
/research-investigate Deep dive, brainstorm, plan with all context

Operations

Command What it does
/deploy-checklist Pre-deployment validation. Every time. No exceptions
/emergency-handover Fast context save when things are critical

Setup

Command What it does
/setup-claude-md Build CLAUDE.md with Hot/Warm/Cold memory hierarchy
/iterate-visual Iterative UI/UX refinement with visual feedback loops

Every template supports $ARGUMENTS for passing context directly:

/debug-rootcause TypeError in UserService.create()
/feature-build add dark mode toggle
/resilience-audit payment processing service
/database-audit users and orders tables

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.

npx @ccprompt/cli install .

Or install globally:

npm install -g @ccprompt/cli
ccprompt install .

CLI Commands

ccprompt install [path]      # Install templates as slash commands
ccprompt templates           # List all templates
ccprompt show <template>     # View a template in the terminal
ccprompt copy <template>     # Copy a template to clipboard
ccprompt new-template <name> # Create a custom template

Troubleshooting

"command not found: ccprompt"

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

npx @ccprompt/cli install .

Or reinstall globally:

npm install -g @ccprompt/cli

Slash commands don't appear in Claude Code

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

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

FAQ

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 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

License

MIT. See LICENSE.