I’ve built a kanban board, a reporting tool, and a scheduling manager, and I’m getting tired of setting up user accounts, login, a database, a styled frontend, and an API server every time.
So today, I pulled the shared parts into a template called Spernakit. The name is an acronym - SQLite, Prisma, Express, React, and Node, plus ‘akit’, as in SPERN-a-kit. (I never claimed to be good at naming things.) It’s the stack August’s throwaway projects helped narrow down. I can clone it to start the next app.
Every new app stress-tests the foundation and improvements flow back into the template for the others to inherit. There’s already a backlog against it - better notifications, user profiles, performance, hardening, request tracking, health monitoring, and shutting the server down without losing data.
The useful part is that a login bug I fix in the kanban board can go back into the template and on to the reporting tool. Keeping those copies in sync will be its own bit of work, but at least I know which parts I keep rebuilding. Three apps was enough to make that fairly obvious.