Skills for Real Engineers. Straight from my .agents directory.
39 skills
fork-discipline
Agent skill from
Audit and enforce the core/client boundary in multi-client projects. Detects where shared platform code is tangled with client-specific code, finds hardcoded client checks, config files that replace instead of merge, scattered client code, migration conflicts, and missing extension points. Produces a boundary map, violation report, and refactoring plan. Optionally generates FORK.md documentation and restructuring scripts. Triggers: 'fork discipline', 'check the boundary', 'is this core or client', 'platform audit', 'client separation', 'fork test', 'refactor for multi-client', 'clean up the fork'.
How to install fork-discipline
install fork-discipline
# install the claude-skills pack with the skills CLI
npx skills add jezweb/claude-skills# or add only this skill to Claude Code: copy the folder
plugins/dev-tools/skills/fork-discipline/
# into
~/.claude/skills/fork-discipline/ (all projects)
.claude/skills/fork-discipline/ (one project)
1# Fork Discipline23Audit 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.45## The Principle67```8project/9 src/ ← CORE: shared platform code. Never modified per client.10 config/ ← DEFAULTS: base config, feature flags, sensible defaults.11 clients/12 client-name/ ← CLIENT: everything that varies per deployment.13 config ← overrides merged over defaults14 content ← seed data, KB articles, templates15 schema ← domain tables, migrations (numbered 0100+)16 custom/ ← bespoke features (routes, pages, tools)17```1819**The fork test**: Before modifying any file, ask "is this core or client?" If you can't tell, the boundary isn't clean enough.2021## When to Use2223- Before adding a second or third client to an existing project24- After a project has grown organically and the boundaries are fuzzy25- When you notice `if (client === 'acme')` checks creeping into shared code26- Before a major refactor to understand what's actually shared vs specific27- When onboarding a new developer who needs to understand the architecture28- Periodic health check on multi-client projects2930## Modes3132| Mode | Trigger | What it produces |33|------|---------|-----------------|34…
Excerpt shown under the repository's MIT license.
More skills in claude-skills
Keep exploring
Similar skill repositories
An agentic skills framework & software development methodology that works.
15 skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
CC1 skill
Public repository for Agent Skills
20 skills
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
CCCU6 skills
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
CCCXCUGH6 skills