one templates

one templates lists every template in the registry. In a terminal it prints human-readable output; when piped or used with -o json, it returns structured data.

Usage

one templates [-o <fmt>]

Arguments

Argument	Description
-o, --output <fmt>	json / yaml / text; default is TTY-aware auto detection

Interactive Mode

one templates does not have a wizard. It only lists templates. Humans see readable terminal output; scripts and agents use -o json to read template IDs, categories, and compatible backends.

To choose a template interactively, use one add.

Output (schema one-cli/templates/v1)

{
  "schema": "one-cli/templates/v1",
  "templates": [
    {
      "id": "nestjs-api",
      "code": "ne",
      "category": "backend",
      "name": "NestJS API service",
      "description": "NestJS + TypeScript for API services and business backends",
      "toolchain": "node",
      "tags": ["api", "nestjs", "typescript", "backend"],
      "domains": {
        "container": { "default": "docker", "compat": ["docker"] },
        "deploy": { "default": "kustomize", "compat": ["kustomize"] }
      }
    },
    {
      "id": "go-api",
      "code": "go",
      "category": "backend",
      "name": "Go API service",
      "toolchain": "go"
    },
    // ... 8 more
  ]
}

Complete Template List

The current registry has 10 templates:

ID	Category	Details
nestjs-api	backend	->
go-api	backend	->
astro-site	frontend	->
starlight-docs	frontend / docs	->
nextjs-app	frontend	->
react-spa	frontend	->
expo-mobile	frontend / mobile	->
ts-library	library	->
go-lib	library	->
electron-app	frontend / desktop	->

Not sure which one to pick? Read the template decision tree.

Examples

Human Output

one templates

Agent / Script

# All template IDs
one templates -o json | jq -r '.templates[].id'

# Filter by category
one templates -o json | jq '.templates[] | select(.category == "backend")'

# Inspect a selected template
one templates -o json | jq '.templates[] | select(.id == "nestjs-api")'

Common Errors

Code	Recovery
REGISTRY_FETCH_FAILED	Network issue; inspect the registry URL in context
REGISTRY_INVALID	Registry JSON is malformed; contact the maintainer
REGISTRY_NOT_FOUND	Registry path does not exist
NO_TEMPLATES	Registry is empty; this should not normally happen

Full table: Error codes.

Next

• Template decision tree — choose the right template
• one add — add the selected template to a workspace