Brainless: Shadcn components that look like Claude Code, Codex and Grok

6 hours ago (brainless.swerdlow.dev)

Why did you choose to use shadcn registry?

  • Generally, when using these components I ended up wanting to customize a lot. I switched around the options, coloring, the words in the loading, I mix and matched the components from different CLIs, etc.

    I think these are more useful as baselines than as final destinations, and I expect production users to customize them far more than options in components.

    I also separately don't really believe in traditional components anymore, code is cheap. The value in these components is that I took the time to pixel match a bunch of the CLIs, not the specific interface used to integrate them.

I fully expected this to be complements for the output you get from those tools for some reason, that AI generated look. No idea why anyone would want that though.

On a barely-related note, I'm getting a little tired of job openings at startups that emphatically require Shadcn and Tailwind for dedicated frontend development. Shadcn and Tailwind are crutches for "fullstack" devs -- if I'm a really accomplished frontend developer, they make little sense for me to use and hamper what I can do for you. Just a peeve.