frontend-deep-fusion-architecture-decision

Chosen approach for frontend capability upgrade: Deep Fusion (absorb intelligence from 4 repos into existing 7-skill stack rather than installing repos as-is). Rationale: avoids skill overlap/ambiguity (Law #2), prevents context window bloat from duplicate design intelligence sources. Key integrations: Impeccable’s 25 rules → frontend-taste + PostToolUse hook; SkillUI → new design-extractor skill; Design MD 66 brand files → design-library skill with npx getdesign integration; WebGPU skill installed as-is (niche domain, no overlap).

Related

• deep-fusion-over-plugin-install-for-capability-upgrades
• deep-fusion-over-plugin-install-for-skill-overlap-prevention
• deep-fusion-beats-plugin-install-for-design-skill-upgrades
• deep-fusion-vs-plugin-install-for-repo-integration
• deep-fusion-vs-plugin-install-for-skill-upgrades
• deep-fusion-chosen-over-parallel-skill-install-for-frontend
• frontend-skill-deep-fusion-approach-a-architecture