Stack

If you've ever packed a bag for a weekend, you already understand a stack.

You don't bring "travel." You bring a toothbrush, a charger, one pair of shoes that works with everything. Each item does one job. Together they get you through Saturday.

A stack is that bag, for software. Frontend, backend, database, auth — each is a thing you chose. The stack is the set.

People talk about stacks like they're religions. "We're a Next shop." "We're a Hono team." That is mostly shorthand for "we already packed these and we don't want to unpack."

At a hackathon you don't have a shop. You have a deadline. So you pack on purpose.

What you actually pick

Open the builder and the questions are the bag:

• What does the user see? That's the frontend.
• What does the work? That's the backend.
• Where does stuff live? That's a database.
• How do two pieces talk? That's an API.
• How do you know who someone is? That's auth.

None of those is the app. The app is what you write after the bag is packed.

Why the order matters

Some things don't go together. A toothbrush does not need a ski rack. The builder greys out combinations that will fight you later, so you don't discover the fight at 2 a.m. when the demo is at 9.

That's the whole point of a stack picker: not to impress anyone with how many logos you know. To leave you with a bag you can actually carry.

What this unlocks

Once you see the bag, the CLI command stops looking like a spell.

npx create-hackhaton-space-stack@latest my-app --frontend next --backend hono

That isn't "install Next." That's "pack these, leave the rest on the shelf, give me a project I can run."

Without a stack, you spend the first hour installing tools and the second hour googling why they hate each other. With one, you spend the first hour on the idea.

That's the leap. The stack is not the product. It's the bag that lets you leave the house.