skill-source-composition
Skill Source Composition
Apply this methodology to the requested import, adaptation or composition, whether the sources are skills, code or documentation. Reuse the project's conventions and tooling; introduce only the machinery its maintenance needs justify.
Source identity
Classify each carried source independently:
| Classification | Contract |
|---|---|
| Verbatim | Carried bytes match the pinned original exactly. |
| Patched (verbatim patched) | Preserve the pristine original and a replayable patch that reproduces the carried bytes exactly. Record why the adaptation exists. |
| Derived | Reworked from an identified source; retain provenance and explain the derivation. Update adoption requires comparing behavior and intent, rather than relying on patch replay. |
| Authored | Locally owned work, distinguished from carried upstream material. |
Composition is a separate axis: sources work together under a local entry point or integration. Keep their identities and classifications. Compose to resolve a concrete conflict, route distinct methods or bundle related capabilities; an unchanged independent package can retain its original name.
Rulings settle actual conflicts: identify the competing guidance, which owns the disputed behavior and when that decision applies. Put the actionable ruling where the consumer uses it; keep provenance and maintenance explanations in records.