directory-deepdive

Documenting directory architecture involves analyzing design patterns, dependencies, and naming conventions to create or update a CLAUDE.md file. This ensures implementation knowledge is placed within the analyzed directory for immediate context loading during onboarding.

The best way to analyze design patterns and dependencies is to investigate the target directory and its subdirectories to identify key abstractions and naming conventions. This generates structured documentation of the module's architecture and implementation details.

Generating a CLAUDE.md file involves running an architecture investigation on a specified directory to analyze design patterns and dependencies. This creates or updates the file to capture implementation knowledge and boost developer productivity.

Yes, this code analysis approach works for subdirectories by investigating the target directory and its nested structures. It analyzes design patterns and dependencies across the hierarchy to document implementation knowledge for context loading.

You need to create implementation knowledge documentation when starting work in an unfamiliar area or assigned a new feature in a large project. This ensures crucial information about the module's architecture is readily available for future reference.

Yes, you can update an existing CLAUDE.md file by performing a directory deep dive. The investigation analyzes design patterns and dependencies to ensure the existing documentation captures the most current implementation knowledge.