[Wordpress] Add a 'bring your own component library' feature

I'm a designer/developer who uses Bricks/WP Etch for my client work, and I've been thinking a lot about the future of our workflows. I'm hoping to get some thoughts from other pros here. On one hand, the native reusable elements in modern builders are fantastic for efficiency. On the other, I find myself locked into a single ecosystem. My meticulously crafted Bricks patterns are useless if a client comes to me with an existing Elementor site. This has led me down a rabbit hole, exploring a more "agnostic" way to build. At the same time, AI tools are getting incredibly powerful. They're great for generating initial ideas, but the final output often feels generic and still needs to be rebuilt and refined within my preferred builder to meet a professional standard. This got me thinking... what if the "pro" workflow of the future isn't about saving patterns inside a builder, but building them outside? I've started building a small, offline tool for myself that's basically a "component scratchpad." In it, I can use AI to generate the boilerplate for complex sections, but then I can immediately refine the code, apply advanced/fluid CSS (clamp(), etc.), and save the finished component as pure, optimized HTML/CSS. The result is a library of truly portable, high-quality "Lego blocks" that I can drop into the code block of any builder, Bricks, Etch, Elementor, Gutenberg, you name it. I know what some of you are thinking... "Why not just stick to one builder?" Many of us do, but this approach could offer a way to maintain a single, "golden" component library that works across any project, regardless of the client's stack. So, my question for the community is... **1. For those who stick to one builder** Do you ever feel limited by your builder's styling or structure, and wish you had a faster way to build and import truly custom, code-first components? **2. For those who work with multiple builders** Is the pain of rebuilding components for each new client a significant drag on your efficiency? I'm trying to gauge if a "bring your own component library" approach has real-world value, or if the combination of native builder features and improving AI is making this idea obsolete before it's even built. Not selling anything, just trying to start a discussion about our workflows. Thanks!