← All tools

A story, in full

create-next-beecode-pack

A Next.js starter so setup is not the first hour.

create-next-beecode-pack

An hour of setup before every new app.

A Next.js starter with ESLint, Storybook, Husky, Tailwind and shadcn/ui ready to go.

01A long weekend plan

A friend asked if we could start a small Next.js app over the vacation — nothing heavy, just enough to see if an idea was real. I said yes. Then the first evening vanished. Create the app, add ESLint the way I actually like it, set up Husky so a bad commit cannot wander off, stand up Storybook, pull in Tailwind, add shadcn/ui, and only then look at the thing we had come to build. By the time the starter felt "right," the holiday day was mostly gone. They said, not unkindly, "can we just write the app tomorrow?"

I knew this pattern. I had paid that first hour, sometimes more, at the start of too many side projects.

02What I packed

The next morning I started pulling my usual setup into one starter: create-next-beecode-pack. Next.js, ESLint, Storybook, Husky with pre-commit and pre-push hooks, Tailwind, shadcn/ui, the pieces I was tired of installing in the same order. The point was not to invent a framework. It was to make "clone this and start" a real sentence. It is on npm at 1.0.2, and the repo is public.

03What it does now

If you want to begin a Next app and you already know you will want linting, component stories, git hooks and a UI kit, you can start from the pack instead of assembling it again. You still have to write the product. You just do not have to earn the right to write it.

04What I learned

Short holidays are a good test for a starter. If setup eats the first day, the starter does not exist yet — only a checklist in your head. The checklist belongs in a repository.