Post by Melissa Milloway

What's one thing you need to do to scale vibe coded projects? Most L&D teams have some version of a style guide. Like a brand deck, a template library, a Figma file someone made two years ago that half the team uses or knows about. The problem is none of it is connected. You update a color and you're manually hunting through every file. You may have a style guide that exists but it doesn't always get applied to the work. For our Meridian Emergency Communications project, I'm starting with a design system before I touch a single deliverable. Right now it covers the foundations like color tokens, typography, spacing, component patterns, icon rules, voice and tone. As I build out each deliverable, the system will grow with it. By the time we have deliverables like a Rise course, Mighty interactives, videos, or event presentations, they'll all pull from the same source to automatically create a consistent design. That means a few things practically: ➡️ When Meridian updates their brand, we update the design system once and every deliverable inherits the change. No hunting through six courses to swap a hex code. ➡️ When someone new joins the team and needs to build something, they don't have to reverse-engineer what the brand is supposed to look like. ➡️ When we vibe code the Mighty interactives using Claude Code, the design system goes into the prompt. And our styling will also auto apply to our entire Rise project via the Mighty plugin. This is what scalable and maintainable L&D operations looks like. In my experience setting up a system like this, ensures that we spend time on solving the learning opportunities. If you're just finding this, I'm building a fictional 911 dispatch center training program to document what scalable L&D operations looks like from both the leader and IC seat. I'm documenting my decisions along the way. What does your team use to keep design consistent across deliverables? #eLearning #InstructionalDesign #LearningandDevelopment #AIinLearning