Modern AI tools are very good at reading, summarizing, and connecting information, but many people overcomplicate their personal knowledge systems too early. You do not always need a vector database, embeddings, or a full RAG pipeline.

For a solo developer, freelancer, researcher, or small team, a well-organized Obsidian vault + Claude Code can work surprisingly well as a lightweight knowledge base.

This tutorial shows you how to build a simple “RAG-like” system using only:

• Obsidian
• Markdown files
• A clear folder structure
• Claude Code
• Optional browser clipping tools

The goal is simple: collect information, organize it into clean wiki pages, and ask Claude Code questions based on your own knowledge base.

1. What You Are Building

You are building a personal knowledge system where:

• Raw notes, articles, documents, and research are saved into one folder.
• Claude Code turns that raw material into structured wiki pages.
• Obsidian becomes the visual interface for browsing your knowledge.
• Claude Code can later answer questions by reading your organized files.

This is not a traditional RAG system.

There is:

• no vector database,
• no embeddings,
• no complicated retrieval service,
• no backend infrastructure.

Instead, the system works because your files are structured clearly enough for both you and Claude Code to navigate.

Think of it as a human-readable knowledge base that is also AI-friendly.

2. When This System Makes Sense

This setup is ideal if you are:

• learning programming,
• managing research notes,
• building projects with Claude Code,
• collecting technical documentation,
• organizing business ideas,
• saving useful articles,
• building a personal wiki,
• working alone or in a small team.

It works well for dozens or hundreds of documents.

You may need a real RAG system later if you are dealing with:

• thousands or millions of documents,
• many users,
• strict retrieval performance requirements,
• enterprise search,
• production AI applications.

But for personal use, project research, and small-team knowledge management, this simple system is often enough.

Start simple. Move to real RAG only when this setup clearly becomes too limited.

3. Install Obsidian

First, install Obsidian from the official website.

After installation, create a new vault.

You can name it something like:

my-knowledge-vault

An Obsidian vault is just a normal folder on your computer.

For example, on Ubuntu or Linux:

/home/yourname/Documents/my-knowledge-vault

On Windows:

D:\Obsidian\my-knowledge-vault

Everything inside this folder can be opened in Obsidian and also accessed by Claude Code.

4. Create the Basic Folder Structure

Inside your Obsidian vault, create this structure:

my-knowledge-vault/
  raw/
  wiki/
    MASTER_INDEX.md
  CLAUDE.md

Each part has a clear purpose.

raw/

This folder stores unprocessed source material.

Put messy information here, such as:

• copied articles,
• rough notes,
• documentation,
• saved webpages,
• copied code explanations,
• research dumps,
• project ideas,
• PDFs converted to Markdown.

Do not worry about making this folder perfect. It is only the staging area.

wiki/

This folder stores clean, organized knowledge pages.

Claude Code will create structured topics here.

For example:

wiki/
  claude-code/
  fastapi/
  react/
  ecommerce/
  paypal/

wiki/MASTER_INDEX.md

This is the main index of your knowledge base.

It should list all major wiki topics so both you and Claude Code know what exists.

CLAUDE.md

This file tells Claude Code how to behave inside your knowledge base.

It is like a rulebook for maintaining your personal wiki.

5. Use Claude Code to Create the Structure

Open a terminal inside your Obsidian vault:

cd /path/to/my-knowledge-vault
claude

Then paste this prompt:

Create a simple Obsidian knowledge base structure.

Create these folders and files:

- raw/
- wiki/
- wiki/MASTER_INDEX.md
- CLAUDE.md

The raw folder is for unprocessed source material.
The wiki folder is for clean organized wiki articles.
The MASTER_INDEX.md file should list all wiki topics.
The CLAUDE.md file should explain how Claude should maintain this knowledge base.

Do not delete any existing files.

Claude Code should create the required folders and starter files.

6. Add Rules to CLAUDE.md

The CLAUDE.md file is important because Claude Code can use it as project-level guidance.

Open CLAUDE.md and add something like this:

# Claude Knowledge Base Rules

This folder is an Obsidian knowledge base.

## Folder structure

- `raw/` contains unprocessed source material.
- `wiki/` contains clean wiki pages.
- `wiki/MASTER_INDEX.md` lists all created wiki topics.

## Main rules

When creating a wiki:
1. Read relevant files from `raw/`.
2. Create a new folder inside `wiki/` for the topic.
3. Create an `index.md` file for that topic.
4. Create smaller article files when needed.
5. Use Obsidian wiki links like `[[Some Topic]]`.
6. Update `wiki/MASTER_INDEX.md`.
7. Keep writing clear and beginner-friendly.
8. Do not delete raw files.
9. Do not invent facts not supported by the raw files.
10. If something is uncertain, say it is uncertain.

