uid	cogitave.templates.overview
title	templates — golden-path starter scaffolds
description	One repo, one directory per starter template — the golden path a new Cogitave repo is born from, plus a per-product-type add-on layered on top.
type	reference
owner	cogitave/platform
lastReviewed	2026-07-08

templates

Every Cogitave starter scaffold lives here, one directory per template - not one GitHub repo per template. This is deliberate: a public org with a repo-per-template quickly turns into dozens of near-identical, low-traffic repos that clutter the org's real product list. Established public orgs keep starters in a single, curated, browsable collection instead (e.g. Vite ships its create-vite templates as directories inside one repo, not as separate top-level repos).

Directories

Directory	For
base	Every repo starts here - engineering standards, CI, hooks, docs-as-code.
agent	MCP server / agent (evals scaffold).
service	Containerized backend service.
library	Publishable library (Rust/TS/Go).
web	Marketing / web property.
docs	Docs / learn content repo.
infra	Provider-agnostic infra stack.
rust	Native Rust golden path.
go-service	Go service golden path.
frontend	TypeScript/React frontend golden path.
desktop	Native desktop shell + shared Rust core.
mobile	Native mobile shells + shared Rust core.

How a new repo is born

1. Copy base/ into the new repo, plus the per-type template matching the product type (e.g. base + rust for a native Rust service).
2. Update README.md, AGENTS.md, CHANGELOG.md for the project; add the owning team to CODEOWNERS; lefthook install.

See the project baseline for the full scaffold-to-Definition-of-Done chain.