Skip to content

Choosing Your AI Knowledge Base Folder Structure

Purpose: Share this file with your AI assistant (Claude Code, Codex CLI, etc.) to help it create the right folder structure for your needs.


How to Use This Reference

Tell your AI:

"Read this reference file and help me create a folder structure based on my role: [describe yourself]"

The AI will recommend and create an appropriate structure.


The Essential Files (Required for All Structures)

No matter which structure you choose, you need these files at the root:

πŸ“„ AGENTS.md        # Universal AI context (all tools read this)
πŸ“„ CLAUDE.md        # Claude-specific instructions (optional)
πŸ“„ CODEX.md         # Codex/GPT-specific instructions (optional)
πŸ“„ GEMINI.md        # Gemini-specific instructions (optional)

AGENTS.md is the universal context file. Tool-specific files extend it for customization.


1. PARA Method (Tiago Forte)

Best for: General productivity, life management, mixed personal/professional use

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ Projects/        # Active, time-bound work with deadlines
β”œβ”€β”€ πŸ“ Areas/           # Ongoing responsibilities (Health, Finance, Career)
β”œβ”€β”€ πŸ“ Resources/       # Reference material, topics of interest
β”œβ”€β”€ πŸ“ Archive/         # Completed or inactive items
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

Philosophy: Organize by actionability, not topic. Projects are active, Areas are ongoing, Resources are reference, Archive is done.


2. Johnny Decimal

Best for: People who want strict organization, large file collections, team environments

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ 10-19 Administration/
β”‚   β”œβ”€β”€ πŸ“ 11 Company/
β”‚   β”œβ”€β”€ πŸ“ 12 Finance/
β”‚   └── πŸ“ 13 Legal/
β”œβ”€β”€ πŸ“ 20-29 Clients/
β”‚   β”œβ”€β”€ πŸ“ 21 Active Clients/
β”‚   └── πŸ“ 22 Past Clients/
β”œβ”€β”€ πŸ“ 30-39 Projects/
β”‚   β”œβ”€β”€ πŸ“ 31 Current/
β”‚   └── πŸ“ 32 Completed/
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

Philosophy: Every item gets a unique ID (XX.XX). Maximum 10 areas, 10 categories per area. Forces constraints to prevent sprawl.


3. ACE Method (Nick Milo)

Best for: Obsidian power users, networked thinking, knowledge workers

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ Atlas/           # Maps of Content, indexes, navigation
β”œβ”€β”€ πŸ“ Calendar/        # Time-based notes (daily, weekly, meetings)
β”œβ”€β”€ πŸ“ Efforts/         # Active work, projects, initiatives
β”œβ”€β”€ πŸ“ Sources/         # Books, articles, references (optional)
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

Philosophy: Atlas = navigation layer, Calendar = time layer, Efforts = action layer. Relies heavily on linking between notes.


4. Minimal / Steph Ango Approach

Best for: Beginners, people who over-engineer, bottom-up thinkers

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ notes/           # All your notes, flat
β”œβ”€β”€ πŸ“ daily/           # Daily notes (YYYY-MM-DD.md)
β”œβ”€β”€ πŸ“ templates/       # Note templates
β”œβ”€β”€ πŸ“ attachments/     # Images, PDFs, files
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

Philosophy: Start simple, add structure only when needed. Use links and tags over folders. Let organization emerge from usage.


Role-Based Starter Templates

For Consultants / Agencies

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ 00-INBOX/            # Quick capture
β”œβ”€β”€ πŸ“ 10-CLIENTS/          # Client workspaces
β”‚   β”œβ”€β”€ πŸ“ client-alpha/
β”‚   β”‚   β”œβ”€β”€ context.md      # Client background
β”‚   β”‚   β”œβ”€β”€ projects/       # Their projects
β”‚   β”‚   └── meetings/       # Meeting notes
β”‚   └── πŸ“ client-beta/
β”œβ”€β”€ πŸ“ 20-INTERNAL/         # Your business operations
β”‚   β”œβ”€β”€ processes/
β”‚   β”œβ”€β”€ templates/
β”‚   └── finance/
β”œβ”€β”€ πŸ“ 30-KNOWLEDGE/        # Reference & learning
β”œβ”€β”€ πŸ“ 40-ARCHIVE/          # Completed work
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

