Featured Builder Spotlight

Vibe-coded compliance, examined through a Learning Rewired Lab lens.

Ronni Teagle built an AI-assisted bloodborne pathogens compliance course in Claude Design. The finished artifact is course-shaped, but the more interesting story is underneath it: accessibility choices, interaction logic, UDL constraints, and the instructional judgment required when AI makes polished screens fast.

Compliance training has to survive contact with the real moment.

Frontline caregivers at a senior living facility need to follow OSHA bloodborne pathogens standards correctly when the moment is messy, time-sensitive, and practical. Traditional compliance training often treats that work like information transfer: read the policy, click through the content, pass the check.

Ronni’s submission pushes against that pattern. The problem was not simply that caregivers needed more information. They needed preparation for the actual situations where exposure can happen and where the right response has to be recalled, selected, and acted on quickly.

“Traditional compliance training is a click-through slog that doesn’t prepare them for the messy, real situations where exposure actually happens.”
Ronni Teagle, Featured Builders submission

A scenario-based compliance course built end to end in Claude Design.

Ronni designed and built a fully accessible OSHA bloodborne pathogens compliance course in Claude Design. The course included five custom interaction types and UDL features throughout.

That matters because the project was not just an experiment in making something look polished with AI. It was an experiment in whether an AI-assisted build could still preserve the designer’s instructional intent, accessibility standards, and decision architecture.

Project type Scenario-based compliance course
Tool Claude Design
Interaction layer Five custom interaction types
Design priority UDL and accessibility throughout

Course Preview

Explore the actual build behind the feature.

Ronni’s project is available as a live course prototype. As you explore it, look beyond the visual polish. Notice how the experience uses scenario framing, interaction choices, accessibility decisions, and learner-centered constraints to make compliance feel closer to the real work.

The real friction was polish versus control.

Ronni described the core tension clearly: Claude Design could produce something that looked strong quickly, but the tool’s defaults did not always match the accessibility behaviors, keyboard expectations, interaction logic, or UDL standards she wanted.

That is the part worth studying. AI can reduce the cost of production, but it can also hide design decisions inside defaults. The more polished the first output looks, the easier it becomes to accept the tool’s choices as if they were the design.

AI gives you

Speed, polish, layout, and momentum.

Design still needs

Judgment, accessibility, scope, and practice logic.

Ronni did not treat the AI output as final. She pushed back. She overrode defaults. She protected accessibility when it would have been easier to let clean visuals win.

The tool does not make the designer.

The strongest part of Ronni’s submission is not that she used AI. It is that she kept the instructional thinking in her own hands. She scoped the experience to a meaningful slice, chose active interactions over click-next delivery, and protected accessibility when the defaults did not match the learner need.

“AI lowers the cost of building, which means our value shifts even more toward instructional thinking, not less.”
Ronni Teagle

That is a useful lesson for the field. If AI makes production faster, the designer’s value does not disappear. It moves upstream into diagnosis, scoping, practice design, accessibility judgment, and the ability to decide what learners actually need to do.

Learning Rewired Lab Lens

What would move this from course-shaped to system-shaped?

Ronni’s project is a strong AI-assisted course build. The next evolution would be connecting the course to the larger performance environment where bloodborne pathogen decisions actually happen.

Current shape

Scenario course

The course helps learners encounter realistic choices before the stakes are real. That is valuable, especially when the content is usually treated as passive compliance.

System question: What happens after completion to support the same behavior at work?

Builder Reflection

Accessibility was not added at the end. It shaped the build from the start.

Ronni shared that the part she is proudest of is not the challenge win. It is that she proved she could build something polished and genuinely accessible in a new tool, under real constraints, without letting go of the instructional thinking.

That throughline matters. UDL and accessibility were not treated as finishing touches. They were design starting points. In Ronni’s words, she designs for the learner who gets left out of most training, then builds everything else around that.

Why this was featured: This submission shows a designer wrestling with the actual tradeoff AI creates for learning work: faster production, but a greater need for human judgment around access, practice, and purpose.

What Other Builders Can Learn

Three useful design moves from this feature.

01

Use AI for momentum, not judgment.

Claude Design helped Ronni build quickly, but the important design calls still came from the human designer.

02

Treat accessibility as structure.

UDL and accessibility work best when they shape the design from the start, not when they are added after the interface looks finished.

03

Turn compliance into practice.

Even course-shaped compliance can become more useful when learners are asked to make decisions, interpret situations, and practice the real moment.

Submit Your Work

Your project could become the next feature.

Featured Builders highlights useful learning design work, prototypes, scenarios, job aids, system maps, facilitation moves, and design decisions the community can learn from.