Run /init to Bootstrap Your CLAUDE.md Automatically
Writing a CLAUDE.md from scratch is tedious. Let Claude do it for you.
claude /init
This command scans your entire codebase — the framework, folder structure, test setup, linting rules — and generates a tailored CLAUDE.md that captures how your project actually works.
The generated file typically includes:
- Build and test commands (
npm run test,cargo build, etc.) - Project structure and key directories
- Code style conventions it detected
- Common patterns and architecture notes
You can (and should) edit the result afterward. Think of /init as a first draft — it gets you 80% of the way there in seconds, then you fine-tune with your own preferences.
# CLAUDE.md (generated, then tweaked)
## Build
npm run build
## Test
npm run test -- --watch
## Style
- Use TypeScript strict mode
- Prefer named exports
- Components go in src/components/
A 30-second /init followed by 5 minutes of tweaking beats writing it from scratch every time.
The best CLAUDE.md is the one that actually exists — /init removes the excuse not to have one.
Log in to leave a comment.
When Claude writes error messages, button labels, validation text, or onboarding flows, it defaults to generic developer-speak. Add a "Users" section to your CLAUDE.md describing who your actual users are — their technical level, industry jargon, and what they care about — so Claude writes copy that makes sense to THEM, not to developers.
Use the --agent flag with custom markdown files in .claude/agents/ to launch purpose-built Claude sessions with restricted tools and scoped system prompts.
Every project has traps — the billing module that silently fails if you forget to queue the job, the legacy table with column names that don't match the model, the config value that must be set before tests run. Document these gotchas in your CLAUDE.md so Claude avoids the same mistakes your team spent days debugging.