← CCAR-F study guide

Domain 3: Claude Code Configuration & Workflows (20%)

6 lessons, each ending with a practice scenario (Pro)

Log in to save your progress.

  1. ✓3.1 — CLAUDE.md Hierarchy, Scoping, and Modular OrganisationA CLAUDE.md file is a Markdown file of instructions for Claude Code. Claude Code reads these files at three levels.Scenario: Pro
  2. ✓3.2 — Custom Slash Commands and SkillsA skill is a named, reusable set of instructions that Claude Code loads on demand. You run it as a slash command (/deploy).Scenario: Pro
  3. ✓3.3 — Path-Specific Rules for Conditional Convention LoadingPath-specific rules load conventions only when you edit files matching their glob patterns. They solve what neither root CLAUDE.md nor directory-level CLAUDE.md handles well: one file type scattered across many directories.Scenario: Pro
  4. ✓3.4 — Plan Mode vs Direct ExecutionClaude Code has two main modes:; Plan mode: reads the codebase, analyses dependencies, proposes an approach — does not modify files until you approve.; Direct execution: makes changes straight away.Scenario: Pro
  5. ✓3.5 — Iterative Refinement TechniquesIterative refinement steers Claude Code towards the right result over several rounds. Five techniques.Scenario: Pro
  6. ✓3.6 — CI/CD IntegrationIn CI/CD, Claude Code runs headless (no keyboard). Key patterns.Scenario: Pro
Domain recapQuick overview of all lessons

6 Task Statements / Lessons

3.1 CLAUDE.md Hierarchy, Scoping, and Modular Organisation

Project-level .claude/CLAUDE.md (or root CLAUDE.md) overrides user-level (~/.claude/) which overrides global.
Modular organisation keeps conventions maintainable.

3.2 Custom Slash Commands and Skills

Unified Skills system:

  • .claude/commands/foo.md → /foo
  • .claude/skills/foo/SKILL.md (supports frontmatter: context: fork, allowed-tools, argument-hint)

Skills can be project-scoped (shared via git) or user-scoped (personal).

3.3 Path-Specific Rules for Conditional Convention Loading

Load different conventions based on file path or directory (e.g., stricter rules for /src/payments).

3.4 Plan Mode vs Direct Execution

When Claude Code should produce a plan first versus executing immediately.
Trade-offs of each mode for safety and speed.

3.5 Iterative Refinement Techniques

How to drive Claude Code through successive improvement cycles while preserving context and intent.

3.6 CI/CD Integration

Running Claude Code in pipelines (GitHub Actions claude-code-action, CLI flags such as --append-system-prompt, --allowedTools, --max-turns).

High-yield exam items: Correct location of team vs personal skills, meaning of context: fork, and CLAUDE.md precedence order.

Next domain

Domain 4: Prompt engineering & structured output →