manastalukdar Procedure for Organizing Claude Session Directories:
- Analyze the Project
- Perform a thorough analysis of the project's codebase and overall architecture to understand its components.
- Define the Directory Structure
- Based on your analysis, create a flat or hierarchical list of the project's key features and product areas. This list will serve as the blueprint for your session directory structure.
- Synchronize Directories in
.claude/sessionsOnce you have the ideal structure defined, navigate to the.claude/sessionsdirectory and perform the following actions:- Reconcile Existing Directories: Compare the current sub-directories against your new blueprint.
- Rename, move, or delete existing directories to match the new structure.
- Relocate session files from any old or incorrect directories into their proper new locations.
- Create New Directories: For any features or areas in your blueprint that do not yet have a corresponding directory, create them now.
- Reconcile Existing Directories: Compare the current sub-directories against your new blueprint.
- Ensure Directory Persistence
- In any sub-directory that is empty (whether newly created or after moving files), add a
.gitkeepfile. This ensures the directory structure is committed to version control.
- In any sub-directory that is empty (whether newly created or after moving files), add a
- Add or update
.claude/sessions/README.mdas relevant.
Token Optimization
Expected range: 100–400 tokens (initial), 50 tokens (already initialized)
Caching: Caches init state in .claude/sessions/.init_cache.json for 7 days.
Early exit: Returns immediately if session tracking is already initialized.
Patterns used: Grep-before-Read, early exit, caching