For Content Creators / YouTubers

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ 00-INBOX/            # Ideas, inspiration
β”œβ”€β”€ πŸ“ 10-CONTENT/          # Content by status
β”‚   β”œβ”€β”€ πŸ“ ideas/           # Raw ideas
β”‚   β”œβ”€β”€ πŸ“ drafts/          # In progress
β”‚   β”œβ”€β”€ πŸ“ ready/           # Ready to publish
β”‚   └── πŸ“ published/       # Live content
β”œβ”€β”€ πŸ“ 20-AUDIENCE/         # Community, comments, feedback
β”œβ”€β”€ πŸ“ 30-BRAND/            # Style guides, assets, voice
β”œβ”€β”€ πŸ“ 40-RESEARCH/         # Topics, trends, competitors
β”œβ”€β”€ πŸ“ 50-BUSINESS/         # Sponsors, analytics, revenue
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

For Developers / Engineers

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ 00-INBOX/            # Quick notes, snippets
β”œβ”€β”€ πŸ“ 10-PROJECTS/         # Active project docs
β”‚   β”œβ”€β”€ πŸ“ project-x/
β”‚   β”‚   β”œβ”€β”€ architecture.md
β”‚   β”‚   β”œβ”€β”€ decisions.md    # ADRs
β”‚   β”‚   └── todos.md
β”‚   └── πŸ“ project-y/
β”œβ”€β”€ πŸ“ 20-LEARNING/         # Tech notes, tutorials, TILs
β”œβ”€β”€ πŸ“ 30-REFERENCE/        # Docs, cheatsheets, configs
β”œβ”€β”€ πŸ“ 40-TEMPLATES/        # Code templates, boilerplate
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

For Knowledge Workers / Researchers

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ 00-INBOX/            # Capture everything
β”œβ”€β”€ πŸ“ 10-PROJECTS/         # Active research/work
β”œβ”€β”€ πŸ“ 20-NOTES/            # Evergreen notes (Zettelkasten-style)
β”œβ”€β”€ πŸ“ 30-SOURCES/          # Books, papers, articles
β”œβ”€β”€ πŸ“ 40-OUTPUTS/          # Writing, presentations, deliverables
β”œβ”€β”€ πŸ“ 50-META/             # Templates, workflows, logs
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

For Solopreneurs / Small Business

πŸ“ your-vault/
β”œβ”€β”€ πŸ“ 00-INBOX/            # Quick capture
β”œβ”€β”€ πŸ“ 10-BUSINESS/         # Core business
β”‚   β”œβ”€β”€ strategy/
β”‚   β”œβ”€β”€ finance/
β”‚   └── operations/
β”œβ”€β”€ πŸ“ 20-CLIENTS/          # Client work (if applicable)
β”œβ”€β”€ πŸ“ 30-MARKETING/        # Content, campaigns, brand
β”œβ”€β”€ πŸ“ 40-PRODUCTS/         # Products/services
β”œβ”€β”€ πŸ“ 50-LEARNING/         # Skills, courses, notes
β”œβ”€β”€ πŸ“ 60-PERSONAL/         # Personal notes (optional)
β”œβ”€β”€ πŸ“„ AGENTS.md
└── πŸ“„ CLAUDE.md

Principles for Any Structure

1. Start Simple, Evolve

Don't create 50 folders on day one. Start with 3-5, add when you feel friction.

2. Numbered Prefixes (Optional but Helpful)

10-, 20-, 30- keeps folders in order regardless of name. Skip numbers (10, 20, 30 not 1, 2, 3) to leave room for insertion.

3. INBOX is Your Friend

A catch-all folder for quick capture. Process weekly. Prevents "where does this go?" paralysis.

4. Flat > Deep

2-3 levels max. Deep nesting = lost files. If you're going 4+ levels deep, rethink the structure.

5. The Folder Isn't the Point

The AI reads AGENTS.md regardless of folder structure. The structure helps YOU navigate. The AI just needs good context files.


Quick Decision Guide

If you are... Start with...
Unsure / new to this Minimal (notes, daily, templates, attachments)
A consultant with clients Client-based structure
A content creator Content pipeline structure
A developer Project-based with learning
Managing life + work PARA method
Want strict organization Johnny Decimal
Obsidian power user ACE method

How to Ask Your AI to Create a Structure

Example prompts:

"I'm a freelance consultant with 5 active clients. Create a folder structure for my knowledge base."

"I'm a YouTuber who makes tech tutorials. Set up a folder structure for content creation."

"I'm new to this. Give me the simplest possible structure to start with."

"I want to use PARA method. Create the folders and a starter AGENTS.md."

The AI will create the folders and initial files based on your description.


Sources / Inspiration

  • PARA Method - Tiago Forte (Building a Second Brain)
  • Johnny Decimal - Johnny Noble (johnny.decimal)
  • ACE Method - Nick Milo (Linking Your Thinking)
  • Minimal Approach - Steph Ango (Obsidian CEO)
  • Zettelkasten - Niklas Luhmann (via SΓΆnke Ahrens)

Remember: The best structure is the one you'll actually use. Start simple, iterate based on friction.