Contextual Assist

Contextual Assist

Proactive skill and workflow suggestions based on what you're actually doing. Five levels from silent to full mentoring. Configure via bible-config.json or KZ_ASSIST_LEVEL env var.

Assistance Levels

Configure in ~/.claude/bible-config.json:

{
  "assistLevel": "standard"
}

Or override per-session: export KZ_ASSIST_LEVEL=guided

How It Works

Signal Detection

The contextual assist system monitors these signals to understand what you're doing:

Suggestion Categories

Suggestions are drawn from across the entire CC Commander kit:

1. CCC Domains — Route to the right CCC domain for the domain
2. Individual Skills — Specific skills for specific tasks
3. Slash Commands — Quick actions via /cc commands
4. Prompt Templates — Starting templates for common scenarios
5. Workflow Modes — Suggest mode switches when activity pattern shifts
6. Hooks — Mention relevant automated protections

Pattern Matching Rules

Project Type Detection

When the contextual assist system detects a project type, it loads the relevant suggestion set:

Next.js / React Project (detected: next.config.js, app/, .tsx files)

Detected: Next.js project

Relevant CCC domains:
  ccc-saas     — Auth, billing, database, API patterns
  ccc-design   — UI components, animations, landing pages
  ccc-testing  — E2E with Playwright, component testing

Quick starts:
  /cc mega saas        — Full SaaS stack (auth + billing + DB)
  /cc mega design      — UI polish, animations, component library
  /cc mode design      — Switch to design-first workflow
  /cc mode saas        — Switch to full-stack SaaS workflow

Relevant skills:
  nextjs-app-router    — App Router patterns and best practices
  shadcn-ui            — Component library integration
  tailwind-v4          — Tailwind CSS v4 patterns
  better-auth          — Authentication setup
  stripe-subscriptions — Billing integration

API / Backend Project (detected: routes/, controllers/, prisma/, drizzle/)

Detected: API / Backend project

Relevant CCC domains:
  ccc-saas     — Database, API design, auth
  ccc-devops   — CI/CD, Docker, monitoring
  ccc-testing  — API testing, load testing

Quick starts:
  /cc mega saas        — Full backend patterns
  /cc mega devops      — Infrastructure and deployment

Relevant skills:
  api-design           — RESTful API design patterns
  backend-patterns     — Service layer, repository pattern
  database-designer    — Schema design and migrations
  postgres-patterns    — PostgreSQL optimization
  drizzle-neon         — Drizzle ORM with Neon DB
  fastify-api          — Fastify API patterns
  harden               — Security hardening

DevOps / Infrastructure (detected: Dockerfile, .github/workflows/, terraform/, k8s/)

Detected: DevOps / Infrastructure project

Relevant CCC domains:
  ccc-devops   — Full DevOps suite (25+ skills)

Quick starts:
  /cc mega devops      — CI/CD, Docker, monitoring, security

Relevant skills:
  docker-development   — Docker best practices
  github-actions-reusable-workflows — CI/CD pipeline patterns
  container-security   — Container hardening
  senior-devops        — Infrastructure architecture
  infra-runbook        — Operational runbooks
  setup-deploy         — Deployment configuration

Marketing / Content (detected: blog/, content/, landing/, MDX/MD heavy)

Detected: Marketing / Content project

Relevant CCC domains:
  ccc-marketing  — Content strategy, copywriting, CRO
  ccc-seo        — Technical SEO, content optimization

Quick starts:
  /cc mega marketing   — Full marketing toolkit
  /cc mega seo         — SEO optimization suite
  /cc mode marketing   — Switch to marketing workflow

Relevant skills:
  landing-page-builder — High-converting landing pages
  seo-content-brief    — SEO-optimized content briefs
  content-strategy     — Content planning and calendars
  email-capture        — Lead generation forms
  ab-test-setup        — A/B testing configuration

Activity Pattern Detection

Beyond project type, the system detects real-time activity patterns:

Stuck Pattern (3+ errors in a row, or >60s with no action)

You seem stuck. Here are some options:

  /tdd            — Write a test first to clarify the expected behavior
  /build-fix      — Auto-resolve build errors
  /investigate    — Systematic debugging approach
  /clarify        — Ask structured clarifying questions

