deep-fusion-over-plugin-install-for-capability-upgrades

When integrating external repos into an existing skill ecosystem, cherry-pick intelligence and fuse it into existing skills rather than installing new skills side-by-side. Installing Impeccable as a separate plugin alongside frontend-taste creates ambiguity about which skill governs design quality (Law #2 violation) and doubles context window cost. Deep fusion merges non-overlapping rules into existing skills, wires deterministic tools as hooks, and maintains a single source of truth per capability domain. Approach B (plugin install) was rejected specifically because of skill overlap and context bloat.

Related

• deep-fusion-beats-plugin-install-for-design-skill-upgrades
• deep-fusion-beats-plugin-install-for-overlapping-skills
• deep-fusion-over-plugin-install-for-skill-overlap-prevention
• deep-fusion-vs-plugin-install-for-repo-integration
• deep-fusion-vs-plugin-install-for-skill-upgrades
• progressive-disclosure-skill-architecture-four-layer-pattern
• deep-fusion-beats-plugin-install-for-skill-ecosystem-integri
• frontend-deep-fusion-architecture-decision
• deep-fusion-over-install-for-capability-integration-avoids-s
• deep-fusion-over-plugin-install-avoids-law2-violation
• deep-fusion-vs-plugin-install-for-capability-upgrades
• domain-overlays-compose-simultaneously-at-runtime