deep-fusion-over-plugin-install-for-zero-ambiguity
When integrating external repo intelligence into an existing 7-skill frontend stack, Deep Fusion (absorbing intelligence into existing skills) was chosen over Plugin Install (install as-is + orchestrator wiring) to avoid skill overlap that violates Law #2 (Zero Ambiguity). Competing design intelligence sources (e.g., Impeccable anti-slop + frontend-taste anti-slop) create context window bloat and ambiguous routing. The rule: cherry-pick non-overlapping intelligence and merge it into existing skills rather than creating parallel skills with overlapping domains.
Related
- deep-fusion-preferred-over-plugin-install-for-skill-integrat
- deep-fusion-beats-plugin-install-for-overlapping-skills
- 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
- frontend-deep-fusion-vs-plugin-install-rationale
- deep-fusion-vs-plugin-install-for-capability-upgrades
- frontend-skill-deep-fusion-approach-a-architecture
- frontend-skill-deep-fusion-over-plugin-install-decision
- marketing-speak-in-skill-files-reduces-intelligence-density
- master-orchestrator-requires-explicit-not-covered-section