## Wiki article style

Each wiki article should include:

- Title
- Summary
- Key ideas
- Detailed explanation
- Practical examples
- Related links
- Source notes if available

## Question answering

When I ask questions:
1. First check `wiki/MASTER_INDEX.md`.
2. Then open the relevant topic index.
3. Then read the specific article files.
4. Answer based on the knowledge base.
5. If the answer is not in the knowledge base, say so.

This gives Claude Code a repeatable workflow.

Without this file, Claude may still help, but it will not have consistent rules for how to organize your vault.

7. Add Raw Material

Now start putting useful information into the raw/ folder.

Example files:

raw/claude-code-notes.md
raw/ecommerce-ideas.md
raw/paypal-sandbox-guide.md
raw/fastapi-auth-notes.md
raw/react-product-page-design.md
raw/ubuntu-server-setup.md

You can manually create Markdown files and paste your notes inside.

For example:

# PayPal Sandbox Notes

Source: PayPal documentation and my own testing notes

Main points:
- Use a sandbox business account as seller.
- Use a sandbox personal account as buyer.
- Backend must use sandbox API URL.
- Frontend should only expose the PayPal client ID.
- PayPal secret must stay on backend.

The raw folder does not need to be beautiful. It only needs to contain useful information.

8. Optional: Use Obsidian Web Clipper

If you often save webpages, install the Obsidian Web Clipper browser extension.

Configure it so saved pages go directly into:

raw/

This makes your workflow easier:

1. Find a useful article.
2. Clip it to Obsidian.
3. It appears in raw/.
4. Later, ask Claude Code to convert it into a wiki page.

For the first version of your system, you can skip this and just paste notes manually.

9. Optional: Save Images Locally

Some webpage clippers do not save images properly. They may only link to external image URLs.

If images matter to your notes, you can install an Obsidian community plugin such as a local image saver/downloader plugin.

This is optional.

For most programming, business, and research notes, text is enough.

10. Create Your First Wiki Topic

Suppose you have several raw files about Claude Code.

Ask Claude Code:

Create a wiki topic about Claude Code.

Use the relevant files in raw/.

Create:

wiki/claude-code/
wiki/claude-code/index.md
wiki/claude-code/getting-started.md
wiki/claude-code/common-prompts.md
wiki/claude-code/project-workflows.md

Update wiki/MASTER_INDEX.md.

Use Obsidian wiki links between related pages.
Keep the explanation beginner-friendly.

After Claude Code finishes, your structure may look like this:

wiki/
  MASTER_INDEX.md
  claude-code/
    index.md
    getting-started.md
    common-prompts.md
    project-workflows.md

Now you have a clean topic folder instead of random notes.

11. Example Topic Index

A good index.md file might look like this:

# Claude Code

## Summary

Claude Code is a coding assistant that can read, explain, edit, and create files inside a project folder.

## Main articles

- [[getting-started]]
- [[common-prompts]]
- [[project-workflows]]

## Key ideas

- Use clear goals.
- Ask Claude to inspect before editing.
- Use `PLAN.md` for larger projects.
- Ask Claude to test changes after editing.
- Keep prompts specific.

## Related topics

- [[FastAPI]]
- [[React]]
- [[PayPal Sandbox]]
- [[Ubuntu Development Environment]]

This style is simple, readable, and easy to navigate.

It also helps Claude Code find relevant information quickly.

12. Ask Questions Based on Your Knowledge Base

Once your wiki has structure, you can ask Claude Code questions like:

Based on my Obsidian knowledge base, explain how I should use Claude Code for my ecommerce project.

Or:

Look through the wiki and raw folders. What have I saved about PayPal sandbox testing? Summarize it and create a checklist.

Or:

Search my knowledge base for anything related to FastAPI authentication and explain the recommended approach.

Claude Code should first check:

wiki/MASTER_INDEX.md

Then it should open the relevant topic folder and read the related files.

This is why the index system matters.

13. Create Topic-Based Wikis from Long Notes

Long notes are hard to reuse. A better approach is to split them into smaller connected pages.

For example, suppose you have one long file about AI-assisted software development:

raw/ai-assisted-development-notes.md

Ask Claude Code:

Create a wiki topic from raw/ai-assisted-development-notes.md.

Topic name:
AI-Assisted Software Development

Create a folder:
wiki/ai-assisted-development/

Create these files:
- index.md
- software-3.md
- prompt-driven-development.md
- agentic-engineering.md
- verification-and-testing.md
- practical-checklist.md

Update wiki/MASTER_INDEX.md.

Use simple explanations and practical examples.
Use Obsidian wiki links between related files.

This turns one large file into a useful mini-wiki.

14. Suggested Topics for a Developer Vault

