The /inbox workflow automatically categorizes incoming files from the _inbox/ directory into their permanent locations within the PARA structure. It acts as a smart file router.
Commands Overview
/inbox # Review and categorize all files in _inbox/
/inbox [filename] # Categorize a specific fileCategorization Flow
Scan inbox → Classify file type → Check project context → Move to target → Report1. Scan Inbox
Lists all files currently in _inbox/ for processing.
2. Categorization Logic
The agent classifies files based on type and content indicators:
| Category | Indicators | Target Directory |
|---|---|---|
| Code Templates | .tsx, .jsx, .vue | Resources/references/code/components/ |
| Logic Snippets | .ts, .js, .py | Resources/references/code/snippets/ |
| Design Patterns | .md regarding design | Resources/references/code/patterns/ |
| Integrations | API/Webhook code | Resources/references/code/integrations/ |
| Research/Tutorials | .md how-to guides | Resources/references/articles/tutorials/ |
| Project Assets | [p]-logo.png, .csv | Projects/[name]/artifacts/assets/ |
| Learning | Notes, best practices | Areas/Learning/ |
2.5. Project Context Check
Before moving files to any project directory, the agent reads the project’s existing structure first.
If the target is a Projects/[name]/ directory:
- Reads the project’s
docs/README.mdto understand layout - Lists top-level folder structure
- Matches the file to an existing folder — does NOT create new directories without confirmation
3. Move File
- Duplicate check — If target file exists, appends
_YYYYMMDDtimestamp - Directory creation — Ensures target directory exists (known paths only)
- Move and report — Moves the file and confirms the action
Notes
- Large files (>10MB): Asks for confirmation before moving
- Unidentified files: Stays in
_inbox/— agent asks for clarification - Files moved to
Projects/must match an active project
→ Workflow /learn — Package lessons into Areas/Learning → Workflow /para — Master workspace controller