CyrilXBT — Most productivity systems fail because they are too complex to maintain and too scattered to navigat…
Most productivity systems fail because they are too complex to maintain and too scattered to navigate.
You have tasks in one app. Projects in another. Notes in a third. Calendar in a fourth. Reference material in a fifth.
You are not managing your life. You are managing the infrastructure that is supposed to manage your life.
The one-folder Obsidian system solves this at the root level.
Not by simplifying what you track.
By unifying where everything lives.
One folder. One system. Everything that runs your life accessible from a single place with a single tool connected to a single intelligence layer.
This guide is the complete build.
The Philosophy Behind One Folder
Before the architecture understand the principle.
The one-folder system is not about minimalism for its own sake.
It is about cognitive load.
Every folder hierarchy you create is a decision you have to make every time you capture something. Where does this go? Which subfolder? Which level of nesting?
That decision costs attention. Attention is the scarcest resource in knowledge work.
The one-folder system eliminates the filing decision entirely.
Everything goes in one folder. Claude Code connected via MCP handles the organization automatically. You capture at the speed of thought and the system files at the speed of automation.
The apparent chaos of one folder becomes invisible because the intelligence layer makes everything findable, organized, and actionable without you manually maintaining the structure.
What One Folder Actually Means
The one-folder system does not mean one note.
It means one root location that contains everything. No hierarchy you have to navigate. No nested folders you have to remember. No taxonomy you have to maintain.
Your vault has one folder called LIFE.
Inside LIFE everything is a flat file with a consistent naming convention and a consistent properties structure.
Claude Code reads every file in LIFE when you ask it anything. It understands what is a project, what is a task, what is a reference, and what is a daily note by reading the type property in each file’s frontmatter.
You never navigate folders.
You ask Claude what you need.
Claude reads the flat file structure and gives you exactly what you asked for.
The File Naming Convention
When everything lives in one folder, naming becomes the organizational system.
Every file follows this exact convention:
YYYY-MM-DD-[TYPE]-[TOPIC].md
Examples:
2026-05-20-daily-wednesday.md 2026-05-18-project-website-rebrand.md 2026-05-15-task-client-proposal.md 2026-05-10-reference-claude-prompting.md 2026-05-01-meeting-q2-planning.md 2026-04-28-idea-newsletter-series.md 2026-04-20-decision-hire-contractor.md
The date prefix means every file sorts chronologically automatically. The type identifier means Claude can filter by type instantly. The topic identifier means you can search by keyword and find files without navigating.
This convention handles everything a folder hierarchy used to handle without requiring you to make any filing decisions.
The Properties Structure
Every file regardless of type has a properties block at the top.
The properties block is what the system reads to understand each file. It is what makes Claude’s organization intelligent rather than generic.
The Universal Properties Block:
type: [daily/project/task/reference/meeting/idea/decision] date: 2026-05-20 status: [active/complete/archived/pending] tags: [topic1, topic2] priority: [high/medium/low]
Additional Properties by Type:
For projects:
client: [CLIENT NAME] deadline: 2026-06-15 completion: 40 next_action: Write the campaign brief
For tasks:
project: [PROJECT NAME] due: 2026-05-22 energy: [deep/shallow/admin]
For meetings:
attendees: [names] decisions: [key decisions made] actions: [specific follow-ups]
For decisions:
chosen: [what you decided] reasoning: [why] review_date: 2026-08-20
The properties block takes 30 seconds to fill when you create a file. It is what makes the entire intelligence layer work.
The CLAUDE.md That Powers Everything
The CLAUDE.md lives in the root of your vault alongside the LIFE folder.
It is the constitution of your entire system. Every automated workflow reads it first.
One-Folder Life System — CLAUDE.md
Who I Am
Name: [YOUR NAME] Primary focus: [YOUR MAIN PROFESSIONAL FOCUS] Location: [YOUR CITY AND TIMEZONE]
My Life Areas
Work: [BRIEF DESCRIPTION OF YOUR WORK SITUATION] Health: [CURRENT HEALTH FOCUS AND STATUS] Finances: [CURRENT FINANCIAL SITUATION AND GOALS] Relationships: [KEY RELATIONSHIPS TO MAINTAIN] Learning: [WHAT YOU ARE CURRENTLY STUDYING] Personal: [PERSONAL GOALS AND PROJECTS]
Active Projects
[PROJECT NAME]: [ONE-SENTENCE STATUS] | Deadline: [DATE] | Next: [SPECIFIC ACTION] [Repeat for each active project]
Current Top 3 Priorities
- [MOST IMPORTANT RIGHT NOW]
- [SECOND MOST IMPORTANT]
- [THIRD MOST IMPORTANT]
My File System
Everything lives in the LIFE folder as flat files. Naming convention: YYYY-MM-DD-[TYPE]-[TOPIC].md Type values: daily, project, task, reference, meeting, idea, decision
How to Navigate My System
To find active projects: filter type=project AND status=active To find today’s tasks: filter type=task AND due=today To find open decisions: filter type=decision AND status=pending To find recent ideas: filter type=idea, sort by date DESC
Quality Standards
[WHAT GOOD WORK LOOKS LIKE FOR YOU]
Operating Rules
- All outputs save to LIFE folder with correct naming convention
- Never delete files, add status=archived to outdated ones
- Always read this CLAUDE.md before any task
- Log significant actions in LIFE/YYYY-MM-DD-log-operations.md
- Update Current Top 3 Priorities every Monday
This Week’s Focus
[UPDATE EVERY MONDAY]
The Five Commands That Run Your Life
With the one-folder system in place five commands handle everything your life requires.
You do not need complex workflows. You do not need to navigate any structure. You type one command and the system executes.
Command 1: Morning
/morning
This is your daily briefing command.
Claude reads your CLAUDE.md, scans every file in LIFE created or modified in the last 48 hours, reads your current week’s daily notes, and generates a morning briefing.
The skill file that powers it:
/morning
What this does
Generates a complete morning briefing from the LIFE folder.
Process
- Read CLAUDE.md for full life context
- Read today’s date
- Find all task files with due=today or due<today and status=active
- Find all project files with status=active, read their next_action property
- Find yesterday’s daily note, extract any OPEN: items
- Check for any meeting files dated today
Output Format
MOST IMPORTANT TODAY: [single highest-leverage action] DUE TODAY: [task list with priorities] PROJECT PULSE: [one line per active project with next action] MEETINGS: [any meetings today with prep note] OPEN LOOPS: [unfinished items from yesterday] ONE DECISION: [most important pending decision]
Save to
LIFE/[DATE]-briefing-morning.md
You open your laptop. You type /morning. You read the output. You know what matters before you see a single notification.
Command 2: Capture
/capture [anything]
This is your universal input command.
You type /capture followed by whatever you want to record. Idea. Task. Note. Decision. Reference. Anything.
The skill file:
/capture
What this does
Takes any input and creates the correct file type in the LIFE folder.
Process
- Read the capture input
- Identify the type:
- Action required → task
- Something to develop → idea
- Time-bound → meeting
- Needs a choice → decision
- For later reference → reference
- Context about active work → note in project file
- Generate the correct filename
- Create the file with appropriate properties
- If it is a task: extract due date if mentioned, assign priority based on context
- If it is an idea: tag with relevant areas from CLAUDE.md
Output
Confirm: “Captured as [TYPE]: [FILENAME]”
You capture at the speed of thought. The system handles the rest. Nothing gets lost because you did not know where to file it.
Command 3: Review
/review
This is your weekly review command. Run it every Sunday evening.
The skill file:
/review
What this does
Generates the weekly review from everything in LIFE.
Process
- Read all daily notes from the past 7 days
- Read all project files modified this week
- Read all task files completed this week
- Read all decision files created this week
- Read CLAUDE.md for context
Output Format
WINS THIS WEEK: [specific achievements with evidence] WHAT STALLED: [honest assessment with reasons] PATTERN: [one theme from the week] NEXT WEEK’S TOP 3: [priorities ranked by leverage] OPEN DECISIONS: [any pending decisions older than 7 days] ONE INSIGHT: [something the week revealed worth recording]
After generating
Update CLAUDE.md Current Top 3 Priorities with next week’s priorities Save to LIFE/[DATE]-review-weekly.md
The weekly review used to take 45 minutes of manually reading notes and trying to remember what happened.
Now it takes 10 minutes to read what the system generated and 3 minutes to add anything it missed.
Command 4: Find
/find [what you need]
This is your search command. But not a keyword search. An intelligent search.
The skill file:
/find
What this does
Finds anything in your LIFE folder using natural language and reasoning.
Process
- Read the search request
- Identify what type of information is being sought
- Search LIFE folder using relevant filters:
- By type property
- By date range if mentioned
- By tags if relevant
- By status if mentioned
- By keyword in content
- Return results with context, not just filenames
Examples
“find all open decisions from this quarter” → filter type=decision, status=pending, date >= 2026-04-01
“what did I decide about the contractor hire” → search type=decision, topic contains “contractor”
“all ideas tagged learning” → filter type=idea, tags contains “learning”
Output
List of relevant files with:
- Filename
- Key content summary
- Relevant properties
- Direct link
You never navigate your vault looking for something. You ask Claude where it is and Claude finds it.
Command 5: Plan
/plan [project or goal]
This is your planning command. Give it any project or goal and it creates a complete plan in your LIFE folder.
The skill file:
/plan
What this does
Creates a complete project plan in the LIFE folder for any project or goal.
Process
- Read the project or goal description
- Read CLAUDE.md for current context and commitments
- Break the project into phases
- For each phase: identify specific tasks with realistic deadlines
- Create one project file with full overview
- Create individual task files for each task
- Identify dependencies between tasks
- Flag any conflicts with existing commitments
Project File Output
Complete overview with:
- Project description and goal
- Success criteria
- Phase breakdown
- Timeline
- Next action
Task Files
One file per task with:
- Clear deliverable
- Realistic due date based on current commitments
- Energy requirement
- Dependencies
You describe what you want to accomplish. The system creates the project file, the task files, and a realistic timeline based on your current commitments.
The Automation Layer
The five commands handle everything you initiate.
The automation layer handles everything that should happen without you initiating it.
Three automated workflows make the one-folder system self-maintaining.
The Daily Capture Processor
Every evening at 8PM N8N triggers a Claude workflow that processes the day’s captures.
It reads every file created in LIFE today. For any file with incomplete properties it fills in the gaps based on the content. For any task without a due date it assigns one based on context and your current workload. For any file that needs to be linked to an existing project it adds the project property.
The daily captures process themselves. You never have to clean up after a day of fast captures.
The Stale File Monitor
Every Monday at 7AM N8N triggers a workflow that scans LIFE for stale files.
Projects with no activity in 14 days get flagged. Tasks overdue by more than 7 days get surfaced. Decisions pending for more than 30 days get escalated. Ideas older than 90 days get reviewed for archiving.
The Monday stale file report appears in your LIFE folder as a briefing file. You read it alongside your morning briefing.
The Monthly Life Review
On the first day of every month N8N triggers a comprehensive life review workflow.
It reads all activity from the previous month across every file type. It generates a monthly summary covering wins, patterns, decisions made, projects advanced, and goals progressed. It identifies any life areas that received no attention in the previous month.
The monthly review compounds into your weekly reviews. Over 12 months you have a documented record of exactly how your life and work evolved.
Living in the System Day to Day
The daily experience of the one-folder system is radically simpler than any multi-folder alternative.
Morning: Type /morning. Read the briefing. Know what matters before anything else competes for your attention.
During the day: Type /capture [anything] for every thought, task, idea, or piece of information. Never make a filing decision. Never interrupt your flow to organize.
As things come up: Type /find [what you need] when you need to retrieve anything. Never navigate folders.
When starting new work: Type /plan [project or goal] and receive a complete plan in your vault.
Sunday evening: Type /review. Read the weekly summary. Update your Monday priorities.
Five commands. One folder. Everything runs.
Why One Folder Does Not Become Chaos
The objection most people raise: without folders, how do you find anything?
The answer reveals the core insight of the entire system.
Folders are a human navigation aid for systems without intelligence.
When you have to browse to find things, folders tell you where to browse.
When you have Claude reading every file and responding to natural language queries, folders are unnecessary overhead.
You do not browse.
You ask.
The system answers.
The intelligence layer makes the flat structure more navigable than any folder hierarchy because it understands what you are looking for rather than requiring you to remember where you put it.
After 30 days the LIFE folder will contain 100 to 200 files.
After 6 months it will contain 1,000 to 2,000 files.
After 2 years it will contain 5,000 to 10,000 files.
At every stage Claude can find anything in under 10 seconds because it reads properties and content rather than navigating a structure.
The flat folder does not become chaos.
It becomes a searchable, queryable, intelligent database of your entire life.
One folder. One system. Everything that matters.
Build it this weekend.
The commands run from the first day.
The intelligence compounds from the first week.
The life clarity compounds from the first month.
Follow @cyrilXBT for the exact CLAUDE.md templates, skill files, and N8N workflows that make this entire system run.