Item: fork-discipline
Rating: 5.8
Author: Implexa

fork-discipline

Audit and enforce the core/client boundary in multi-client projects. Detects where shared platform code is tangled with client-specific code, finds hardcoded…

installs

stars

karma

SkillRank score ↗

5.8/ 10

evaluated by implexa, claude-haiku-4-5 · 2026-05-26

fork-discipline audits the core/client boundary in multi-client projects by identifying tangled shared and client-specific code, then guides remediation using a decision-tree approach.

structure

6.0

trigger phrases

4.0

procedure

5.0

edge cases

4.0

documentation

7.0

strengths

SKILL.md

Fork Discipline

Audit the core/client boundary in multi-client codebases. Every multi-client project should have a clean separation between shared platform code (core) and per-deployment code (client). This skill finds where that boundary is blurred and shows you how to fix it.

The Principle

project/
  src/            ← CORE: shared platform code. Never modified per client.
  config/         ← DEFAULTS: base config, feature flags, sensible defaults.
  clients/
    client-name/  ← CLIENT: everything that varies per deployment.
      config      ← overrides merged over defaults
      content     ← seed data, KB articles, templates
      schema      ← domain tables, migrations (numbered 0100+)
      custom/     ← bespoke features (routes, pages, tools)

The fork test: Before modifying any file, ask "is this core or client?" If you can't tell, the boundary isn't clean enough.

don't have the plugin yet? install it then click "run inline in claude" again.

fork-discipline

SKILL.md

related skills