If you've ever seen an `if (client === 'acme')` check creep into what should be shared platform code, you need this. It audits multi-client codebases for boundary violations: hardcoded client names in core, config files that replace instead of merge, client-specific code scattered in src/, and missing extension points that force developers to patch shared code for every new deployment. You get a boundary map showing what's actually core versus client-specific, a violation report with severity levels, and a refactoring plan. Most useful right before adding a second or third client to a project, or when onboarding someone who needs to understand why the codebase is structured the way it is.
npx skills add https://github.com/jezweb/claude-skills --skill fork-discipline