Onboard Claude Code on an existing project
You launch Claude Code on an existing project and it dives into coding without grasping the architecture. Best Practice repo gives you templates for your CLAUDE.md and project rules, Graphify builds the dependency graph Claude queries before touching code (replaces 10-20 Grep/Glob with a natural-language query), RPI Pattern enforces the Research phase before any implementation.
Why
You inherit an 800-file repo and must ship in 5 days. The scene: you're handed an existing project: fork, contract, new job. 800 files, opaque cross-module dependencies, implicit conventions, ZERO up-to-date docs. You prompt "explain this project" to Claude Code, you get a polite mush that paraphrases the README. You spend 3 days opening files at random, the 4th realizing half of what you read is deprecated, the 5th shipping in panic mode. This kit installs the right order: you index reality (code graph, detected dependencies), you freeze observed patterns (project memory written by hand,…
When
Onboarding phase on a non-trivial existing project, for a dev/PM/tech-lead who must ship fast without breaking things. ✅ You know it's your kit when The repo is over 200 files: you can no longer hold the picture in your head The docs are stale or missing: 2024 README, empty ARCHITECTURE.md You must deliver a specific feature, not just exploring for fun ❌ Not for this kit You're starting a…
Tools included
- Claude Code Best Practice
- Graphify
- Rpi Pattern