gtmesh init
Scaffolds a complete mesh repo — config, reference tables, schemas, templates, foundation files, and the repo-local skills — into the current directory.
gtmesh init # a clean, demo-free mesh repo
gtmesh init --template acme # overlaid with the acme-integrations worked exampleWhat it does
init writes a full, documented mesh repo from the bundled scaffold template. Everything it writes is yours to tune to your domain — the structural-law gtmesh.config.yaml, the reference/ tables, the per-type page schemas, the templates/, the foundation/ voice files, and the .claude/skills/ skills (the writer, the quality gates, and the operator that drives the build loop).
A plain gtmesh init scaffolds a clean, demo-free repo — placeholder config, empty (header-only) reference tables, generic foundations and schemas. --template acme overlays the acme-integrations worked example so you have real content to learn the shape on; --list-templates shows what’s available.
The scaffolded gtmesh.config.yaml carries only the decisions a project should complete — its name, its site kind, its sections and domain axes, the routing rules, the demand floor, the page types. Every other setting resolves from a schema default the engine owns, which is why the file is short and why it keeps tracking the engine as gtmesh evolves. To see the full set of keys you could set, run gtmesh config describe rather than reading the file.
There’s no pre-init step. After init, open the repo in Claude Code and run the repo-local operator skill — it interviews you, validates demand first, then builds config and reference tables through the deterministic CLI verbs (config, reference, plan, apply), with a human gate on every judgement call. See the walkthrough.
Arguments & flags
| Option | Description | Default |
|---|---|---|
--force | Overwrite existing files instead of skipping them | off (skip existing) |
--template <name> | Overlay a worked-example template (e.g. acme) on the base scaffold | — (clean scaffold) |
--list-templates | List the available templates and exit | — |
The global --project <dir> chooses where to scaffold (default .).
Reads & writes
- Reads: the bundled scaffold template (and, with
--template, the named overlay). - Writes: the whole mesh repo —
gtmesh.config.yaml,reference/,schemas/,templates/,foundation/,.claude/skills/. - Committed: everything
initwrites is committed; it is your project.
Examples
mkdir acme-integrations && cd acme-integrations
gtmesh init --template acme # worked example to learn the shape
# …or a clean repo to build your own from scratch:
gtmesh init
gtmesh init --list-templates # see the available templatesRelated
- Platform: Discovery & harvest, Page types & schemas
- Guide: Before you start, Walkthrough, After init