deep-fusion-vs-plugin-install-for-repo-integration

When integrating external repos/tools into an existing skill ecosystem, absorbing their intelligence into existing skills (Deep Fusion) is superior to installing them as standalone plugins. Installing separately creates skill overlap and ambiguity (Law #2 violation), competing design intelligence sources, and context window bloat. Reserve standalone installation only for truly non-overlapping domain skills (e.g. WebGPU — zero overlap with frontend stack).

Related

• deep-fusion-vs-plugin-install-for-skill-upgrades
• deep-fusion-over-plugin-install-for-skill-upgrades
• plugin-install-rejected-skill-overlap-ambiguity
• oracle
• docker
• deep-fusion-beats-plugin-install-for-design-skill-upgrades
• deep-fusion-beats-plugin-install-for-overlapping-skills
• webgpu-skill-progressive-disclosure-architecture-pattern
• deep-fusion-beats-plugin-install-for-skill-overlap
• deep-fusion-over-plugin-install-for-capability-upgrades
• deep-fusion-over-plugin-install-prevents-skill-sprawl
• frontend-deep-fusion-architecture-decision
• deep-fusion-preferred-over-plugin-install-for-skill-integrat
• deep-fusion-beats-plugin-install-for-skill-integration