This course is about being prepared before the first developer opens a terminal. Most setup failures happen not because the install is hard, but because nobody confirmed the blockers in advance. This is that pre-kickoff work.
You'll walk through the full range of environments Claude Code runs in:
- CLI install on macOS, Linux, and Windows, both the native path and WSL, including when each Windows option makes sense for a managed enterprise fleet
- IDE integrations in VS Code and JetBrains, and the three capabilities worth demonstrating to developers on Day 1
- Terminal and shell setup for enterprise environments, including proxy and certificate handling
- Dev containers and sandboxed execution, for teams that need isolation built into their workflow
- Headless and non-interactive mode for CI pipelines and automated scripts, including how to handle API key distribution in a GitHub Actions context
The practice exercise ties it together: install Claude Code in three environments (local CLI, IDE, and dev container), run a headless script end-to-end, and capture the output.
By the end you'll have your course artifact: the Installation Configuration Pack, a settings file and container spec that turns into the checklist you hand off to the client's IT team before kickoff.
Time In Skilljar (Measured) 1 hour and 12 Minutes
Practice & Artifact Building (Estimated Time In Skilljar) 60 Min
