Comment by Brajeshwar

8 hours ago

First, I confess that I had built quite a lot of CSS Frameworks and Design Systems in my early developer life. So, this is going to be more of a personal experience.

Ever since Coding Assistant LLMs became pretty good (2025-Q4 - 2026-Q1), I feel that it makes very little sense to continue to use pre-defined CSS Frameworks that 'has everything.' Of course, it is still OK if the general team decides on one, and they are OK (such as the Tailwinds, MUI of the frontend world.)

I have used Foundation[1] and Bourbon[2] extensively. Mostly because I can break it down and take just what the project needs and keep it within a low CSS budget for any project.

With that in mind, in the 10+ projects that started for some of the biggest brands of the world, I just defined the CSS framework, design systems, design token, with room for extension as the project grows. Claude Code is my tool of choice for now and I just let it run overnight, tweak as the project scaffolds and finally takes about less than a week to have a complete CSS framework in just plain CSS, and JavaScript where it needs to talk to the broader frontend.

1. https://get.foundation

2. https://www.bourbon.io

3 comments

Brajeshwar

Reply
fodkodrasz  1 hour ago

I'm not being a design/frontend person, but I can decide if I like or don't like something. Having some default "themes" to say so I can choose from is a large help for me.

I mean with AI you can possibly more easily make decisions on the motor oil and suspension choices of the car you are building... but there may still be people who only want to get an pre-designed car, and only make calls on trim and color maybe.