init-deep

Create nested CLAUDE.md files for per-directory contextual guidance.

173|8|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/TechDufus/oh-my-claude --skill init-deep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-deep
Source: https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/init-deep
Command: npx skills add https://github.com/TechDufus/oh-my-claude --skill init-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a lightweight per-directory guidance system by placing CLAUDE.md in root and in subdirectories to enable contextual loading while preventing root bloat.

Core Features & Use Cases

  • Create a minimal root CLAUDE.md with nested CLAUDE.md files across the repository for true progressive disclosure and faster context loading.
  • Ensure closest CLAUDE.md to the file being edited takes precedence, enabling targeted guidance.
  • Supports CLI options to control nesting depth and fresh regeneration of CLAUDE.md structures.

Quick Start

Create a root CLAUDE.md and add nested CLAUDE.md files for relevant directories to enable true progressive disclosure.

Frequently Asked Questions about init-deep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provide contextual guidance to Claude Code without bloating the root CLAUDE.md?

To prevent root CLAUDE.md bloat, you can initialize a nested CLAUDE.md structure with a minimal root file and directory-specific files. This enables per-directory contextual guidance that loads automatically as you navigate subdirectories.

How does contextual guidance work when multiple CLAUDE.md files exist in different directories?

When multiple CLAUDE.md files exist, the closest CLAUDE.md to the file being edited takes precedence. This progressive disclosure mechanism loads targeted guidance based on your current subdirectory, ensuring relevant context without manual configuration.

What is the best way to set up per-directory CLAUDE.md files across a repository?

The best way to set up per-directory CLAUDE.md files is using the /init-deep CLI command. It creates a minimal root CLAUDE.md and automatically generates nested directory-specific files, enforcing a lightweight structure for progressive disclosure across the repository.

Can I control the nesting depth when generating CLAUDE.md files?

Yes, you can control nesting depth using the --max-depth CLI variant. This option manages the per-directory structure generation, while the --fresh variant allows complete regeneration of existing CLAUDE.md files across the repository hierarchy.

When should I use a nested CLAUDE.md structure instead of a single root file?

You should use nested CLAUDE.md structures when a single root file becomes too large and slows context loading. Directory-specific files solve this by providing targeted guidance that only loads when editing files in that specific subdirectory.

How do I migrate existing root CLAUDE.md content to a nested directory structure?

To migrate existing content to a nested directory structure, the init-deep skill supports migration patterns. It enforces a lightweight root CLAUDE.md and distributes context into subdirectory files, using the --fresh CLI variant to regenerate the structure.