I Built a Claude Code Skill to Sync CLAUDE.md Across 12+ Laravel Projects

You know that feeling when you update something important in one place, then you realise — oh no, I need to propagate this to like 10 other projects ? Yeah. That was me last week. A Bit of Background I maintain a Laravel kickstart project called Kickoff . Every Laravel project I start — personal, client, internal — starts from this base. It contains my opinionated project structure, conventions, Docker setup, and one particularly important file: stubs/CLAUDE.md If you're using Claude Code, this file matters a lot. It's the instruction manual Claude reads before it touches your codebase. Stack, conventions, patterns, boundaries — it's all there. Without it, Claude guesses. With it, Claude codes like it already knows your project. Problem: I have multiple projects built on top of Kickoff. Every time I update stubs/CLAUDE.md in Kickoff, those changes need to flow downstream. Into every project. One by one. I did it manually twice. Third time, I refused. The Boring Fix vs The Right Fix The