The summary.
ORGANISE BY FEATURE, AND ESTABLISH WHICH WAY DEPENDENCIES FLOW
Features may depend on shared code; shared code may not depend on features. Otherwise everything depends on everything.
Review shared code periodically and move anything used once back into its feature.
A UTILITIES FOLDER THAT COLLECTS EVERYTHING UNCLASSIFIABLE IS A WARNING SIGN
Detect circular dependencies and import-rule violations automatically.
MICRO-FRONTENDS SOLVE A COORDINATION PROBLEM, NOT A TECHNICAL ONE
Establish that the problem is real. The complexity is substantial and difficult to reverse.
A DESIGN SYSTEM IS NOT A COMPONENT LIBRARY
It needs tokens, patterns, documentation, accessibility requirements, governance, and ongoing ownership.
Its success is determined entirely by whether people use it — which means being easier than not using it.
AUDIT WHAT EXISTS BEFORE BUILDING ONE
The number of button variants, colours and type sizes in use is always far more than anyone expected.
AN UNMET NEED IS FILLED BY SOMEONE BUILDING THEIR OWN
Which is how systems fragment. Handle requests promptly, and generate tokens from one definition rather than synchronising by hand.
