Get Started with Claude Code

Use Claude Code to organize files and build reusable AI prompt patterns.

Introduction

30 Second Summary

Everyone has that one folder on their computer crammed with random files, half-finished projects, and things saved "just for now" six months ago. What if you could tell your terminal to clean it all up for you?

In this project, you will install Claude Code and use it to transform a messy folder into an organized workspace using nothing but natural language commands in your terminal.

What You'll Build

You will use Claude Code, an AI-powered terminal assistant, to reorganize files on your machine, build a personalized memory file that makes every session smarter, and create a reusable prompt library.

By the end of this project, you'll have:

  • A personalized CLAUDE.md file that gives Claude Code persistent memory about your coding style, preferences, and project conventions.
  • A reorganized my-workspace folder with files sorted into logical subdirectories as proof that Claude Code works as your terminal assistant.
  • A prompt-library.md reference file with reusable prompt patterns you can apply to any future Claude Code session.
  • Secret Mission: Build a multi-step "digital audit" command that analyzes storage, finds duplicates, identifies forgotten files, and produces a readable report.

Are there any prerequisites?

You need an active Claude Pro subscription ($20/month, which includes Claude Code access) and Visual Studio Code installed on a Windows 10 or later machine.

Install Claude Code

Claude Code is a terminal-based AI assistant that can read, write, and restructure files directly on your machine. Unlike a chatbot in a browser window, it operates inside your actual file system.

In this step, you will install Claude Code, set up Git for Windows (so Claude Code has access to richer shell tools), and authenticate with your Claude Pro subscription.

In this step, get ready to:
  • Install the Claude Code CLI on your machine.
  • Install Git for Windows so Claude Code can use Bash.
  • Authenticate Claude Code with your Claude Pro subscription.
Install Claude Code via PowerShell

Claude Code installs through a single PowerShell command. The installer downloads the CLI binary and adds it to your system path so you can run it from any terminal.

  • Press the Windows key to open your search bar.
  • Type PowerShell and press Enter to open it.
  • Install Claude Code by running this command:
irm https://claude.ai/install.ps1 | iex

What does this command do?

irm (short for Invoke-RestMethod) downloads the install script from Anthropic's servers. The pipe (|) sends the script directly to iex (Invoke-Expression), which runs it. This is the official native installer from Anthropic.

The installer may take a minute to complete. Once finished, it adds claude to your system path.

  • Verify the installation by running:
claude --version

✔️ I see a version number

Claude Code is installed and ready. You can move on to the next substep.

ⓧ Command not found or error

If PowerShell does not recognize claude, try these fixes:

  • Close PowerShell completely, reopen it, and run claude --version again. The system path sometimes needs a fresh session to pick up new entries.
  • If it still fails, rerun the install command above. Look for any error messages during installation.
  • As an alternative, install via WinGet by running:
winget install Anthropic.ClaudeCode

After installing, close and reopen PowerShell, then run claude --version to confirm.

Auto-updates included

Native installations automatically update in the background to keep you on the latest version. You do not need to manually update Claude Code after installing.

Verify Git for Windows is installed

Git for Windows is recommended because it gives Claude Code access to the Bash shell tool. Without it, Claude Code can only use PowerShell as its shell. Bash provides richer file operations that Claude Code can leverage.

  • Check if Git is already installed by running:
git --version

✔️ I see a version number

Git is already installed. You are all set for the next substep.

ⓧ Command not found

  • Open your browser and go to https://git-scm.com/download/win.
  • The download should start automatically. If it does not, click the link for the latest x64 standalone installer.
  • Run the downloaded installer.
  • Click Next through each screen, keeping all the default settings.
  • Click Install, then Finish when it completes.
  • Close PowerShell completely, reopen it, and run:
git --version

You should now see a version number confirming Git is installed.

Why does Claude Code need Git?

If Git for Windows is not installed, Claude Code uses PowerShell as the shell tool instead of Bash. Bash provides more standard Unix-style file commands that Claude Code can use for richer operations like searching, filtering, and batch renaming.

