The DeesseJS Manifesto
Software that builds software.
Six beliefs that shape how we design templates, ship defaults, and think about the agentic era.
- Last updated
- 2026-08-04
- Beliefs
- 6
- Reading time
- ~ 5 min
DeesseJS is the main app of a small team building the templates, contracts, and tooling we wished existed when we shipped our last product. We work in public, in the open, and in the same stack most of our readers will reach for tomorrow.
These six beliefs are the rules we hold each other to when the easy call is to ship something less careful. They are not a manifesto in the sense of a manifesto being authoritative — they are the document we rewrite whenever we need to remember why we're here.
Agents are the developers now
The next platform shift is autonomous agents shipping production code. Templates should be shaped for the agents that ship them — clear boundaries, machine-readable metadata, hooks over conventions. If a template can't be navigated by a coding agent, it isn't done.
Opinionated defaults, modular everything
We pick the stack — Next.js, Better Auth, Drizzle, shadcn/ui, Tailwind v4 — and we ship it wired. Every primitive is removable without breaking the rest. The opinions give speed; the modularity gives longevity.
Speed is the feature
A good template lands in minutes, debugged in seconds, understood in a single read. We treat every file that survived PR review as a place where someone will live for the next three years. Documentation in the file beats documentation in a wiki.
The CLI is the product surface
A discoverable, composable CLI — `deessejs init`, `deessejs list`, `deessejs update` — is how developers adopt a system. We invest in the terminal because that's where the time adds up. The web surface is where humans browse; the CLI is where they ship.
Open source, with guardrails
DeesseJS templates, contracts, and the CLI are MIT. The brand, the marketplace positioning, and the curated registry stay ours. The source-code ecosystem is shared; the product surface is owned.
Ship the smallest useful thing
We don't wait for the full vision to release the first slice. Templates, the registry, the SDK — they land as they become useful, and they evolve in the open. The roadmap is a public draft. The community is part of how we build, not who we build for.