deep-fusion-over-install-for-capability-integration-avoids-skill-sprawl
When integrating external repositories into an existing skill ecosystem, ‘Deep Fusion’ (absorbing intelligence into existing skills) outperforms ‘Plugin Install’ (installing as separate skills). Installing Impeccable as a separate plugin creates competing design intelligence against frontend-taste (both do anti-slop detection), violating Law #2 (Zero Ambiguity) and bloating the context window with overlapping coverage. The correct pattern is to cherry-pick non-overlapping intelligence and merge it into the canonical skill, then wire automation as hooks.
Related
- deep-fusion-over-plugin-install-for-skill-upgrades
- deep-fusion-beats-plugin-install-for-overlapping-skills
- deep-fusion-beats-plugin-install-for-design-skill-upgrades
- deep-fusion-beats-plugin-install-for-skill-overlap
- deep-fusion-over-plugin-install-for-capability-upgrades
- deep-fusion-preferred-over-plugin-install-for-skill-integrat
- deep-fusion-over-plugin-install-avoids-law2-violation
- deep-fusion-over-plugin-install-prevents-skill-ambiguity
- deep-fusion-over-plugin-install-for-zero-ambiguity
- frontend-deep-fusion-vs-plugin-install-rationale
- frontend-skill-deep-fusion-over-plugin-install-decision
- taxonomy-drift-canonical-term-mappings