Or try: "What's the simplest thing that could possibly work?"

Testing Pattern (editing test files, running test commands)

Working on tests? CC Commander has you covered:

  /tdd                 — Full TDD red-green-refactor cycle
  /verify              — Run verification loop (tests + types + lint)
  /e2e                 — E2E testing with Playwright
  /test-coverage       — Check and improve test coverage
  ccc-testing         — 15+ testing skills

Tip: Write the test assertion first, then make it pass.

Refactoring Pattern (many edits to same files, renaming, moving)

Refactoring detected. Useful tools:

  /refactor-clean      — Dead code cleanup + restructuring
  /code-review         — Multi-agent code review
  /checkpoint          — Save a restore point before big changes
  /quality-gate        — Verify quality metrics

Tip: Run /verify after each refactoring step to catch regressions early.

New Feature Pattern (creating new files, new directories)

Building something new? Start with structure:

  /plan                — Spec-first planning
  /tdd                 — Test-driven development
  /init                — Project setup wizard (if new project)
  confidence-check     — Assess confidence before diving in

Tip: "What does done look like?" — define success criteria first.

Deployment Pattern (git commands, CI files, deploy scripts)

Deploying? Safety checks:

  /verify              — Full verification before push
  /checkpoint          — Git checkpoint (safe restore point)
  /harden              — Security hardening check
  /deploy              — Deployment checklist

  ccc-devops          — Full CI/CD, monitoring, rollback patterns

Icons / Logos Pattern (mentions of "icon", "icons", "logo", "logos", "tech stack", "badge", "badges", "svg icon", "tech icon")

Looking for tech icons or logos? Use developer-icons:

  developer-icons     — 500+ optimized SVGs, React-ready, tree-shakeable
  npm install developer-icons
  Browse: https://xandemon.github.io/developer-icons/icons/All

Tip: Never build custom SVG icons when developer-icons covers it.
Load the skill: /developer-icons

Documentation Pattern (editing .md files, README, docs/)

Writing docs? Available tools:

  /update-docs         — Sync docs with code changes
  /docs                — Documentation generator
  typeset              — Typography and formatting polish
  doc-coauthoring      — Collaborative documentation

Tip: Keep docs close to the code they describe.

Progressive Disclosure (Mentored Level)

At the mentored level, the system introduces kit features gradually over the course of a session:

Phase 1: First 10 Interactions

Introduce only:

• /plan — planning
• /verify — verification
• /checkpoint — saving progress
• Basic file operations

Message style:

[Mentored] You just edited 3 files. A good practice is to verify your changes
work correctly before moving on. Try typing: /verify

This runs your tests, type checker, and linter in one step.

Phase 2: Interactions 11-30

Introduce:

• /tdd — test-driven development
• /code-review — code review
• Mode switching (/cc mode)
• Relevant CCC domains for detected project type

Message style:

[Mentored] Did you know? CC Commander includes CCC domains — large skill bundles
for common workflows. For your Next.js project, try:

  /cc mega saas — sets up auth, billing, database, and API patterns

You can also switch modes: /cc mode saas activates the full SaaS workflow.

Phase 3: Interactions 31+

Introduce:

• Agency Orchestrator (multi-agent)
• Task Commander (complex orchestration)
• Overnight runner (autonomous sessions)
• Advanced features (dialectic review, strategic compact)

Message style:

[Mentored] You're working on a complex task with many files. For tasks this
large, the Task Commander can orchestrate multiple agents in parallel:

  Use the task-commander skill to set up a DAG workflow.
  It manages agent assignment, retries, and cost tracking automatically.

This is an advanced feature — only use when you have 3+ independent subtasks.

Integration with Hooks

The contextual assist system works alongside these hooks:

Configuration Reference

Full bible-config.json options relevant to contextual assist:

{
  "assistLevel": "standard",
  "features": {
    "coach": true,
    "sessionCoach": true
  },
  "thresholds": {
    "stuckTimeoutSec": 60
  }
}

Environment override: KZ_ASSIST_LEVEL=mentored (takes precedence over config file).

Quick Reference Table