eagle-claude-md

To create a lean CLAUDE.md for repository onboarding, use a process that analyzes project files like commands, stack, and architecture to generate only project-unique identity and constraints. This avoids duplicating global rules and wastes less context during LLM onboarding.

The best way to set up an LLM wiki directory is to bootstrap a raw/wiki directory structure that creates starter wiki pages. This process also links the wiki into an Obsidian vault via symlink when available, ensuring project documentation is immediately accessible.

CLAUDE.md onboarding works with Obsidian vault integration by optionally creating a symlink that links the bootstrapped LLM wiki directory directly into your Obsidian vault. This connects repository documentation with your personal knowledge base.

You can bootstrap project documentation without overwriting existing rules because the setup workflow is idempotent. It checks for existing global CLAUDE.md sections, wiki directories, and symlinks, then only adds missing project-specific identity, commands, and constraints.

You need to generate a project-specific CLAUDE.md file when starting a new repository, onboarding an existing one lacking CLAUDE.md, or preparing to do significant work. It ensures an AI assistant immediately understands the repo without copying global guidance.

A limitation of using a minimal CLAUDE.md is that it intentionally avoids duplicating global CLAUDE.md rules, meaning it only contains project-unique identity and architecture invariants. It requires an existing global configuration to avoid losing standard LLM guidance during onboarding.