Claude Code Setup Guide
Free
Make one small, verified change in a local practice repository.
BEGINNER / TERMINAL WORKFLOW
1. Set the stage
Use a terminal, a practice project, and a supported subscription or developer account. Git for Windows is recommended for native Windows use.
1. Install in PowerShell
Use the official native installer: irm https://claude.ai/install.ps1 | iex. When it finishes, open a new terminal and run claude --version.
2. Start in the right folder
Open your practice project folder in the terminal, then run claude. Complete the browser sign-in and check the displayed working directory.
3. Set project boundaries
Ask for a read-only overview first. Add a short CLAUDE.md with project commands and conventions. Keep normal action approvals enabled.
4. Change, test & review
Work on a Git branch. Ask for one small edit, run the relevant check, and inspect the diff before committing or publishing.
2. Lean working stack
| Stage | Role | | --- | --- | | Claude Code | Inspect & edit | | Git | Track the change | | Tests | Verify behavior | | Preview | Review the result |
Arrows in the visual sheet show the order of work. External connections require separate setup. Optional tools may be replaced with ones you already use. This is a suggested stack for this task, not a universal optimum.
Instructions are not permissions
CLAUDE.md explains how to work. Tool permissions control what can run. Use both; do not rely on a prompt alone to protect important systems.
Add skills for repeated work
Begin without extra plugins. Add a trusted skill or connector only when the task needs it, and review its access before use.
3. First practice task
Confirm this practice repository's folder, branch, and uncommitted changes. Explain the app without editing it. Then propose one small text change and the check that would prove it works.
Your setup is working when
The correct project is identified, the change is isolated, the relevant check passes, and the actual diff matches the requested scope.
Troubleshooting
Command missing? Reopen the terminal and check PATH. No session? Start in the original directory. Blocked action? Use the approved permission path.
Series 18 / 40