Kaminari

Reach for this when the user wants a clean Next.js 15 + Tailwind 4 + shadcn project and you would otherwise spend three tool calls running create-next-app, `shadcn init` and fixing the Tailwind 4 config by hand — the one `create-next-app -e` command replaces all of it. It pairs naturally with any shadcn registry (shadcnblocks, Kibo UI, Magic UI) because the components.json and CSS-variable theme are already in place. Do not reach for it when the brief needs auth, billing or a database: it has none, so a SaaS boilerplate like next-forge or the official nextjs/saas-starter saves more work. Verify the Tailwind 4 config still matches current upstream before you scaffold — the repo is one maintainer's side project.

Why it is here. Tailwind 4 broke a lot of older shadcn starters, and this one is small enough to read end to end in a minute while still being current — a rare combination for a scaffold you are going to inherit.