Skip to content

PARA Structure

Create 5-folder vault with Projects, Areas, Resources, Archives

Build your PARA structure
/CC.m1.lb2
  • Explain the PARA methodology and distinguish between its four containers (Projects, Areas, Resources, Archives) plus Inbox
  • Create a complete 5-folder knowledge vault structure using Claude Code
  • Apply the Inbox workflow to process items into their correct PARA locations
ConceptDescription
PARA MethodologyAn organisational system that groups information by actionability rather than topic or category
InboxYour capture point for new items that have not been processed yet
ProjectsActive work with a clear end date and specific deliverables
AreasOngoing responsibilities you maintain indefinitely without completion dates
ResourcesReference materials like templates, research, and guides you might need in future
ArchivesInactive items from completed projects or outdated resources you may need to reference later
ActionabilityThe principle of organising by what you are doing with something, not what topic it belongs to
README FilesDocumentation in each folder explaining what belongs there, serving as signposts for yourself and others
  • knowledge-vault/ - 5-folder structure with READMEs

“Oh! Projects end, but Areas are forever. That’s why I kept getting confused - I was treating my ongoing responsibilities like projects that never finished. PARA separates them because they need different kinds of attention.”


Navigation: Lab 1: First Conversation | Module Overview | Lab 3: Folder Architectures