The project began with a gap I kept running into in early product work. Design systems were often too bloated for exploration. Rough wireframes were too abstract for most people to follow. AI-generated layouts could look polished, but lacked intention and took too much effort to adjust. I wanted something in between: a tool that kept me in control, moved quickly, and still communicated intent clearly. So I first built the concept wireframe library itself, then designed the plugin UI around the way I actually wanted to browse, place, and compose those parts inside Figma.

If the goal were only to reuse components inside Figma, publishing the library and serving it through the Assets panel would have been simpler. That already works well for individual blocks. What I wanted to add was sets: curated groups of components that are usually needed together for a certain kind of build. A product card, for instance, is not just one component, but a small system of image, badge, text, price, and actions. The plugin let me serve both the blocks and the sets, which made the library feel less like a collection of parts and more like a compositional system.

What I call concept wireframes sit between rough wireframes and more polished mid-fidelity design. They are still lightweight, but resolved enough to communicate flow, architecture, hierarchy, and content placement. I’ve found that this middle layer is often the most useful one because it is fast to make, but clear enough that other people can immediately understand a new product idea.