What is a Personal OS?
A Personal OS is just a folder structure on your computer with a few special files that help Claude (or any AI assistant) understand who you are, what you're working on, and how you like to work.
Think of it as giving Claude a map of your brain. Instead of explaining your projects and preferences every time, Claude already knows.
What You'll Need
VS Code
Free code editor where Claude Code runs.
Download here
Claude Pro or Max Account
Paid subscription required for Claude Code.
Subscribe here
Obsidian
Free note-taking app for viewing your files.
Download here
Important: Keep Sensitive Information Out
Claude can read any files in your Personal OS folder. Do not store:
- Passwords, API keys, or credentials
- Social Security numbers or government IDs
- Financial account numbers
- Medical records or health information
- Confidential work documents your employer hasn't approved for AI use
- Other people's personal information without consent
If you need to reference sensitive projects, create a note that describes the project without including the actual sensitive data.
Why This Matters
Without structure, every conversation with AI starts from scratch. You waste time re-explaining context. Claude gives generic advice because it doesn't know your situation.
With a Personal OS, everything changes:
Persistent Memory
Claude reads your files at the start of each session. It remembers your projects, preferences, and history.
Instant Context
No more "I'm working on a presentation about..." Just ask for help and Claude already knows what you're doing.
Better Suggestions
Because Claude understands your work patterns and goals, its suggestions fit your actual situation.
Task Tracking
Built-in commands scan your files for tasks due today, creating automatic daily agendas.
The Folder Structure
Your Personal OS uses a numbered folder system based on the PARA method (Projects, Areas, Resources, Archives). The numbers keep things sorted in a logical order.
Personal_OS/ │ ├── 00_Inbox/ # Daily agendas and quick captures │ ├── 10_Projects/ # Active work with deadlines │ ├── 20_Areas/ # Ongoing responsibilities (no deadline) │ ├── 30_Resources/ # Reference materials, templates │ ├── 40_Archives/ # Completed or inactive items │ ├── 99_System/ # Configuration, profiles, scripts │ │ │ ├── Context_Library/ │ │ ├── business_profile.md │ │ ├── personal_profile.md │ │ └── project_specs/ │ │ │ ├── Profiles/ │ │ ├── writing_profile.md │ │ └── coding_profile.md │ │ │ └── Scripts/ │ └── task_scanner.py │ └── CLAUDE.md # The brain - Claude reads this first
The CLAUDE.md File
This is the most important file in your system. Claude reads it automatically when you start working in this folder. It tells Claude who it is in your world and how to behave.
## Role Chief of Staff for Personal Operating System. Manage tasks, organize information, facilitate research with precision and low friction. ## Architecture - Root: Obsidian Vault - Tasks: Markdown files in `10_Projects/` and `00_Inbox/` - Archive: Never search/modify `40_Archives/` unless explicitly asked ## Behavioral Guidelines 1. Read local files before asking for context 2. Concise, actionable responses - no lectures 3. Confirm before deleting; edit freely if aligned with request 4. Today is {{DATE}} - calculate relative dates accordingly ## Context & Profiles Profiles and project specs live in `99_System/`. Load only when explicitly requested: - "Writing Mode" → `Profiles/writing_profile.md` - "Coding Mode" → `Profiles/coding_profile.md` - Project work → relevant spec in `Context_Library/project_specs/` Do NOT preload profiles based on inferred task type.
Nested CLAUDE.md Files
Here's where it gets powerful: you can put CLAUDE.md files inside specific project folders too. Claude reads them hierarchically, from the root down to wherever you're working.
Personal_OS/ │ ├── CLAUDE.md # Global instructions │ └── 10_Projects/ │ └── My_Website_Redesign/ │ ├── CLAUDE.md # Project-specific instructions ├── process_notes.md # Session history └── Website_Redesign.md # Project details
The project-level CLAUDE.md might say things like:
- This is a React project - use TypeScript
- The client prefers minimalist design
- Always run tests before suggesting we're done
- Design files are in Figma at [link]
Process Notes: Your Project Memory
Each project can have a process_notes.md file that tracks what happened in each work session. This is how Claude remembers what you did yesterday, what decisions you made, and what's still pending.
# Process Notes: Website Redesign Session logs documenting decisions, progress, and context. --- ## 2026-01-23 - Homepage Layout Summary: Finalized hero section design and implemented mobile responsive layout. Changes: - Updated Header.tsx with new navigation - Created HeroSection component - Added mobile breakpoints to global CSS Decisions: - Using CSS Grid instead of Flexbox for main layout - Client approved blue color palette Open: - [ ] Add animation to hero section - [ ] Get client feedback on footer design
Obsidian + VS Code: How They Work Together
These two tools serve different purposes in your workflow:
Your Daily Workflow
Obsidian = Viewing & Navigating
Use Obsidian to browse your notes, read project files, check your daily agenda, and navigate between linked documents. It's your "reading" interface.
VS Code + Claude = Working & Creating
Use VS Code when you want Claude's help. This is where you run slash commands, ask Claude to write or edit files, create new projects, and do actual work.
Both Open at Once
Keep both apps open. Changes sync instantly because they're reading the same files on your computer.
Why Obsidian?
Obsidian is a free app for writing and organizing notes. It works with plain text files (Markdown) stored on your computer. Here's why it's perfect for a Personal OS:
Your Files, Your Computer
Unlike Notion or Google Docs, your notes are just files on your hard drive. No internet required. You own them forever.
Complete Privacy
Your notes never leave your computer unless you choose to share them. No cloud sync required. No company reading your data.
Plain Text = Future-Proof
Markdown files work everywhere. If Obsidian disappears tomorrow, your files still open in any text editor.
Linking & Backlinks
Connect ideas across notes. See which notes link to each other. Build a web of your knowledge.
Don't want to use Obsidian?
That's fine! The Personal OS works with any folder of Markdown files. You can use Typora, iA Writer, or any Markdown editor you prefer for viewing. VS Code is still recommended for working with Claude.
The Slash Commands
Slash commands are shortcuts that trigger specific workflows. Here are two essential ones:
/today Daily Agenda Generator
This command scans all your project folders for tasks with due dates, checks what's overdue, and creates a daily agenda file in your Inbox.
What it does:
- Scans all markdown files for tasks with due dates
- Groups them by: Overdue, Due Today, Due This Week, Due Next Week
- Creates a new file like
2026-01-25_Agenda.md - Includes sections for daily focus, notes, and someday/maybe items
How to use: Just type /today in VS Code when starting your work day.
/log Session Logger
When you finish a work session, this command summarizes what you accomplished and appends it to your project's process_notes.md file.
What it does:
- Identifies which project you're working in
- Creates a summary of the session (changes, decisions, open items)
- Appends it to process_notes.md with today's date
- Automatically compacts old entries to keep the file lean
How to use: Type /log in VS Code at the end of a work session.
Setup Instructions
Good news: Claude will do most of the setup work for you. You just need to install the tools and paste a few prompts.
Install VS Code
Download VS Code from code.visualstudio.com and run the installer. Default settings are fine.
Install the Claude Extension
Open VS Code. Click the Extensions icon in the left sidebar (looks like four squares), or press Cmd+Shift+X (Mac) or Ctrl+Shift+X (Windows).
Search for "Claude" and install the official extension by Anthropic. Sign in with your Claude account when prompted.
Create Your Personal_OS Folder
Create one empty folder on your computer. This is the only thing you need to do manually.
On Mac:
Open Finder → Go to Documents → Right-click → New Folder → Name it Personal_OS
On Windows:
Open File Explorer → Go to Documents → Right-click → New → Folder → Name it Personal_OS
Open the Folder in VS Code
In VS Code: File → Open Folder → Navigate to Documents → Select your Personal_OS folder → Click "Open"
If VS Code asks "Do you trust the authors?", click "Yes, I trust the authors"
Have Claude Build Your System
Open the Claude panel in VS Code (click the Claude icon in the sidebar or press Cmd/Ctrl+Shift+P and search for "Claude"). Then paste this prompt:
Copy and paste this into Claude:
Please set up a Personal OS folder structure for me. Create: 1. These folders: - 00_Inbox - 10_Projects - 20_Areas - 30_Resources - 40_Archives - 99_System - 99_System/Context_Library - 99_System/Context_Library/project_specs - 99_System/Profiles - 99_System/Scripts 2. A CLAUDE.md file in the root with this content: ## Role Personal assistant for [my name]. Help me manage tasks, organize information, and stay productive. ## Architecture - Tasks: Markdown files in `10_Projects/` and `00_Inbox/` - Archive: Never modify `40_Archives/` unless asked ## Guidelines 1. Read local files before asking for context 2. Be concise - no unnecessary explanations 3. Ask before deleting anything 3. A Someday_Maybe.md file in 20_Areas with sections for Ideas, Long-Term Projects, Things to Explore, and Wishlist. Please create all of these now.
Claude will create all the folders and files for you. When it's done, you'll see the structure appear in VS Code's file explorer on the left.
Set Up the Slash Commands
The /today and /log commands need to be installed in a special folder. Paste this prompt into Claude:
Copy and paste this into Claude:
Please create the /today and /log slash commands for me. Create these files: 1. ~/.claude/skills/today/SKILL.md with this content: --- name: today description: Scans the vault for tasks due today and creates a daily agenda. allowed-tools: Bash(*), Read(*), Write(*) --- # /today Command Create a daily agenda by scanning for tasks with due dates. ## What to Do 1. Search all .md files in 10_Projects/ and 00_Inbox/ for YAML frontmatter containing "due_date" fields 2. Group tasks by: - Overdue (due_date before today) - Due Today - Due This Week - Due Next Week 3. Create a new file in 00_Inbox/ named YYYY-MM-DD_Agenda.md with today's date 4. Format the agenda with sections for each group, plus: - Daily Focus (leave blank for user to fill) - Quick Notes (leave blank) 5. Tell the user: "Good morning! I've prepared your agenda: [filename]" 2. ~/.claude/skills/log/SKILL.md with this content: --- name: log description: Log session notes to project's process_notes.md allowed-tools: Glob(*), Read(*), Write(*), Edit(*) --- # /log - Session Logger Log the current session to the project's process_notes.md file. ## What to Do 1. Identify which project folder we're working in 2. Find or create process_notes.md in that folder 3. Generate a session entry with this structure: ## YYYY-MM-DD - [Brief Title] **Summary:** 1-2 sentences max. **Changes:** Bullet list of files modified. **Decisions:** Only if meaningful choices were made. **Open:** Remaining tasks (use - [ ] format). 4. Append the entry at the end of the file 5. Tell the user: "Entry added for [date]" Please create both of these skill files now.
Install Obsidian
Download Obsidian from obsidian.md and install it.
When Obsidian opens, click "Open folder as vault" and select your Personal_OS folder.
You'll see your new folder structure in the left sidebar. This is where you'll browse and read your notes.
Test It!
Go back to VS Code and type /today in the Claude chat. Claude should create your first daily agenda file. Check Obsidian - you'll see it appear in your 00_Inbox folder.
Adding Your First Project
Want to add a project? Just tell Claude:
Example prompt:
Create a new project called "Q1 Marketing Plan" with a due date of March 15. Include a project file, process_notes.md, and a few starter tasks.
Claude will create the folder structure, files, and properly formatted tasks that /today can find.
Task Format (For Reference)
When Claude creates tasks, it uses this format. You don't need to memorize this - just ask Claude to create tasks for you:
--- type: task status: todo created: 2026-01-20 due_date: 2026-01-25 priority: high tags: [] --- # Task Title Description of what needs to be done...
due_date field to build your agenda.Tips for Success
- Let Claude do the work. Instead of manually creating files, just tell Claude what you want. "Create a new task for reviewing the budget by Friday" is all you need.
- Use the Inbox. When you're not sure where something goes, tell Claude to put it in 00_Inbox. You can organize it later.
- Run /log regularly. The more you log, the better your process notes become, and the more context Claude has for future sessions.
- Keep Obsidian open. Use it to browse and read your notes while VS Code + Claude handles the editing.
- Archive liberally. When a project is done, tell Claude to move it to 40_Archives. Keep your active spaces clean.
- Ask for help. If you're stuck, just ask Claude! "How should I organize my consulting projects?" or "Create a template for client kickoff meetings."
Ready to Get Started?
Your Personal OS will grow with you. Start with the basics, and add more as you need it. The productivity gains compound over time as Claude learns your work patterns and preferences.
Explore More at Agents of Change