An honest comparison. All three are good tools — they optimize for different things. Skynet UI optimizes for zero build steps and LLM-generated markup that just works.
| Skynet UI | Tailwind CSS | Bootstrap | |
|---|---|---|---|
| Setup | 2 files, paste a <link> + <script> | Build step (CLI/PostCSS/Vite) | 1–2 files or npm |
| Build step | None, ever | Required for real use | None (Sass optional) |
| Components | 80+ styled + behaviors built in | None (utilities only; paid Tailwind Plus or libraries) | ~25 styled, JS via plugins |
| Utilities | ~400, Tailwind-named, semantic colors | Everything, any value (JIT) | Basic set |
| Arbitrary values | Yes — runtime (bg-[#1da1f2], ~50 prefixes + variants) | Yes (compiler) | No |
| Theming | 9 themes + builder; CSS vars, one attribute | Config/CSS-first tokens; dark via variant | CSS vars + Sass; dark since 5.3 |
| Dark mode | Default, automatic everywhere | You write dark: on every element | One attribute |
| JS behaviors | Declarative data-sk-*, zero deps | Bring your own | Bundled plugins |
| AI / LLM support | First-class: llms.txt, MCP server, chat kit, markdown renderer, streaming | Well known to models (training data) | Well known to models |
| File size (page pays) | ~160 KB CSS + ~106 KB JS, cached; ~34 KB gzipped total | Tiny (purged) — plus your component CSS | ~230 KB + Popper |
| Purge / tree-shake | No (one shared cached file) | Yes (compiler) | No (Sass imports) |
| Ecosystem | Small and new | Huge | Huge, mature |
| License / cost | MIT, everything free | MIT core; component library is paid | MIT |
flex, grid-cols-3, md:hidden, hover:scale-105,
bg-gradient-to-r…) with semantic colors instead of the raw palette.
The LLM reference ends with a step-by-step conversion guide any model can follow.
<link rel="stylesheet" href="https://skynetui.com/skynet-ui.css"> <script src="https://skynetui.com/skynet-ui.js" defer></script>