From xonovex-skill-connascence
Use when grading or loosening the coupling between two pieces of code, or judging how cohesive a module is. Triggers on connascence, coupling vs cohesion, 'too tightly coupled', decouple/loosen, the coupling ladder (content/common/control/stamp/data), the cohesion ladder, Law of Demeter / train wrecks like a.b().c(), positional vs named parameters, or reviewing a module boundary for coupling strength — even when the user doesn't say 'connascence' and only says 'tightly coupled'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/xonovex-skill-connascence:connascence-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Grade a seam by naming its worst coupling and its strongest connascence, then weaken or localize it — "tight/loose" is unactionable.
Grade a seam by naming its worst coupling and its strongest connascence, then weaken or localize it — "tight/loose" is unactionable.
SEAM a billing function reaches into an Order's private `total` field
GRADE content coupling (reaches internals) + connascence of meaning across a boundary
FIX Order exposes a neutral `amountDue()` value (rule of degree → data coupling);
billing reads the value — agreement is now named, local, and weak
npx claudepluginhub xonovex/platform --plugin xonovex-skill-connascenceGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.