Bible Guide

Bible Guide — Interactive Onboarding

Welcome to the CC Commander by Kevin Z. This guide helps you discover the right skills, commands, and workflows for your experience level and goals.

Welcome

CC Commander is a comprehensive toolkit: 456+ skills, 11 CCC domains, 83 commands, 24 hooks, 10 workflow modes, and 37 prompt templates. That is a lot. This guide helps you find exactly what you need without reading everything.

How this guide works:

1. Tell me what you are building (Skill Discovery Wizard below)
2. I suggest the right CCC domains, modes, and commands
3. You start building immediately

Skill Discovery Wizard

Answer one question: What are you building?

Not sure? Run /init and the decision tree will ask the right questions and configure everything for you.

Progressive Disclosure

Beginner: The 4 Essential Commands

If you learn nothing else, learn these four commands. They cover 80% of daily usage.

Beginner workflow:

/init                    # Set up your project
/plan                    # Plan your feature
# ... build it ...
/verify                  # Confirm everything works

That is it. Four commands. You are now using CC Commander effectively.

Intermediate: Modes, CCC Domains, Prompts, Hooks

Once you are comfortable with the basics, unlock these capabilities:

Workflow Modes

Switch your entire workflow persona with one command:

/cc mode design          # Visual-first: design/animation skills, critique loop
/cc mode saas            # Full SaaS lifecycle: auth, billing, DB, deploy
/cc mode marketing       # Content + CRO: SEO, copy, conversion
/cc mode research        # Deep research: citations, confidence, sources
/cc mode night           # Autonomous overnight: checkpoints, recovery
/cc mode yolo            # Max speed: skip confirmations, auto-approve

CCC Domains

Load ONE CCC domain to get an entire domain. Each CCC domain bundles 8-46 specialist skills behind a single router:

# Load a CCC domain by name
"use ccc-design skill"
"use ccc-saas skill"
"use ccc-devops skill"

The router inside each CCC domain dispatches your request to the right specialist automatically.

Prompt Templates

36+ battle-tested prompts across 6 categories. Access them with:

/cc prompts              # Browse the prompt library
/cc prompts coding       # Filter by category

Kit-Native Hooks (Automatic)

13 hooks run automatically during your sessions:

• context-guard — warns when context window is getting full
• auto-checkpoint — creates git checkpoints at safe points
• cost-alert — alerts when session cost exceeds thresholds
• confidence-gate — checks confidence before major operations
• session-coach — periodic coaching nudges for better workflow

No setup needed. Hooks activate automatically after install.

Advanced: Task-Commander, Multi-Agent, Night Mode, Custom Plugins

Task-Commander

For large features spanning multiple files and multiple steps:

/task-commander

This breaks your feature into subtasks, dispatches parallel subagents, tracks progress, and assembles the result. Use it for anything that takes more than one session.

Multi-Agent Workflows

/orchestrate             # Multi-agent pipeline
/devfleet                # Dispatch fleet of dev agents
/code-review             # Multi-perspective code review

The /orchestrate command creates a pipeline where specialized agents handle different parts of the work in parallel.

Night Mode

For autonomous overnight work (migrations, large refactors, batch processing):

/cc mode night

Night mode enables:

• Automatic git checkpoints every N minutes
• Error recovery with rollback
• Progress logging to a file
• Cost monitoring with kill threshold

Custom Plugins

Create your own skills:

/skill-create            # Interactive skill creator wizard

Skills are just markdown files in ~/.claude/skills/your-skill/SKILL.md with YAML frontmatter. CC Commander includes templates for creating new skills.

What Can You Help With?

Quick Commands Reference (Top 10)

Walkthrough Scenarios

Scenario 1: Build a Landing Page

Goal: Create a high-converting landing page with animations.

Step 1: /init
   → Select "landing page" when asked about build type
   → Bible auto-configures design mode

Step 2: /cc mode design
   → Activates design-first workflow

Step 3: "use ccc-design skill"
   → Loads 35+ design skills behind the router

Step 4: "Build a landing page for a SaaS product called Acme.
         Hero section with gradient animation, features grid,
         pricing table, and CTA with hover effects."
   → ccc-design routes to landing-page-builder + animate + colorize

Step 5: /verify
   → Checks: responsive, accessible, fast, no console errors

Step 6: "use critique skill on the landing page"
   → Gets design feedback, then apply polish

Time: 30-60 minutes for a polished, animated landing page.

Scenario 2: Debug a Production Bug

Goal: Find and fix a bug reported by a user.

Step 1: "use systematic-debugging skill"
   → Structured debugging: reproduce, isolate, hypothesize, verify

Step 2: Describe the bug with reproduction steps
   → Agent narrows down the root cause

Step 3: /tdd
   → Write a failing test that reproduces the bug FIRST

Step 4: Fix the implementation
   → Test should now pass

Step 5: /verify
   → Full verification: tests pass, no regressions, no console errors

Step 6: /checkpoint
   → Git commit with conventional commit message (fix: ...)

Time: 15-45 minutes depending on bug complexity.

Scenario 3: Set Up CI/CD Pipeline

Goal: Configure GitHub Actions with Docker, tests, and deployment.

Step 1: "use ccc-devops skill"
   → Loads 20 DevOps skills behind the router

Step 2: "Set up a CI/CD pipeline with GitHub Actions.
         Run tests on PR, build Docker image on merge to main,
         deploy to AWS ECS."
   → Routes to github-actions-reusable-workflows + docker-development + setup-deploy

Step 3: "Add container security scanning"
   → Routes to container-security

Step 4: "Add monitoring and alerting"
   → Routes to prometheus-configuration + grafana-dashboards

Step 5: /verify
   → Validates: workflow syntax, Dockerfile best practices, security scan config

Step 6: /checkpoint
   → Git commit (ci: add GitHub Actions pipeline with Docker + AWS ECS deploy)

Time: 1-2 hours for a production-grade pipeline.

Show Me More

Tips for Getting the Most Out of CC Commander

1. Start with /init — it detects your stack and configures everything automatically
2. Use modes — they change Claude's entire behavior to match your workflow
3. Load CCC domains, not individual skills — the router picks the right specialist
4. Use /plan before building — plans prevent wasted tokens and wrong-direction work
5. Always /verify before done — catches errors before they reach production
6. Use /compact when context gets long — keeps quality high by freeing context space
7. Run /cc when stuck — the command center shows every available action
8. Try prompt templates — /cc prompts gives you battle-tested starting points
9. Use subagents for parallel work — /orchestrate dispatches independent tasks simultaneously
10. Read BIBLE.md once, use CHEATSHEET.md daily — learning guide vs quick reference