Capstone: Set Up Your Workspace
Time: 30--45 minutes | Skills: Installation, Authentication, Basic Conversation, File Creation, Git Basics
The Scenario
You have just installed Claude Code and you are ready to start using it for real. Your first task is to set up a proper workspace -- a dedicated project folder where you will do all of your practice throughout this entire tutorial series.
By the end of this capstone you will have a project folder under version control, a couple of useful files created by Claude, and your first Git commit. You will also prove to yourself that you can start Claude Code, have a conversation with it, and find the results on your computer afterward.
Every real-world project starts with a workspace. Getting comfortable with folder creation, Git, and Claude Code in one smooth flow is exactly what you will do on day one of any job or side project. Nail this now and the rest of the tutorials will feel natural.
Prerequisites
Before you begin, make sure you have completed everything in Module 01:
- Windows Terminal or PowerShell is installed and you can open it.
- Git is installed (
git --versionprints a version number). - Node.js 18 or later is installed (
node --versionprints a version number). - Claude Code is installed globally (
claude --versionprints a version number). - You have authenticated at least once (or you are ready to authenticate when prompted).
If any of those checks fail, go back to the earlier lessons in this module before continuing.
Step-by-Step Instructions
Step 1 -- Create a project folder
Open PowerShell (or Windows Terminal) and run the following command to create a new folder inside your Documents directory:
mkdir $env:USERPROFILE\Documents\claude-tutorials
You should see output confirming that the directory was created. Now move into that folder:
cd $env:USERPROFILE\Documents\claude-tutorials
$env:USERPROFILE is a PowerShell shortcut that points to your user folder -- usually something like C:\Users\YourName. So the full path becomes C:\Users\YourName\Documents\claude-tutorials. You can always find this folder later by opening File Explorer and navigating to Documents > claude-tutorials.
Step 2 -- Initialize a Git repository
While you are still inside the claude-tutorials folder, run:
git init
Git will respond with something like:
Initialized empty Git repository in C:/Users/YourName/Documents/claude-tutorials/.git/
Now verify that everything looks right:
git status
You should see a message that says "On branch main" (or "On branch master" on some systems). Either is fine. The important thing is that Git is tracking this folder.
Make sure you are inside the claude-tutorials folder. Run pwd (PowerShell) to check your current location. If you are somewhere else, run cd $env:USERPROFILE\Documents\claude-tutorials and try git init again.
Step 3 -- Start Claude Code
With your terminal still pointing at the claude-tutorials folder, start Claude Code:
claude
Claude Code will launch right inside your terminal. If this is your first time, you may be prompted to authenticate -- follow the on-screen instructions to log in. Once you see the Claude Code prompt (a cursor waiting for your input), you are ready to go.
Claude Code runs inside your terminal -- there is no separate window to open. Everything happens right where you typed claude.
Step 4 -- Create a CLAUDE.md file using Claude
Type (or paste) the following message into Claude Code:
Create a CLAUDE.md file for this project. This is my practice workspace
for learning Claude Code. I'm a beginner on Windows. Add instructions
that remind you to explain things simply and use PowerShell commands.
Claude will draft a CLAUDE.md file and show you what it plans to write. Read through it -- this is your chance to see what Claude came up with before anything is saved to disk.
When you are happy with it, approve the file creation by accepting the action that Claude proposes (press y or follow the on-screen prompt).
CLAUDE.md is a special file that Claude Code reads every time it starts in a project. It acts like a set of standing instructions -- "always explain things simply," "use PowerShell, not bash," and so on. Think of it as a sticky note for Claude.
Step 5 -- Create a README using Claude
Next, ask Claude to create a second file:
Create a README.md file that describes this as my Claude Code learning
workspace. Include today's date and a section for notes.
Again, review what Claude proposes and then approve the creation.
Step 6 -- Explore what was created
Now that you have two files, practice asking Claude to tell you about them. Try these messages one at a time:
What files are in this folder now?
Claude should list at least CLAUDE.md and README.md (and possibly the hidden .git folder).
Then ask:
Read the CLAUDE.md file and tell me what's in it.
Claude will open the file, read its contents, and summarize them for you. This is a great way to double-check any file without leaving your terminal.
Step 7 -- Make your first Git commit using Claude
Time to save your work with Git. Ask Claude:
Create a git commit with all these files. Use the message
'Initial workspace setup'
Claude will stage the files and commit them. You will likely see it run commands like git add and git commit behind the scenes. Approve the git commands when prompted.
Whenever Claude wants to run a command that changes something (like a Git commit), it will ask for your permission first. Always read the proposed command before approving. This is a good habit that will serve you well in every future project.
Step 8 -- Check your work
Verify that the commit was recorded:
Show me the git log
You should see output that includes your commit message "Initial workspace setup", a commit hash (a long string of letters and numbers), and a timestamp. That means your work is saved in version control -- congratulations!
Step 9 -- Exit and verify
Type the following to leave Claude Code:
/exit
You are now back in regular PowerShell. Run:
dir
You should see CLAUDE.md and README.md listed in the output.
Finally, open the folder in File Explorer to see everything with your own eyes:
explorer .
This opens a File Explorer window pointed at your claude-tutorials folder. You should see the same files there. Everything Claude created is a normal file on your computer -- nothing hidden or magical.
Stretch Goals
Finished early or want extra practice? Try these:
-
Create a notes folder. Ask Claude:
Create a notes/ folder with a day-01.md file inside it.
In the file, write a few bullet points about what I learned today. -
Add a .gitignore file. Ask Claude:
Add a .gitignore file to this project. Can you also explain what
a .gitignore file is and why it's useful?Read Claude's explanation carefully --
.gitignorewill come up again in future modules. -
Make another commit. Ask Claude:
Commit these new files with the message 'Add notes and gitignore'
These are here for extra practice. If you are feeling comfortable, move on to Module 02. You can always come back later.
Self-Assessment
Use this checklist to make sure you covered all the essentials. Check off each item you completed:
- Created the
claude-tutorialsproject folder using PowerShell - Initialized a Git repository with
git init - Started Claude Code and authenticated successfully
- Created a
CLAUDE.mdfile by asking Claude - Created a
README.mdfile by asking Claude - Asked Claude to read files back to you
- Made at least one Git commit through Claude
- Found your files in File Explorer
- Exited Claude Code with
/exitand returned to PowerShell
If you checked all nine boxes, you are in great shape. If you missed one or two, go back and try those steps again -- repetition is the fastest way to build confidence. There is no penalty for redoing steps.
Congratulations!
You now have a fully working Claude Code workspace. This folder will be your practice area for the rest of the tutorials, so keep it handy.
Here is what you proved you can do:
- Navigate your terminal -- you created folders and moved between them in PowerShell.
- Use Git basics -- you initialized a repository and made a commit.
- Have a conversation with Claude Code -- you asked Claude to create files, read files, and run commands.
- Review and approve actions -- you practiced the habit of reading what Claude proposes before letting it proceed.
These are the foundational skills that every module builds on. In Module 02, you will dive deeper into Claude's core features -- reading code, editing files, searching across projects, and running commands with confidence.
How was this lesson? Take 2 minutes to share your feedback — it helps us make the tutorials better for everyone.