If you are learning web development and AI-assisted coding, useful topics could include:

wiki/claude-code/
wiki/fastapi/
wiki/react/
wiki/javascript/
wiki/ecommerce/
wiki/paypal/
wiki/authentication/
wiki/database-design/
wiki/ubuntu-linux/
wiki/deployment/
wiki/freelancing/
wiki/ai-assisted-development/

Each topic should have:

index.md
concept pages
checklists
common mistakes
useful prompts
implementation notes

This creates a personal technical library you can reuse across projects.

15. Recommended Daily Workflow

Use this simple workflow.

Step 1: Capture

Put raw information into:

raw/

Examples:

• project notes,
• articles,
• copied documentation,
• command-line fixes,
• Claude answers,
• design ideas,
• coding plans.

Step 2: Review

Ask Claude Code:

Review the new files in raw/ and suggest which wiki topics they belong to.

Step 3: Organize

Ask:

Turn the relevant raw files into clean wiki pages. Update MASTER_INDEX.md.

Step 4: Ask Questions

Ask:

Based on my wiki, what should I do next for my ecommerce project?

Step 5: Improve

Whenever you learn something new, add it to raw/, then ask Claude Code to integrate it into the correct wiki topic.

16. A Useful /goal Prompt for Claude Code

Use this inside your Obsidian vault:

/goal Maintain this Obsidian knowledge base as a lightweight RAG-like system.

Rules:
- raw/ contains unprocessed source material.
- wiki/ contains clean organized knowledge pages.
- wiki/MASTER_INDEX.md lists all wiki topics.
- Use Obsidian wiki links.
- Do not delete raw files.
- Do not invent unsupported facts.
- Keep explanations beginner-friendly and practical.

When I give you new raw material:
1. Identify the topic.
2. Create or update the correct wiki folder.
3. Create or update index.md.
4. Split long topics into smaller pages.
5. Add links between related pages.
6. Update MASTER_INDEX.md.
7. Tell me what changed.

When I ask questions:
1. Check MASTER_INDEX.md.
2. Read the relevant wiki pages.
3. Answer based on the knowledge base.
4. Mention if the answer is missing or uncertain.

This prompt gives Claude Code a clear operating mode.

17. Example: Build an Ecommerce Knowledge Wiki

If you are building an ecommerce website, create a topic like this:

Create a wiki topic called Ecommerce Website Building.

Use relevant files from raw/.

Create:
- wiki/ecommerce-website-building/index.md
- product-catalog.md
- shopping-cart.md
- paypal-checkout.md
- guest-checkout.md
- user-accounts.md
- deployment.md

Each file should explain:
- What it is
- Why it matters
- How to implement it
- Common mistakes
- Useful Claude Code prompts

Update wiki/MASTER_INDEX.md.

This gives you a reusable ecommerce development guide.

Later, when you forget how guest checkout or PayPal sandbox testing works, you can ask Claude Code to read your own wiki and explain it.

18. Example: Create a Learning Path

Once your vault has enough notes, you can ask Claude Code to create a learning plan:

Read my wiki topic about Claude Code and create a beginner learning path for me.

Include:
- What to learn first
- What commands to practice
- What small projects to build
- What mistakes to avoid
- A 7-day study plan

This turns your saved information into an action plan.

19. Why This System Works

This system works because Markdown is simple.

Markdown files are:

• easy to read,
• easy to edit,
• easy to search,
• easy for AI tools to understand,
• portable across apps,
• not locked inside a database.

Obsidian gives you a clean visual interface.

Claude Code gives you an assistant that can read, organize, connect, and explain your files.

The folder structure provides the retrieval path.

Instead of asking an AI to search a messy folder full of random files, you guide it through:

MASTER_INDEX.md
→ topic index
→ related article
→ answer

That is the core idea.

20. Limitations

This setup is powerful, but it is not magic.

It may struggle if:

• your vault has too many files,
• your folder structure is messy,
• pages are not indexed,
• raw notes are low quality,
• you ask broad questions without context,
• the answer requires information not saved in the vault.

To keep it useful:

• maintain MASTER_INDEX.md,
• create topic indexes,
• split long pages into smaller files,
• use clear filenames,
• add links between related pages,
• regularly clean up old notes.

21. Final Simple Version

Your whole system can be as simple as this:

vault/
  raw/
    messy notes and source material
  wiki/
    MASTER_INDEX.md
    clean organized topics
  CLAUDE.md

Your main commands are:

Create a wiki from this raw material.
Update the index.
Link related pages.
Answer based on my wiki.
Tell me what is missing.

This is a practical starting point for a personal AI-powered knowledge base.

Build it first. Use it for real work. Only move to a more complex RAG system when you clearly outgrow this simple approach.

Reference

Original YouTube video: YouTube Video Reference