Skill

subfolders

Creates new Tandem project or context folders with CLAUDE.md and MEMORY.md configured from templates. Trigger on: "create a folder", "new project", "set up a workspace for", "start a project for [client]", "make a folder for", "new workspace", "create a space for", "organize [X] in its own folder", "client folder for [name]", "project folder". Do NOT use for creating folders outside ~/Tandem/, file system operations on desktop/Dropbox/cloud storage, project creation in external tools (VSCode, Notion, Monday.com), or simple file organization not requiring a workspace.

From tandem

Install

Run in your terminal

npx claudepluginhub binatrixai/tandem-marketplace --plugin tandem

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBashGlob

Supporting Assets

View in Repository

evals/evals.json

examples/sample-structures.md

references/proactivity-mapping.md

references/template.md

template.md

Skill Content

Similar Skills

executing-plans

Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.

superpowers

134.2k

brainstorming

7 files

Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.

superpowers

134.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

134.2k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 5, 2026

Actions

View Source View Plugin View on GitHub View README

Subfolder Creation

Create organized project and context folders with pre-configured CLAUDE.md and MEMORY.md files, ready for focused work.

Language

See METHODOLOGY.md language mirror rule. Reply in the user's language. Generated CLAUDE.md content adapts to user's language; structural headers stay in English.

Procedure

Step 1: Ask Folder Name

What would you like to call this workspace?

AskUserQuestion:
  - "Let me type a name"

If the user provides a name, normalize it:

Lowercase
Replace spaces with hyphens
Remove special characters
Example: "Acme Corp Project" -> acme-corp-project

Confirm the normalized name:

I'll create a folder called `acme-corp-project`. Sound good?

AskUserQuestion:
  - "Yes, create it"
  - "Let me change the name"

Step 2: Ask Parent Location

Where should this folder live?

AskUserQuestion:
  - "projects/ (client or project workspace)"
  - "email/ (email-related)"
  - "documents/ (document workspace)"
  - "research/ (research workspace)"
  - "tasks/ (task management)"
  - "Root (~/Tandem/)"
  - "Custom location"

Default to projects/ if the user mentioned a client or project name.

Step 3: Ask Purpose

What's the main purpose of this workspace? This helps me configure the right
proactivity triggers and behavior.

AskUserQuestion:
  - "Client project (deliverables, meetings, communication)"
  - "Internal project (planning, tracking, documentation)"
  - "Event planning (logistics, vendors, timeline)"
  - "Research initiative (investigation, analysis, reporting)"
  - "Custom — let me describe it"

Step 4: Memory Isolation Check

Should this workspace inherit memory from the parent folder, or start fresh?

AskUserQuestion:
  - "Start fresh (clean MEMORY.md)"
  - "Copy relevant entries from parent"
  - "Link to parent memory (read but don't copy)"

Start fresh: Create empty MEMORY.md with category headers only. Copy relevant: Read parent MEMORY.md, let user pick entries to carry over. Link to parent: Add a note in CLAUDE.md to reference parent MEMORY.md for global context.

Step 5: Generate Files and Structure

Create the folder with the following structure:

[folder-name]/
├── CLAUDE.md          ← From template, customized with name, purpose, proactivity triggers
├── MEMORY.md          ← With four category headers, either empty or with copied entries
├── documents/         ← For deliverables, reports, spreadsheets
├── examples/          ← For style/format examples the assistant can learn from
│   └── README.md      ← Brief explanation of what to put here
└── references/        ← For reference materials, source documents, specifications

CLAUDE.md — From template, customized with folder name, purpose, and context-specific proactivity triggers. Include a "Skill Invocation Rules" section and "File Placement Rules" section appropriate to the folder's purpose.
MEMORY.md — With four category headers, either empty or with copied entries
documents/ — Empty directory for project deliverables
examples/README.md — Brief note: "Place example files here so your assistant can learn your preferred style and formatting for this project."
references/ — Empty directory for source/reference materials

See template.md for the file templates.

Step 6: Confirm Creation

Created workspace: [parent]/[folder-name]/

Structure:
  - CLAUDE.md (configured for [purpose])
  - MEMORY.md (4 categories, [empty / N entries copied])
  - documents/ (for deliverables)
  - examples/ (for style references)
  - references/ (for source materials)

AskUserQuestion:
  - "Open this workspace"
  - "Create another folder"
  - "Done"

Naming Conventions

Input	Normalized
Acme Corp Project	`acme-corp-project`
Q2 Marketing	`q2-marketing`
Sarah's Onboarding	`sarahs-onboarding`
Event - Annual Conf 2026	`event-annual-conf-2026`
דוח רבעוני	`quarterly-report` (transliterate or translate)

Rules:

Always lowercase
Hyphens instead of spaces
No special characters except hyphens
Hebrew/Russian names: offer to transliterate or translate to English for folder name
Keep it short but descriptive (2-4 words)

Purpose-to-Proactivity Mapping

The purpose selected in Step 3 determines which proactivity triggers are added to the generated CLAUDE.md:

Client Project

After meeting notes: offer to update project status
After email about this client: offer to save key decisions
After deliverable creation: offer to track in task list
Periodically: offer to create status update for client

Internal Project

After task completion: offer to update project board
After decision: offer to save to project memory
After document creation: offer to share with stakeholders
Periodically: offer weekly project review

Event Planning

After vendor communication: offer to update vendor list
After budget update: offer to check remaining budget
After timeline change: offer to notify affected parties
As event approaches: increase check-in frequency

Research Initiative

After research session: offer to update findings document
After source discovery: offer to save to references
After analysis: offer to create interim report
When enough data gathered: offer to create final report

Template Reference

The full CLAUDE.md and MEMORY.md templates are in template.md. Sample folder structures with generated content are in examples/sample-structures.md.

Proactivity Integration

After folder creation:

AskUserQuestion:
  - "Start working in the new folder"
  - "Create another workspace"
  - "Done for now"

When the proactivity engine detects a new client/project mention:

You mentioned "[name]" — I don't see a workspace for that yet.

AskUserQuestion:
  - "Create a workspace for [name]"
  - "No need, it's a one-off"

Error Handling

Folder already exists: Inform user, offer to open it or pick a different name
Parent doesn't exist: Create parent first, then the subfolder
Invalid name: Show the normalized version and confirm
Template missing: Use inline defaults (minimal CLAUDE.md + MEMORY.md with headers)