para-add

/para-add

Add a new item to any PARA category with the appropriate template.

Usage

/para-add <category> <name>

• <category> — one of: projects, areas, resources (case-insensitive)
• <name> — kebab-case name for the item (e.g., website-redesign, book-notes)

Examples:

/para-add projects website-redesign
/para-add areas health-fitness
/para-add resources python-notes

Steps

1. Find the PARA root. Look for .para-config.json in common locations:

   • Current working directory
   • ~/para/
   • Walk up from current directory

   If not found, tell the user to run /para-setup first.

2. Validate the category. Must be one of Projects, Areas, Resources. Normalize to title case for the directory name. If the user tries to add to Archive, explain that Archive is for moved items and suggest the right category.

3. Normalize the name. Convert to lowercase-kebab-case if not already.

4. Check if item already exists. If {PARA_ROOT}/{Category}/{name}/ exists, warn the user and ask if they want to overwrite.

5. Create the item directory structure:

   {Category}/{name}/
   ├── context.md
   ├── notes/
   │   └── log.md
   └── assets/
   

6. Use the right template from skills/para-system/references/templates.md:

   • Projects → Project Template (replace {PROJECT_NAME} with the item name, title-cased)
   • Areas → Area Template (replace {AREA_NAME} with the item name, title-cased)
   • Resources → Resource Template (replace {RESOURCE_NAME} with the item name, title-cased)

7. Create notes/log.md using the Log Template. Replace {TODAY} with today's date.

8. Replace all {TODAY} placeholders with today's date in YYYY-MM-DD format.

9. Create assets/ directory using Bash(mkdir -p).

10. Show confirmation with the path to the new item and suggest the user fill in context.md.

If Arguments Are Missing

• No category: Ask "Which category? Projects, Areas, or Resources?"
• No name: Ask "What would you like to call this item?" and suggest kebab-case format.
• Both missing: Ask both questions.