Specs are meant to be customized. Trellis ships with empty spec templates by default — they are placeholders for your project’s conventions. Every team’s stack, patterns, and quality bar are different, so the specs you write should reflect your actual codebase, not generic best practices. Templates from the marketplace give you a head start, but always tailor them to your project.
Available Templates
| Template | Stack | Description |
|---|---|---|
| Electron + React + TypeScript | Full-stack | Electron desktop app with React frontend |
| Next.js + oRPC + PostgreSQL | Full-stack | Next.js app with oRPC API and PostgreSQL |
| CF Workers + Hono + Turso | Full-stack | Cloudflare Workers with Hono and Turso |
Download Electron Template
Electron + React + TypeScript (50 files)
Download Next.js Template
Next.js + oRPC + PostgreSQL (35 files)
Download CF Workers Template
CF Workers + Hono + Turso (38 files)
Template Marketplace v0.3.6
Starting from v0.3.6, you can fetch spec templates directly from any Git repository using the--registry flag:
How it works
Trellis auto-detects two modes:- Marketplace mode: If the repository contains a
marketplace/index.jsonfile, Trellis reads the template index and lets you pick which template to install - Direct download mode: If no
index.jsonis found, Trellis treats the entiremarketplace/specs/directory as a single template and downloads it directly
Publishing your own templates
To create a spec template registry that others can use with--registry:
- Create a Git repository (GitHub, GitLab, or Bitbucket)
- Add a
marketplace/directory with your spec templates - Create
marketplace/index.jsonto list available templates:
- Inside each template path, place your spec files following the standard structure (see below)
- Share the repository URL — users install with
trellis init --registry <url>
Template Structure
Each template follows this structure:How to Use
- Download the template ZIP or use
trellis init --registry - Extract to
.trellis/spec/in your project - Customize for your project’s specific conventions
- Remove sections that don’t apply
- Update paths and examples to match your codebase