Design a PARA Folder and Tag Structure for Your Personal Knowledge System
Get a ready-to-build PARA folder tree, one file naming convention, a short tag list with rules, and a 10-minute weekly upkeep routine for your tools.
You getFolder tree, naming convention with examples and tag table
Prompt
Act as a personal knowledge management coach who sets up PARA systems (Projects, Areas, Resources, Archive) for busy people.
Before building anything, ask me these questions in one message and wait for my answers:
1. Which note and file tools do I use (e.g. Notion, Obsidian, Google Drive, Apple Notes)?
2. What active projects do I have, each with a goal or deadline?
3. What ongoing areas of responsibility do I manage (work roles, health, home, money)?
4. What topics do I save reference material on?
Then design my system with these rules:
- Every project folder name includes an outcome and an end month; anything without an end date goes in Areas.
- Number the top-level folders so they sort in order, and go no deeper than 3 levels.
- Give one naming convention for files and notes, with 3 examples drawn from my answers.
- Use at most 10 tags, each with a one-line rule for when to apply it; no tag repeats a folder name.
- The weekly routine fits in 10 minutes, with minutes assigned to each step.
Output format:
1. Folder tree (in a code block)
2. Naming convention with examples
3. Tag table: Tag | Use when | Example
4. 10-minute weekly routine (numbered steps with minutes)
5. First 3 moves to migrate my existing notes
End with one line naming any assumption you made about my tools or the biggest risk of the system drifting.Example output
Tips and common edits
Why this works
- Asking about tools and projects first means the folder tree uses your real project names instead of generic examples.
- Forcing an end month in every project name enforces the core PARA rule that separates Projects from Areas.
- Capping tags at 10 with a usage rule each prevents the tag sprawl that makes most systems collapse.
Use when your notes and files are scattered across apps. Paste into ChatGPT, Claude or Gemini and have a quick list of your tools, current projects and recurring responsibilities ready.
Common edits
- Ask for a version that works only in Notion, using databases and properties instead of folders.
- Change the weekly routine to a 30-minute monthly review if you prefer fewer, longer sessions.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Turn an Article or Book Chapter into Atomic Zettelkasten Notes
Paste any article or chapter and get 5-12 one-claim permanent notes in your own words, with IDs, reasoned links, a link map and open questions.
Turn Lecture or Reading Notes into Cornell Notes with Cue Questions
Paste your raw notes and get a Cornell-style table with one cue question per main idea, a 3-sentence summary, a self-test list and a note on gaps.
Build a 30-Day Learning Plan for a New Skill with Weekly Project Milestones
You get a 30-day plan sized to your daily time, with one small, checkable project each week, day-by-day tasks with minutes, and a catch-up plan.
Build a Timed Meeting Agenda with Owners, Decision Labels and Pre-Reads
Get a timed agenda where every item has a Decide, Discuss or Inform label, an owner and minutes that fit the slot, plus pre-reads and a list of items to handle async.
Prepare a Constructive Feedback Conversation with a Teammate Using SBI
Get a ready-to-say feedback script with an opening line, a situation-behavior-impact statement, one clear request, and calm replies to defensive reactions.
Replace Your Weekly Status Meeting with an Async Written Check-In
Get a reusable async check-in with a posting schedule, response deadline, short questions, a sample answer and clear rules for when a live call is still needed.