Explore and understand

Lesson outcome

You will use Claude Code to make sense of something unfamiliar on your computer — not by reading documentation, but by pointing Claude Code at it and asking questions until you understand.

Why this matters in an agency

Agency owners constantly encounter things they did not build and do not fully understand: a developer's codebase, a CRM export file, a spreadsheet from a client, a configuration folder from a tool. The old approach is to either ignore it or spend hours googling. The operator approach is to point Claude Code at it and say "explain this to me." That skill — using Claude Code as an exploration tool — is one of the highest-leverage habits in this entire course.

Inputs, tools, and prerequisites

Claude Code running in your vault directory. The Obsidian vault you created in Module 2 (which now has a hidden .obsidian configuration folder inside it).

Step-by-step walkthrough

Explore the .obsidian folder

Your Obsidian vault has a hidden folder called .obsidian that contains configuration files. You did not create this folder — Obsidian did. You probably have no idea what is inside it. That makes it a perfect exploration target.

Start Claude Code in your vault directory and ask:

```
There is a hidden folder called .obsidian in this vault. Explore it and explain what each file and folder inside it does. I have never looked inside this folder before.
```

Claude Code will use the Glob tool to find files inside .obsidian, then read some of them, and explain what it finds. Allow the tool uses as they come. Watch what Claude Code does — it is searching, reading, and synthesizing, which is the same exploration process you would do manually but much faster.

Read the explanation. You will learn that .obsidian contains things like your workspace layout, any settings you changed, hotkey configurations, and plugin data. None of this is critical for you to memorize. The point is that you now understand what that folder does — and you got there in two minutes instead of thirty.

Ask follow-up questions

Good exploration is a conversation, not a single question. Ask follow-up questions based on what Claude Code told you:

```
Which of those files would I lose if I deleted the .obsidian folder? What would happen to my vault?
```

Or:

```
Is there anything in there I should back up separately from my notes?
```

Claude Code will answer based on the files it already read. This is the exploration pattern: start broad, then drill into whatever is interesting or useful. You are training yourself to treat Claude Code as a collaborator for understanding things, not just a tool for producing output.

Explore something else

Now try a different target. If you have a Downloads folder with miscellaneous files, point Claude Code at it:

```
Look at the files in my Downloads folder and tell me what is there. Group them by type and tell me which ones are probably safe to delete.
```

Or if you have any project folders from previous work:

```
Explore the folder at [path] and give me a summary of what this project is and how it is organized.
```

The specific folder does not matter. The skill is the same: point Claude Code at something, ask it to explain, and follow up until you understand.

Recognize what just happened

You just used Claude Code to understand things you did not build and could not have explored as quickly on your own. You did not write any code. You did not read any documentation. You asked questions in plain English and got useful answers. This is the operator model. You direct the exploration. Claude Code does the work. You decide what matters.

Failure modes and verification checks

The main failure mode is accepting Claude Code's explanation without questioning it. If something does not make sense, say so. Ask Claude Code to explain it differently or give an example. The other failure mode is only exploring things you already understand — push yourself to explore something genuinely unfamiliar.

Verification: after the exploration, can you explain in one or two sentences what the .obsidian folder contains and why it exists? If yes, the exploration worked.

Implementation checklist

• Start Claude Code in your vault directory.
• Ask Claude Code to explore the .obsidian folder and explain it.
• Ask at least two follow-up questions based on the initial explanation.
• Explore at least one other folder or file you did not create.
• Confirm you understand what you explored.

Immediate next action

Move to the next lesson. You are about to ask Claude Code to build something from scratch.

Exercise

Find the most confusing file on your computer — something you downloaded months ago, a config file from an application, or a spreadsheet a client sent you. Point Claude Code at it and ask: "Explain what this file is, what it contains, and whether I need to keep it." Evaluate the response. If Claude Code is wrong or unsure, it should tell you. If it gives a confident answer, verify it makes sense. The goal is to prove to yourself that Claude Code can make unfamiliar things understandable.