project-structure

You can automatically generate a living map of your codebase by running an auto-install command in the project root, which scans the repository and produces a readable `.claude/structure.md` file. This file documents directory trees, key files, and their purposes for quick orientation.

Self-healing project structure documentation automatically regenerates the `.claude/structure.md` file when it detects the codebase map is missing or outdated. It scans the current repository state, filters out noise, and updates the directory tree and key-file annotations to reflect the latest changes.

Yes, the project structure documentation works across languages and project types by scanning the repository and filtering noise to annotate parts of the tree. It identifies key files and maps their relationships regardless of the specific tech stack you are using.

The best way to map directory trees is to use an auto-installed structure generator that scans the repository and produces a `.claude/structure.md` file. This file provides annotated descriptions of directories and key files, clarifying project organization and relationships for quick orientation.

Yes, the generated `.claude/structure.md` file meets automated discovery requirements and supports OpenCode-compatible workflows. It ensures the project structure map is easily accessible and integrates with automated codebase orientation processes.

Your codebase structure map needs automatic regeneration to remain a living document that accurately reflects ongoing development. As directories and key files change, self-healing regeneration updates the `.claude/structure.md` file to prevent outdated documentation and maintain quick orientation.