deep-fusion-vs-plugin-install-for-skill-upgrades
When integrating external repos/tools into an existing skill ecosystem, merging intelligence into existing skills (‘Deep Fusion’) avoids Zero Ambiguity violations — two competing design intelligence sources (e.g., Impeccable anti-slop + frontend-taste anti-slop) create skill overlap and context window bloat. Installing as separate plugins causes Law #2 violations. The correct pattern: absorb non-overlapping intelligence into the closest existing skill, not add a parallel skill.
Related
- deep-fusion-over-plugin-install-for-skill-upgrades
- plugin-install-rejected-skill-overlap-ambiguity
- oracle
- docker
- graphiti
- progressive-disclosure-skill-architecture-pattern
- oklch-color-gap-in-current-frontend-skills
- deep-fusion-vs-plugin-install-for-repo-integration
- oklch-first-color-science-gap-in-frontend-skills
- deep-fusion-beats-plugin-install-for-design-skill-upgrades
- deep-fusion-beats-plugin-install-for-overlapping-skills
- deep-fusion-over-plugin-install-for-skill-overlap-prevention
- deep-fusion-beats-plugin-install-for-skill-overlap
- deep-fusion-over-plugin-install-for-capability-upgrades
- frontend-deep-fusion-architecture-decision
- deep-fusion-preferred-over-plugin-install-for-skill-integrat
- deep-fusion-chosen-over-parallel-skill-install-for-frontend
- deep-fusion-beats-plugin-install-for-skill-integration
- frontend-skill-deep-fusion-over-plugin-install-decision
fusion-invariants-lint-requires-exact-header-format(archived)