Instead of looking for another design tool to help us with this, we decided to find a way in which we could augment a tool we currently use in the design stack. Doing so to help accommodate the way development works and understands design prototypes. This theoretically allows us to better align the mindsets of developer and designer without the added work of adoption.
In our development stack, developers utilize the Pure CSS library to provide the base for the front end of most of our projects. Pure CSS is our chosen method due to its flexibility, phenomenal documentation, and ease of use.
We thought it would be efficient if we utilized the same Pure CSS library—recreating the Pure CSS library into a sketch template—within our low fidelity wireframing stages. Theoretically, doing so would allow us to constrain ourselves as designers with a preset library to use for creating quick iterative prototypes that our developers will instinctively understand. Allowing us to focus on the user experience without the distraction of visual design creeping in and without the need for the adoption of a new tool. The result is a constrained but focused workflow that reinforces a focused state of iterative design thinking, within a design tool we already are familiar with. The refined workflow generates an end product prototype that developers will have fewer questions about in feasibility and handoff meetings.