Spec Driven Cc Guide

Expert knowledge base for Claude Code Terminal — the CLI tool itself, not coding tasks. Implements 4 knowledge-retrieval phases with structural anti-skip enforcement using the Execute-Verify-Gate pattern at every step. Designed to prevent token optimization bias that causes reference file skipping by making every reference load mandatory and verifiable. MUST use this skill whenever the user asks about Claude Code features, configuration, setup, or troubleshooting. This includes: keyboard shortcuts not working (Option key, Alt+P, Shift+Enter, Ctrl+B), creating or configuring subagents/skills/commands/plugins, setting up hooks (PreToolUse, PostToolUse, HTTP hooks), installing or debugging MCP servers, GitHub Actions or GitLab CI/CD integration for PR reviews, switching models mid-conversation, undoing or rewinding Claude's changes, proxy/network configuration, permission modes, memory and CLAUDE.md setup, the /batch /simplify /debug bundled skills, git worktrees, agent teams, remote control, headless mode, or ANY question where the user is asking about how Claude Code works rather than asking Claude Code to do coding work. When in doubt about whether a question is about Claude Code itself vs. a coding task, prefer triggering this skill — it will not interfere with coding-focused responses.

mkdir -p ~/.claude/skills/spec-driven-cc-guide
curl -L https://claudskills.com/skills/spec-driven-cc-guide/SKILL.md \
  -o ~/.claude/skills/spec-driven-cc-guide/SKILL.md

@misc{spec-driven-cc-guide-2026,
  author    = {bankielewicz},
  title     = {Spec Driven Cc Guide [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/spec-driven-cc-guide/}
}