Follow an Utility first approach

[SiddharthSham]

Is your feature request related to a problem? Please describe.
I have found utility-first to be a great (if not the best) approach to CSS, for the following reasons:

• Smallest possible file transfer sizes
• Easy to extend with custom CSS
• more reasons here

The most common con of using this technique is the steep learning curve, which is effectively combated by CSSify's user-defined class generation system. It really takes the best of both worlds.

Describe the solution you'd like
Redefine the existing SCSS modules to generate Utility-first classes. Similar to how Tailwind CSS or Wool CSS work.

Describe alternatives you've considered
Outside of utility-first, a popular strategy is BEM. However, this approach is better suited for custom styling, than for a framework. An interesting alternative is the new CUBE CSS method, but I'm unsure how one would apply it to CSSify.

[sansyrox]

@SiddharthSham , this sounds good 🔥

From the first glance, CUBE CSS looks like it's based over BEM principles only. Should be fairly simple to migrate if that becomes a thing.

An interesting alternative is the new CUBE CSS method, but I'm unsure how one would apply it to CSSify.