Log in to Claude Code with your Pro subscription

Claude Code uses your existing Claude Pro subscription. You authenticate once and the connection persists across sessions.

  • Start Claude Code by running:
claude
  • Claude Code displays a list of authentication options. Select Use Claude.ai account (OAuth).
  • Your browser opens to an Anthropic authentication page. Sign in with the same account you use for your Claude Pro subscription.
  • After signing in, return to your PowerShell window. You should see a confirmation message that Claude Code is connected.

What does this cost?

Claude Code is included with your Claude Pro subscription at $20 per month. There are no additional API costs when using it through your Pro account.

  • Type exit and press Enter to close the Claude Code session for now.

Authentication not working?

Make sure you are signing in with the same email address that has an active Claude Pro subscription. If your browser did not open automatically, look for a URL printed in your terminal that you can copy and paste into your browser manually.

If you need to switch accounts later, use the /login command inside an active Claude Code session.

Help me troubleshoot Claude Code authentication

Your tools are installed and authenticated. Next up, you will create a messy workspace folder and let Claude Code loose on it.

Create Your Messy Workspace

Claude Code shines when it can read, write, and restructure actual files on your machine. To see this in action, you need a folder with real files in it.

In this step, you will create a "digital junk drawer" folder filled with scattered notes, code snippets, and random downloads. This gives Claude Code something meaningful to work with in later steps.

In this step, get ready to:
  • Create a messy project folder on your Desktop with sample files.
  • Open the folder in VS Code and start Claude Code.
  • Run your first exploration prompt to see Claude Code analyze your files.
Create the project folder and seed it with sample files

A realistic messy workspace has files of different types scattered around with no structure. You will create this from scratch using PowerShell.

  • Switch back to your PowerShell window and move to your Desktop by running this command:
cd ~/Desktop
  • Create your project folder and move into it by running these commands:
mkdir my-workspace
cd my-workspace
  • Confirm the folder was created by running:
pwd

You should see a path ending in Desktop\my-workspace.

Seeing an error with mkdir?

If you see a "file already exists" error, you may have a my-workspace folder on your Desktop from a previous attempt. Delete it in File Explorer, then try the mkdir command again.

help me fix a mkdir error in PowerShell

  • Seed your workspace with sample files by running this script:
# Create text notes
"Meeting notes from Tuesday - discuss API redesign with the team" | Out-File meeting-notes.txt
"TODO: fix login bug, update readme, call dentist, renew subscription" | Out-File todo.txt
"Random brainstorm ideas for the hackathon project" | Out-File ideas-brainstorm.txt

# Create Python code snippets
"import requests`nresponse = requests.get('https://api.example.com/data')`nprint(response.json())" | Out-File api_test.py
"def calculate_total(items):`n    return sum(item['price'] for item in items)" | Out-File utils.py
"# untitled script`nfor i in range(10):`n    print(i)" | Out-File untitled.py

# Create empty image placeholders
New-Item -ItemType File photo_2024_vacation.jpg
New-Item -ItemType File screenshot_final_FINAL.png
New-Item -ItemType File logo-old-version.png

# Create generic and old download files
"This is a backup of something important maybe" | Out-File backup_copy_2.txt
"Draft of the Q3 proposal - needs review" | Out-File proposal_draft_v2_FINAL.txt
"Notes from the Monday webinar on cloud architecture" | Out-File "Copy of notes.txt"

What do these commands do?

Each Out-File command creates a text file with content you provide. The New-Item -ItemType File commands create empty files (simulating images you might have lying around).

