Claude Code Configuration & Workflows
6 build exercises to practise the concepts in this domain.
3.1 — Build a Multi-Level CLAUDE.md Configuration
Beginner
30 minutes
- Understand the three-level CLAUDE.md hierarchy (user, project, directory) and when to use each
- Configure modular project standards using @import syntax
- Use .claude/rules/ for topic-specific rule files
- Diagnose configuration scoping issues with the /memory command
- Identify root cause when a new team member does not receive instructions
3.2 — Create Custom Commands and Skills
Intermediate
30 minutes
- Distinguish between project-scoped and user-scoped command locations
- Configure SKILL.md frontmatter with context: fork, allowed-tools, and argument-hint
- Understand when to use skills vs CLAUDE.md for conventions vs workflows
- Verify scoping boundaries between shared and personal configuration
- Apply the context: fork pattern to isolate verbose output from the main conversation
3.3 — Configure Path-Specific Rules with Glob Patterns
Intermediate
30 minutes
- Write YAML frontmatter with glob patterns for conditional rule loading
- Apply path-specific rules to files spread across many directories
- Understand why path-specific rules are more token-efficient than root CLAUDE.md
- Distinguish when to use path-specific rules vs directory-level CLAUDE.md
- Verify conditional loading behaviour using the /memory command
3.4 — Practice Plan Mode vs Direct Execution Decision-Making
Intermediate
45 minutes
- Apply the decision framework for choosing plan mode vs direct execution based on task ambiguity
- Execute the hybrid plan-then-execute pattern for multi-file migrations
- Use the Explore subagent to isolate verbose discovery output from the main conversation
- Recognise complexity upfront rather than waiting for it to emerge
- Distinguish task difficulty from task ambiguity when selecting execution mode
3.5 — Practice Iterative Refinement Techniques
Beginner
30 minutes
- Apply the technique hierarchy: concrete examples over prose for inconsistent interpretation
- Use test-driven iteration to provide unambiguous feedback via test failures
- Deploy the interview pattern for unfamiliar domains to surface hidden requirements
- Distinguish when to batch feedback vs iterate sequentially based on issue interdependence
- Recognise that 2-3 well-chosen examples are sufficient for pattern generalisation
3.6 — Set Up a CI/CD Pipeline with Claude Code
Advanced
45 minutes
- Use the -p flag for non-interactive Claude Code execution in CI pipelines
- Configure structured JSON output with --output-format json and --json-schema
- Implement session context isolation between code generation and review
- Set up incremental review to eliminate duplicate findings across runs
- Provide project context via CLAUDE.md for CI-invoked Claude Code