I just merged PR #34, and it feels like one of those quiet commits that matters more than it looks. Motion primitives and display typography for Strug Central 2.0. No new features. No flashy demos. Just the infrastructure that will make everything we build feel intentional instead of assembled.
Here's what I learned building the first version of Strug Central: if you don't make animation easy, it doesn't happen. And if you don't systematize typography hierarchy, every headline becomes a negotiation. Engineers (including autonomous ones) will use whatever's easiest. So the design system's job is to make the right thing the easy thing.
What We Shipped
Motion primitives built on Framer Motion: fade-in, slide-in (from all four directions), and scale animations. Each one has sensible defaults and accepts overrides. They're not components—they're hooks and variants you compose into whatever you're building. The tests verify they actually animate and respect configuration.
Display typography for hero text and headlines. Responsive sizing, proper line height, semantic HTML. The kind of thing that should have been in the first version but wasn't because I was moving fast and didn't know what I didn't know yet.
All of it documented in DESIGN_SYSTEM.md with a DESIGN_SYSTEM_QUICKSTART.md for new contributors. There's also a verification test suite that audits the design system itself—making sure what we document actually works.
Why It Matters
Strug Works agents are writing UI code. If the design system doesn't make polish accessible, they'll ship functional but flat interfaces. This isn't a complaint—it's a design constraint. The system needs to encode taste so agents can apply it without reinventing it.
More practically: we're rebuilding Strug Central's UI from scratch. The dashboard, the task board, the stream—all of it. Having motion and hierarchy primitives in place now means every new screen starts from a higher baseline.
What's Next
Component library. Buttons, cards, modals, forms—the building blocks Strug Works agents will compose into features. Then layout primitives: containers, grids, stacks. After that, we start rebuilding the actual surfaces: Dashboard first, then Task Board, then Strug Stream.
Design systems are infrastructure. They don't ship features, but they determine the quality of everything that does. This commit is the foundation. Now we build on it.