The backtick-n (`n) in the Python snippets is PowerShell's way of inserting a newline character inside a string.

  • Verify all files were created by running:
ls

You should see 12 files listed: a mix of .txt, .py, .jpg, and .png files with inconsistent naming.

Don't see 12 files?

Make sure you pasted the entire script. If some files are missing, run the specific Out-File or New-Item commands for the missing files again.

If you see an error about "Copy of notes.txt", make sure the filename is wrapped in double quotes since it contains spaces.

help me figure out why my PowerShell file creation commands aren't working

Open the folder in VS Code and start Claude Code

Now that your messy workspace exists, you will open it in VS Code and launch Claude Code from the integrated terminal.

  • Open your my-workspace folder in VS Code by running this command in PowerShell:
  • VS Code will open with your folder loaded in the Explorer sidebar.
code .

What does code . do?

The code command is VS Code's CLI launcher. The dot (.) means "the current directory." Together, they open VS Code with your current folder as the workspace.

  • In VS Code, open the integrated terminal by pressing Ctrl+` (the backtick key below Esc).
  • Confirm the terminal opened in the correct folder by checking the path shown in the terminal prompt. It should end in my-workspace.
  • Start Claude Code by running:
claude

Claude Code will ask if you trust the files in this folder.

  • Select Yes to grant Claude Code permission to read and write files in my-workspace.

You should see Claude Code's interactive prompt appear, ready for your input.

Terminal not opening in the right folder?

If your VS Code terminal shows a different path, type cd ~/Desktop/my-workspace and press Enter to navigate manually.

If code . did not open VS Code, it may not be in your system PATH. Open VS Code using the Windows key search bar (press the Windows key, type Visual Studio Code, press Enter), then open the folder with File > Open Folder.

help me open my workspace folder in VS Code and start Claude Code

Explore with your first prompt

One of the best prompt patterns for Claude Code is "explore first, act later." Before asking Claude Code to reorganize anything, ask it to analyze what it sees.

  • Type this prompt into Claude Code and press Enter:
What's in this folder? Summarize what you see.

What is Claude Code doing?

Claude Code reads your file system directly. It lists the files, reads their contents, and identifies patterns (file types, naming conventions, apparent purpose).

This is different from a chatbot. Claude Code is not guessing what might be in your folder. It actually opens and inspects the files on your machine.

Claude Code responds with a context-aware summary of your workspace. It identifies the different file types, notes the disorganized naming, and may suggest improvements.

Read the tool use indicators

Watch for the tool use indicators in Claude Code's output. You will see it call tools like ls and cat (or their PowerShell equivalents) to inspect your files. This shows you exactly how Claude Code interacts with your file system.

Your messy workspace is ready and Claude Code already understands what is in it. Next up, you will teach Claude Code your personal preferences by building a CLAUDE.md file.

Build Your Personalized CLAUDE.md

Every time you start a new Claude Code session, it begins with a blank slate. It has no idea how you like your files named, how you prefer folders organized, or what coding conventions you follow.

A CLAUDE.md file solves this. It gives Claude Code persistent memory that loads automatically at the start of every session. In this step, you will create one and fill it with your personal preferences.

In this step, get ready to:
  • Initialize a starter CLAUDE.md with the /init command.
  • Add your personalized coding preferences and conventions.
  • Verify that Claude Code loads your preferences automatically across sessions.
Initialize project memory with /init

Claude Code has a built-in command that scans your project and generates a starting CLAUDE.md for you. It looks at your files and auto-discovers what it can about your project structure.

  • In your Claude Code session, run the /init command by typing it and pressing Enter:
/init

Claude Code scans your folder and proposes a CLAUDE.md file. Review the proposed content and accept the change when prompted.

What does /init do?

The /init command analyzes your codebase and creates a CLAUDE.md file with build commands, test instructions, and project conventions it discovers automatically.

Since your my-workspace folder contains a mix of unrelated files, the generated content will be minimal. That is expected. You will fill it in with your own preferences next.

  • Confirm that CLAUDE.md now appears in your my-workspace folder by checking the Explorer sidebar in VS Code.

Don't see CLAUDE.md in the sidebar?

Make sure you accepted the proposed change when Claude Code showed you the file content. If you declined it, run /init again and accept the edit this time.

If the file still does not appear, click the refresh icon in the Explorer sidebar. VS Code sometimes needs a moment to detect new files.

help me troubleshoot why CLAUDE.md was not created after running /init

Personalize your CLAUDE.md with preferences

The auto-generated CLAUDE.md is just a starting point. The real power comes from teaching Claude Code your personal style so it follows your conventions in every future session.

  • Ask Claude Code to update your CLAUDE.md with your preferences by typing this prompt (customize the placeholders with your own style):
Update my CLAUDE.md with these personal preferences:

- File naming: I prefer [[NAMING_STYLE="kebab-case, snake_case, or camelCase"]]
- Folder organization: [[FOLDER_STYLE="group by file type, group by project, or group by date"]]
- Coding style: [[CODING_STYLE="your preferred style, e.g. always add comments, keep functions short, use descriptive variable names"]]
- Always do: [[ALWAYS_DO="things you always want, e.g. add file headers, use consistent indentation"]]
- Never do: [[NEVER_DO="things you never want, e.g. never delete files without asking, never use abbreviations in names"]]

What does this prompt do?

Claude Code reads your prompt and edits the CLAUDE.md file directly. It adds sections for your naming conventions, folder preferences, coding style, and your always-do and never-do rules.

These preferences are loaded at the start of every future session. Claude Code will follow them automatically without you having to repeat yourself.

  • Review the proposed changes that Claude Code shows you and accept them.
  • Open CLAUDE.md in VS Code by clicking it in the Explorer sidebar to confirm your preferences are written in the file.

Keep it under 200 lines

Anthropic recommends keeping your CLAUDE.md under 200 lines for best adherence. Short, specific rules work better than long paragraphs. Think of it as a cheat sheet, not an essay.

Claude Code did not update the file?

If Claude Code responded with advice instead of editing the file, rephrase your prompt to be more direct. Try: "Edit my CLAUDE.md file and add a section called Preferences with these rules:" followed by your list.

help me get Claude Code to edit my CLAUDE.md file instead of just giving advice

Verify persistence by exiting and restarting

The whole point of CLAUDE.md is that it loads automatically every time you start a session. Let's prove this works by exiting Claude Code and starting it fresh.

  • Exit your current Claude Code session by typing:
exit
  • Start a new Claude Code session by running:
claude
  • Test that your preferences loaded by asking:
What do you know about my preferences?

Claude Code should respond with the preferences you added to CLAUDE.md. It knows your naming conventions, folder style, and rules without you telling it again.

Why does this work?

CLAUDE.md files are markdown files that Claude Code reads at the start of every session. As long as the file exists in your project folder, Claude Code loads it automatically.

This means every future session in this folder starts with your preferences already in context. No repetition needed.

Claude Code does not mention your preferences?

Make sure you are still in the my-workspace directory when you run claude. Claude Code only loads the CLAUDE.md from the current working directory.

You can also run /memory inside your session to see all memory files that Claude Code loaded. Confirm CLAUDE.md appears in the list.

help me figure out why Claude Code is not loading my CLAUDE.md preferences

Your Claude Code now has a persistent memory of how you work. Next up, you will put those preferences to work by reorganizing your messy workspace folder using different prompt patterns.

Reorganize Your Folder with Prompt Patterns

Your CLAUDE.md is loaded and Claude Code knows exactly how you like things organized. Now it is time to put that knowledge to work on the messy files in your workspace.

Instead of diving straight into moving files, you will practice three distinct prompting patterns that professional developers use with Claude Code. Each pattern gives you a different level of control over how Claude Code operates on your file system.

In this step, get ready to:
  • Use the "Explore then Act" pattern to plan before making changes.
  • Use the "Step-by-step instruction" pattern to reorganize files with a numbered task list.
  • Use the "Verify and report" pattern to confirm nothing was lost.
Use the "Explore then Act" pattern

The safest way to use an AI agent on your real files is to let it analyze first, then act second. This prevents surprises and gives you a chance to approve the plan before anything moves.

  • In your Claude Code session in the VS Code terminal, type the following prompt and press Enter:
Analyze the files in this folder and propose an organization plan. Don't make any changes yet - just tell me what you'd do and why.

Why explore before acting?

By explicitly telling Claude Code not to make changes yet, you keep full control. Claude Code will read every file, analyze its content, and present a proposed plan. You can review, ask questions, or adjust before anything happens.

This matches Anthropic's official prompting advice: let Claude explore and understand your project before making changes.

Claude Code will respond with a breakdown of the files it found and a proposed folder structure. Take a moment to read through the plan.

  • Once you are happy with the proposed plan, approve it by typing this prompt:
That plan looks good. Go ahead and execute it.
  • Claude Code will ask for permission before creating directories and moving files. Accept each file change when prompted.

Adjust the plan if needed

If part of the plan does not match your preferences in CLAUDE.md, tell Claude Code what to change. For example: "Actually, put all images in a folder called assets instead of images." Claude Code will adjust because it treats your feedback as part of the conversation.

Use the "Step-by-step instruction" pattern

Sometimes you know exactly what you want done. A numbered list gives Claude Code precise instructions to follow in order, leaving no room for interpretation.

  • Give Claude Code a numbered list of reorganization tasks by typing this prompt:
Follow these steps exactly:
1. Create subdirectories for each file type if they don't already exist (notes, code, images, misc)
2. Move each file into the appropriate subdirectory based on its extension
3. Rename all files to follow my naming convention from CLAUDE.md
4. If any file doesn't clearly fit a category, put it in misc

What does this prompt do?

Numbered steps tell Claude Code the exact order of operations. It will handle each step sequentially and ask for permission at each file change.

Notice that step 3 references your CLAUDE.md naming convention. Because CLAUDE.md is loaded automatically, Claude Code already knows your preferred style without you repeating it.

  • Accept each file change as Claude Code works through the steps. You will see it creating directories, moving files, and renaming them according to your preferences.

Watch the VS Code file explorer on the left as files move into their new homes. The folder structure updates in real time.

Claude Code skipping a file?

If Claude Code misses a file or puts it in the wrong folder, tell it directly: "You missed meeting-notes.txt, move it to the notes folder." Claude Code remembers the full conversation, so it understands what you are referring to.

If Claude Code is not following your naming convention, remind it: "Check my CLAUDE.md for naming rules and apply them to the files you just moved."

Help me troubleshoot why Claude Code is not following my instructions.

Use the "Verify and report" pattern

After making big changes to your file system, you want confirmation that everything landed correctly. The verify pattern asks Claude Code to audit its own work.

  • Ask Claude Code to verify the reorganization by typing this prompt:
Verify the reorganization is complete. List the new folder structure as a tree, confirm the total file count matches what we started with, and flag anything that looks wrong.

What does this prompt do?

This prompt asks Claude Code to do three things: show you the new structure, confirm no files were lost (by comparing the count), and flag any issues. It is a self-check that catches mistakes before you move on.

Claude Code will display a tree view of your reorganized folder. Confirm that the file count matches and no files are missing.

  • Check your token usage for this session by typing this command:
/cost

What is /cost?

The /cost command shows how many tokens your session has used. Since Claude Code is included with your Claude Pro subscription, this does not represent an extra charge. It helps you understand how much of your session capacity a task consumes.

  • Look at the VS Code file explorer to confirm your my-workspace folder now shows clean subdirectories with your files sorted inside them.

Files seem to be missing?

If Claude Code's verification shows a different file count than expected, ask it: "List every file in this workspace recursively so I can check." This forces a full listing you can compare against your original files.

Remember that CLAUDE.md itself is a file in the folder. It should be counted but does not need to be moved into a subdirectory.

Help me figure out why my file count does not match after reorganization.

Your workspace is clean and organized. Next up, you will build a reusable prompt library so you can apply these patterns to any future project without starting from scratch.

Build Your Prompt Library

Your workspace is now clean and organized. You accomplished that using several distinct prompting patterns, from exploration to verification.

Without a written reference, those prompt techniques slip away after a few days. In this step, you'll have Claude Code document the patterns into a reusable library file you can pull up for any future project.

In this step, get ready to:
  • Create a prompt-library.md file documenting the four core patterns you used today.
  • Add advanced patterns for code review, creative work, and constraint-based prompting.
  • Review and personalize the library to match your style.
Create a prompt-library.md file

Throughout this project, you used four core prompting patterns with Claude Code. "Explore" asked Claude Code to analyze before acting. "Transform" gave it permission to make changes. "Multi-step" used numbered instructions. "Verify" asked it to confirm results.

Now you'll have Claude Code capture all four into a reference file with reusable templates.

  • In your Claude Code session in the VS Code terminal, type this prompt:
Create a file called prompt-library.md in this folder. Document these four prompt patterns I used today, with a description and a reusable template for each:
1. Explore - asking you to analyze something before making changes
2. Transform - giving you permission to reorganize, rename, or restructure files
3. Multi-step - providing numbered instructions for complex tasks
4. Verify - asking you to confirm results and report back

What does this prompt do?

This prompt asks Claude Code to create a new Markdown file and fill it with structured documentation. Each pattern gets a description explaining when to use it and a template the learner can copy-paste in future sessions.

Because your CLAUDE.md is loaded, Claude Code already knows your naming conventions and formatting preferences. The generated file should reflect those.

  • When Claude Code asks for permission to create the file, accept the change.
  • Look at the VS Code Explorer sidebar. You should see prompt-library.md appear at the root of your my-workspace folder.

Don't see the new file?

Make sure you accepted the file creation when Claude Code asked for permission. If you declined, re-run the same prompt and accept this time.

If the Explorer sidebar still looks empty, click the refresh icon at the top of the Explorer panel. VS Code occasionally needs a nudge to pick up new files created by external processes.

Help me troubleshoot why Claude Code didn't create my prompt-library.md file.

Add advanced patterns for future use

The four patterns above cover what you did today. Three additional patterns will expand your toolkit for future work: reviewing code changes, iterating on creative output, and working within constraints like token budgets.

  • Type this prompt into Claude Code to add the advanced patterns:
Add three more patterns to prompt-library.md:
1. "Diff and explain" - for code review, where I ask you to show what changed and why
2. "Generate then iterate" - for creative work, where I ask you to produce a first draft and then refine it based on my feedback
3. "Constraint-based" - for working within limits, where I specify constraints like token budgets, file size limits, or time boundaries
Include a description and reusable template for each, matching the format of the existing patterns.

Why these three patterns?

"Diff and explain" is useful when Claude Code modifies existing code. You ask it to show exactly what changed and the reasoning behind each change.

"Generate then iterate" works well for writing tasks, README drafts, or any output that benefits from multiple passes. You get a rough first version, then refine with feedback.

"Constraint-based" prompts set boundaries upfront. For example, "Refactor this file but keep it under 100 lines" or "Summarize in 3 bullet points."

  • Accept the file modification when Claude Code asks for permission.
  • Click on prompt-library.md in the Explorer sidebar to open it. You should see all seven patterns listed with descriptions and templates.

Only seeing the original four patterns?

Claude Code may have created a separate file instead of updating the existing one. Check if a second file appeared (like prompt-library-v2.md or similar). If so, ask Claude Code to merge them into a single prompt-library.md.

If the file looks unchanged, make sure you accepted the edit. Try the prompt again.

Help me get Claude Code to add patterns to my existing prompt-library.md file.

Review and personalize your library

Claude Code generated the file, but you should own the content. Reading through the patterns and adjusting the language to match how you actually think will make the library far more useful when you come back to it weeks from now.

  • In the VS Code editor tab showing prompt-library.md, read through each pattern and its template.
  • Note anything that feels too generic or does not match how you prefer to phrase instructions.
  • Switch back to the Claude Code session in your terminal and type a prompt like this to adjust the file:
Review prompt-library.md and adjust it:
- Make the templates sound like how I actually write (check my CLAUDE.md for my style preferences)
- If any pattern description is too wordy, tighten it up
- Make sure each template is something I can copy-paste directly with minimal editing

Why reference CLAUDE.md in this prompt?

By pointing Claude Code back to your CLAUDE.md, you remind it of the style and formatting preferences you set earlier. This creates a feedback loop where your personalized memory improves the output of every future prompt.

  • Accept the changes when Claude Code asks for permission.
  • Check the VS Code editor tab. The file should refresh automatically with the personalized wording. Skim the templates to confirm they feel like something you would actually type.

Keep iterating

You can run as many refinement prompts as you like. Try asking Claude Code to add an example usage for each pattern, or to reorder the patterns by how often you expect to use them. The file is yours to shape.

File not updating in the editor?

If the VS Code editor tab still shows the old content, close the tab and reopen the file from the Explorer sidebar. Some VS Code configurations do not auto-reload files changed by external processes.

Help me get VS Code to show the latest version of my prompt-library.md file.

You now have a personalized prompt library sitting right in your workspace. Every time you start a new Claude Code session in this folder, your CLAUDE.md gives Claude Code memory and your prompt-library.md gives you memory.

Secret mission

Build a Digital Audit Command

You have learned how to explore, transform, and verify with Claude Code. Now combine all of those prompt patterns into a single multi-step command that audits your entire workspace and produces a professional report.

Clean Up Your Resources

Clean Up Your Resources

Decide whether to keep your resources running, pause them to come back later, or delete them entirely. This project runs entirely locally and Claude Code is included with your Pro subscription, so there are no ongoing costs.

Resources you used:

  • my-workspace folder on your Desktop (local files).
  • Claude Code CLI installation (included with your Pro subscription).
  • CLAUDE.md, prompt-library.md, and audit-report.md files inside the workspace folder.

Keep everything running

No action needed. Choose this if you plan to keep using Claude Code on future projects.

  • Your my-workspace folder, CLAUDE.md, and prompt library stay on your machine.
  • Claude Code is included in your Pro subscription at no additional cost.
  • Your CLAUDE.md will load automatically the next time you run claude in the my-workspace folder.

Pause - I'll come back to this later

Delete the practice workspace folder but keep Claude Code installed for future projects.

  • If you have an active Claude Code session, type exit to close it.
  • Delete the workspace folder by running this command in PowerShell:
Remove-Item -Recurse -Force "$env:USERPROFILE\Desktop\my-workspace"
  • Claude Code stays installed and ready. Run claude in any folder to start a new session.

Delete - I don't want to use this again

Remove all project resources and uninstall Claude Code from your machine.

  • If you have an active Claude Code session, type exit to close it.
  • Delete the workspace folder by running this command in PowerShell:
Remove-Item -Recurse -Force "$env:USERPROFILE\Desktop\my-workspace"
  • Uninstall Claude Code by running:
winget uninstall Anthropic.ClaudeCode
  • Confirm the uninstall completes successfully in your terminal output.

Nice Work!

Nice Work!

You did it. You turned a messy folder into an organized workspace using nothing but natural language commands in your terminal.

You've learned how to:

  • Created a personalized CLAUDE.md that gives Claude Code persistent memory about your preferences, coding style, and project conventions.
  • Reorganized a messy folder into a clean, logical structure using AI-powered terminal commands and practiced the Explore, Transform, Multi-step, and Verify prompt patterns.
  • Built a prompt-library.md reference file with reusable prompt patterns you can apply to any future Claude Code session.
  • Built a digital audit command that analyzes storage, finds duplicates, identifies forgotten files, and generates a readable report.

Ready to quiz yourself?