frontend-deep-fusion-vs-plugin-install-rationale
When integrating external design intelligence repos, Deep Fusion (absorbing into existing skills) is correct over Plugin Install (adding new skills). Plugin Install creates skill overlap (e.g., Impeccable anti-slop vs frontend-taste anti-slop) which violates Law #2 Zero Ambiguity, and competing design intelligence sources bloat context window. Deep Fusion merges non-overlapping intelligence and preserves single-source-of-truth per domain. Always evaluate new repos for overlap against existing skill stack before installing as-is.
Related
- deep-fusion-over-plugin-install-for-zero-ambiguity
- deep-fusion-over-plugin-install-for-skill-overlap-prevention
- deep-fusion-beats-plugin-install-for-design-skill-upgrades
- deep-fusion-over-install-for-capability-integration-avoids-s
- deep-fusion-beats-plugin-install-for-overlapping-skills
- deep-fusion-vs-plugin-install-for-capability-upgrades
- frontend-skill-deep-fusion-approach-a-architecture
fusion-invariants-lint-requires-exact-header-format(archived)- domain-overlays-compose-simultaneously-at-runtime
- seo-skill-ecosystem-nucleus-agrici-v190
- domain-overlay-skills-missing-layer-cross-references