Devcontainers, crafted from parts that fit together.

Every repo in this org is a starter template: a runtime wired into a devcontainer, with a set of infrastructure services you can add, remove, or swap without re-plumbing the rest of the project. Use one as-is, or fork it and change the panels you need changed.

• A shared base. template-base is the frame every repo here starts from: devcontainer, CI, hooks, the Claude Code workflow, a release Makefile contract, and template-sync. It has no runtime.
• A runtime on top. Each runtime template is an instance of base that adds its language and, for the backends, independent panels under .devcontainer/stack/: one compose stanza per service, documented on its own. It is in turn a template for your project.
• Updates flow down. Fixes land in base, reach the runtime templates, and then your project, each hop as a template-sync PR.
• Nothing you don't ask for. Panels are opt-in. A template with six supported services doesn't run six containers unless your project needs them.

1. Pick the closest template repo below and click Use this template.
2. Open in your devcontainer — the stack starts with the default panels wired in.
3. Read that repo's docs/TEMPLATE.md for what's included and how to swap a panel.

Start from template-base for a repo with no runtime of its own, or one in a language with no template yet.

Built AI-assisted. These templates are developed with Claude Code — plans, changes, and checks are tracked in-repo so the reasoning behind a template's structure is as visible as the code.

Have a stack to propose? Open an issue on the relevant repo describing the runtime or service and how it composes with the existing frame — panels are reviewed for whether they stay independent, not just whether they work.

Brand assets (logo, palette, type) live in brand/.