deep-fusion-over-plugin-install-for-skill-overlap-prevention
When integrating external skill repos that overlap with existing skills (e.g., impeccable’s anti-slop vs frontend-taste’s anti-slop), installing as-is creates skill ambiguity (violates Law #2) and context window bloat from two competing intelligence sources. The correct pattern is Deep Fusion: absorb non-overlapping intelligence into the existing skill, delete the redundant source. Plugin install is only appropriate for wholly new capability domains with zero overlap (e.g., WebGPU).
Related
- deep-fusion-beats-plugin-install-for-overlapping-skills
- deep-fusion-vs-plugin-install-for-skill-upgrades
- deep-fusion-beats-plugin-install-for-design-skill-upgrades
- plugin-install-rejected-skill-overlap-ambiguity
- deep-fusion-over-plugin-install-for-skill-upgrades
- progressive-disclosure-skill-architecture-from-webgpu
- deep-fusion-over-plugin-install-for-capability-upgrades
- deep-fusion-over-plugin-install-prevents-skill-sprawl
- deep-fusion-beats-plugin-install-for-skill-ecosystem-integri
- frontend-deep-fusion-architecture-decision
- deep-fusion-chosen-over-parallel-skill-install-for-frontend
- deep-fusion-over-plugin-install-prevents-skill-ambiguity
- deep-fusion-over-plugin-install-for-zero-ambiguity
- deep-fusion-beats-plugin-install-for-skill-integration
- frontend-deep-fusion-vs-plugin-install-rationale
- deep-fusion-vs-plugin-install-for-capability-upgrades