This course takes you from an empty machine to a reviewed, production-style workflow with
Claude Code and Claude Cowork. Ten modules, 49 videos, a little over five hours - every one of
them recorded against a real installation rather than narrated over slides.
You begin by installing Claude Desktop and the Claude Code CLI from their official sources,
authenticating without leaking tokens, and building a disposable lab that limits blast radius
before any agent touches anything. From there you work through the agentic loop, repository
exploration before editing, scoped prompting with acceptance criteria, supervised edits, and a
git workflow in which every diff is reviewed before it lands.
The middle of the course is about making the agent predictable: CLAUDE.md and
the .claude directory, allow / ask / deny permissions and least privilege, Skills
and scoped rules, invocable commands, subagents, agent teams and git worktrees for parallel
work, lifecycle hooks, a local MCP server, and packaging all of it as a plugin a team can
review. You then point the whole toolkit at ordinary engineering work: a feature from an issue,
evidence-driven debugging, a refactor that preserves behaviour, review and security review, and
headless runs that return structured output to CI.
The last three modules move to Claude Cowork: working folders, connectors and access
boundaries, project instructions and memory, browser use and computer use, research synthesis
with traceable sources, spreadsheet and data-extraction workflows, cross-app tasks, scheduled
and long-running work, and a team rollout that balances productivity against least privilege
and cost. The course closes on an integrated capstone that combines a Claude Code repository
workflow with a Cowork knowledge-work deliverable and reviews both against explicit
criteria.
Safety is not a bonus module here. Permissions, least privilege, prompt-injection defence,
source traceability and human approval are demonstrated in the lessons where they actually
matter. Every video also contains a deliberate, controlled failure - a wrong routing, an unsafe
tool design, a missed verification - followed by the diagnosis and the correction, because that
is usually where the real lesson is.
Each lesson ships with the slide deck used on screen and the exact commands, fixtures and
sources that were executed, attached as a single download.
Morbi nec nisi ante. Quisque lacus ligula, iaculis in elit et, interdum semper quam. Fusce in interdum tortor. Ut sollicitudin lectus dolor eget imperdiet libero pulvinar sit amet
Morbi nec nisi ante. Quisque lacus ligula, iaculis in elit et, interdum semper quam. Fusce in interdum tortor. Ut sollicitudin lectus dolor eget imperdiet libero pulvinar sit amet
Morbi nec nisi ante. Quisque lacus ligula, iaculis in elit et, interdum semper quam. Fusce in interdum tortor. Ut sollicitudin lectus dolor eget imperdiet libero pulvinar sit amet
Morbi nec nisi ante. Quisque lacus ligula, iaculis in elit et, interdum semper quam. Fusce in interdum tortor. Ut sollicitudin lectus dolor eget imperdiet libero pulvinar sit amet
Morbi nec nisi ante. Quisque lacus ligula, iaculis in elit et, interdum semper quam. Fusce in interdum tortor. Ut sollicitudin lectus dolor eget imperdiet libero pulvinar sit amet
Morbi nec nisi ante. Quisque lacus ligula, iaculis in elit et, interdum semper quam. Fusce in interdum tortor. Ut sollicitudin lectus dolor eget imperdiet libero pulvinar sit amet