shibumistack.dev

Roadmap

Building in public.

The plan is public while the stack settles. This page tracks what is decided, what ships first, and where the design is still open.

Now

Make the path clear

Brand, landing pages, CLI design, and the DX plan. The product promise is being narrowed before the package ships.

Next

Ship create-shibumi

Release the scaffolder with Minimal, Full-stack, and Static themes plus deploy config chosen during setup.

Then

Add owned extensions

Ship auth, email, uploads, payments, and admin as copied source with migrations and agent guidance.

What is planned.

create

create-shibumi. A Bun-first scaffolder with prompts for template, deploy target, git, and dependencies.

themes

Minimal, Full-stack, Static. Different starts for different projects, not one template forced everywhere.

deploy

Config generated up front. Cloudflare, Vercel, Fly.io, static CDN, and self-hosted Bun with Docker.

data

SQLite by default. Drizzle handles schema, queries, and migrations. The production driver follows the target.

state

Nanostores for shared state. Use Alpine inside a component. Use a store only when state is shared.

core

CSRF included. Security defaults should not be an optional extension.

extensions

Copy code, not dependencies. Auth, Resend email, uploads, payments, and admin are added explicitly and owned by the app.

agents

agents.md fragments. Each extension can append local instructions so coding agents know the conventions.

server

shibumi-server. A VPS deploy service that verifies signed GitHub pushes, checks host capacity, validates the deployment config, builds with rootless Podman, replaces the old container, checks the new one's health, keeps the previous two images for quick rollbacks, and removes older ones. App-owned tests are optional. Secrets and machine inventory stay on the server.

渋み Get started

When we have the package, you'll run this in your terminal to scaffold a new project.

bun create shibumi@latest

or npm create shibumi@latest