Claude Code for development
Bring Claude Code into your repository workflow: organise context, understand and modify code, prepare tests and reuse procedures with skills and subagents.
Find your starting point
A good fit when you already read and modify code and want to work with Claude Code, organise context and reuse procedures while retaining technical review.
Another option to consider
Claude for everyday workIf you need to analyse documents and prepare content without working with code, choose the everyday-use programme.- Hours and sessions
- 12 hours live · 6 sessions of 2 h.
- Group size
- Up to 12 participants per trainer as a reference, adjusted to the practice and feedback.
What you will learn
- 01
Prepare Claude Code and organise persistent instructions and context with CLAUDE.md.
- 02
Understand, fix and refactor code, linking tests and diffs to expected behaviour.
- 03
Reuse a procedure through a skill, delegate a task to a subagent and hand over a reviewed new challenge.
A proposed programme
Learn to work with Claude Code from environment preparation to handover review. Use a repository as shared context to explore code, fix a CSV importer, refactor and prepare tests. Also create instructions in CLAUDE.md, a simple skill and a bounded task for a subagent. Finish by applying the method to a new challenge.
We adapt the selection and depth of the modules to the group's starting point and goals.
01Environment and instructions
Environments, configuration, planning, CLAUDE.md, rules, memory and task context.
You will work on
- Explore terminal, IDE and app, configure the main environment and distinguish planning from execution.
- Organise CLAUDE.md, rules and memory; separate persistent instructions from immediate task context.
- Explore code structure, commands and paths with a defined task and criteria.
- Practice
- Prepare Claude Code and repository instructions; request a data-path explanation and check it against the files.
- How you will check it
- A ready environment, reusable instructions and a short code map checked against the repository.
02Understand and change code
Exploration, debugging, fixes, refactoring and tests with Git/GitHub review.
You will work on
- Reproduce and fix the CSV importer accepting “12x” as a quantity.
- Separate the fix from refactoring; check non-negative integers, zero and invalid inputs.
- Prepare a useful regression and review the diff, commits and change proposal with Git/GitHub.
- Practice
- Fix CSV validation and extract a reusable function; show that regression distinguishes the initial code from the fix.
- How you will check it
- A focused change with behaviour tests and an explainable technical review.
03Reuse and delegate
Simple skills, subagents for bounded tasks and a new challenge to hand over.
You will work on
- Create a simple skill describing a reusable review procedure.
- Delegate a research or review task to a subagent with its goal, context and output format; check the findings.
- Solve a new task with its own instructions and checks; isolate changes when work is concurrent.
- Practice
- Prepare a review skill, ask a subagent to identify test cases and individually improve row-level errors.
- How you will check it
- Reusable guidance, checked findings and an individual handover with diff, tests and decisions.
From project context to a reviewed improvement
Teaching example
Work across several challenges in a prepared repository: understand a code path, fix and refactor code, create a skill and delegate a review. Finish with a new task and a checked technical handover.
Fictional classroom case. A team maintains a JavaScript or TypeScript inventory importer. The repository contains CSVs with invented data, conventions and tests; quantities must be non-negative integers.
- Starting point
- The team needs to understand the import path, fix a partially accepted quantity and repeat its review on future improvements.
- First attempt
- The group prepares CLAUDE.md, requests a code map and fixes “12x” being converted to 12. It then refactors validation and writes a skill with review steps.
- What we review
- The trainer asks for evidence that regression detects the bug and zero remains valid. A subagent looks for boundary cases; the group checks its findings and reviews the fix separately from refactoring.
- Result
- The outcome brings together a checked change, project instructions and a reusable procedure. Each person then applies that context to improved row-level errors and hands over code, tests and an explanation.
Understand, improve and reuse
Context
CLAUDE.md
Project instructions and commands
Code map
Path and a bounded task
Change
Fix and tests
Valid quantities and regression
Refactoring
Clear validation, reviewed diff
Continuity
Skill and subagent
Procedure and bounded review
New challenge
Row errors and your own handover
Teaching illustration of several exercises in the prepared repository; their results are checked during the training.
Before calling it complete
- CLAUDE.md provides stable context and the specific task defines its expected behaviour.
- The fix and refactoring preserve valid cases and have tests that detect the original bug.
- The skill and delegated task have a clear goal; the individual challenge includes checked findings and tests.
Sessions to put it into practice.
Reference edition: 12 live hours across 6 sessions of 2 hours. Includes environment and context, fixes and refactoring, Git/GitHub, skills, subagents and a final challenge. Practice and review take place during the sessions.
- Session 12 h
Prepare Claude Code and its environment
Explore terminal, IDE and app; practise in one main environment with configuration, controls and planning and execution modes.
By the endA ready environment and an initial guided repository walkthrough.
- Session 22 h
Organise instructions and context
Prepare CLAUDE.md, rules and memory; separate project and task context and check how instructions are used.
By the endReusable instructions and bounded context for a task.
- Session 32 h
Understand, diagnose and fix
Explain the CSV path, reproduce the bug and apply a small fix with a regression that detects it.
By the endA fixed bug with evidence of behaviour before and after the change.
- Session 42 h
Refactor and review changes
Improve validation while retaining valid inputs; review tests, diff and the change proposal with Git/GitHub.
By the endA code improvement and a review with reproducible checks.
- Session 52 h
Reuse skills and delegate tasks
Create a simple review skill and delegate bounded research or review to a subagent; check the result and recognise when to isolate changes.
By the endA reusable procedure and a delegated task with reviewed findings.
- Session 62 h
Solve a new challenge and hand over
Individually improve row-level errors; choose context and tools, check the result and explain decisions with feedback.
By the endAn individual handover with code, tests and an explanation for technical review.
Advanced blocks to take things further.
We can include these blocks in your training when your team needs more depth.
MCP and hooks for your team
Connect tools and automate checks as part of a Claude Code workflow.
More complex changes
Go deeper into migrations, integrations or delivery workflows with focused tests and review.
We agree the selection, depth and time when preparing your proposal.
With guidance, practice and support.
Each delivery includes working materials, feedback on practical work and assessment against the agreed objectives.
Materials you can keep
Downloadable, versioned guides, exercises and review criteria for internal use.
To prepare and complete the delivery
A short recommendation, an editable communications kit and a group learning report.
The Optimal Flow certificate
A certificate of achievement after the agreed assessment.
A month of email support
On the content covered, up to two accumulated hours for the whole group.
