Nitro Kit is my UI kit for Ruby on Rails. Version 2 is rebuilt completely different than 1.

1 was tailored to devs. 2 is tailored to agents.

How so? What’s the problem? Well, agents can build anything. BUT theyyy quickly lose grip on what components you have and which ones it should build again but slightly different. Do you know what makes a good dialog? Do you really want to discuss it with an algorithm on every new site you build?

Over time, without guidelines, without precedence, this can only end up a mess. You need a system. You know this. But do you want to invent one? No! You have a(nother) CRUD app to build!

Nitro Kit fixes UI confusion by providing strict guidelines on how to do UI work in a Rails context. Its aesthetics are customizable but the APIs strict. It comes with a giant collection of prebuilt components and blocks to build from.

All the way from dialog to form to controller. Convention over configuration, right?!

Maybe your app needs a settings section? An agent can quickly build some settings section. But does it match the rest of your app? Does it use the same buttons, the same form field pacing? Does it use the right Turboframe setup? A working light/dark mode for the Lexxy text editor? Do you want to not worry or find out in 3 weeks by coincidence?

When you tell your agent “admin section” does it come with sortable tables, search, a frickin’ command-k panel? If you want to add one, does it fit right in? When you say “popup menu here” or “lightbox there” or “delete dialog” can you trust that your agent just knows what to reach for?

Nitro Kit 2 is built so your agent does the right thing on the first try.

The gem comes with all components, layouts and skills available FOR FREE and open source.

And if you want more, there’s an MCP server with pre-trained knowledge of a bunch of prebuilt, common sections, blocks and more that makes the process even easier for your agent.

You can install and use it now. It’s not done (is anything ever?) and I still haven’t decided on the Pro pricing. (Wdyt?)

I’m using it already and it has been a real jawdropper to work with so far, if I can say so myself. Even upgrading from Nitro Kit 1 to 2 on 4-5 of my sites has had minimal if any issues.

If you like Ruby on Rails or you really just don’t want to bother finding the best framework (it’s Rails) follow along here and I’ll soon share more.