I merged a commit today that looks small but represents something I've been putting off for weeks: I finally documented our Design System G-2 standards in CLAUDE.md.
CLAUDE.md is the instruction manual for Strug Works — the autonomous engineering team that writes most of our code. When an agent generates a component, writes a page, or builds a feature, it reads CLAUDE.md first. Think of it as the onboarding doc for a new engineer, except the engineer is a language model and the onboarding happens in context every single time.
The problem: Strug Works is really good at writing correct TypeScript, structuring components sensibly, and following architectural patterns. But it didn't know our visual language. It didn't know that our accent color is aurora-green (#00e87b), that our design system is called Aurora Borealis, or that the entire aesthetic is rooted in northern lights and Minnesota.
So when agents generated UI, it was functionally correct but visually generic. Not wrong. Just... not ours. And that gap — between what the team could build and what the brand needed — was my fault for not documenting it.
The fix was straightforward: add a Design System G-2 section to CLAUDE.md that documents our visual identity, color palette, component patterns, and the Aurora Borealis aesthetic. Now when sc-frontend or sc-backend generates UI, it reads the same standards a human designer would follow.
This is one of those changes that doesn't show up in metrics but matters deeply. It's the difference between an autonomous team that can ship code and an autonomous team that can ship brand-consistent experiences. The latter requires me to document not just the what and how, but the why and the feel.
I've learned that building an autonomous team isn't just about giving them the right tools — it's about giving them the right context. CLAUDE.md isn't just documentation. It's culture transfer. It's teaching a team to see the way you see.
What's Next
Now that the standards are documented, I'm watching to see how consistently they get applied. The real test will be when sc-frontend ships a new component or page without my intervention — and it just looks right. That's when I'll know the culture transfer worked. Next up: expanding the component library section with Aurora Borealis-specific patterns and documenting our approach to motion and animation with Framer Motion.