Design systems engineers will actually use

The failure mode is familiar: a polished kit, a sprint of 'we'll clean it up later', and six buttons that all mean primary. Engineers invent what the file forgot — error, empty, disabled, loading, overflow.

Color, type, space, and radius should be named once and imported in code. If a designer changes a token, the product should change. If a developer needs a new red, the system failed, not the developer.

Long names, localization, permission denied, partial failure. Dashboards especially: the empty table is more common than the populated demo. If those frames do not exist, engineering will improvise, and improvisation becomes the brand.

The cheapest system maintenance is a designer who reads the implementation and an engineer who opens the source file. Handoff PDFs are how drift gets a job.