Where this came from
How this workflow was actually built
Hi, I'm Agi. I've been building websites with Divi for 6 years, and started working with Divi 5 this year. It's still early days for the new builder — but I'm excited about what it makes possible, and this workflow is a big part of why.
When I first tried using Claude for Divi work, the output looked plausible — but it broke on import, every time. So I started digging into how Divi 5 JSON actually works, and figured out a process to make Claude generate valid files that import correctly.
Then came the key insight: don't jump straight to pages. Build the design system first — fonts, colours, spacing, presets — import it once, and let every page draw from the same source of truth. I also started feeding Claude real finished Divi 5 page exports alongside the skill files — giving it working examples, not just theory. The output got noticeably better.
"The result was a six-page website template system — a complete design system, six page templates, a Python build pipeline, and validated JSON throughout."
This guide documents that workflow so other Divi designers can use it — whatever niche you work in. It's a new workflow and I'm still learning as I go. If you find something that makes it better, I'd love to hear it.