| name | para |
| description | PARA method for organizing content by actionability (Projects, Areas, Resources, Archive). Use when organizing files, categorizing notes, deciding Projects vs Areas vs Resources, managing folders, or maintaining your knowledge structure. |
<essential_principles>
PARA: Organize by Actionability, Not Topic
PARA organizes information by when you'll need it:
| Category | Definition | Key Signal |
|---|
| Projects | Active work with deadlines | "Complete", "deliver", "launch" |
| Areas | Ongoing responsibilities, no end date | "Maintain", "manage", "track" |
| Resources | Reference material for future use | "Interesting", "might need" |
| Archive | Inactive items from above categories | "Done", "paused", "no longer relevant" |
Example: A Kubernetes article goes in Projects if deploying now, Areas if maintaining systems, Resources if just learning.
Folder Structure
1_Projects/ # Active work with deadlines
├── _INDEX.md # Project overview
└── [Project-Name]/ # One folder per project
2_Areas/ # Ongoing responsibilities
├── _INDEX.md # Area overview
└── [area-name].md # One file per area (or folder if complex)
3_Resources/ # Reference material
├── _INDEX.md # Resource overview
└── [topic]/ # Topic-based resources
4_Archive/ # Inactive items
├── _INDEX.md # Archive overview
└── [archived items] # Completed/inactive content
</essential_principles>
<initialization_check>
IMPORTANT: Before showing the intake menu, run this check.
What would you like to do?
