trak init
Fetches official or community blueprints from trak-registry and recursively materializes the entire workspace directory tree on disk.
Command Overview
Supports official templates (e.g. 'trak init lang/go'), explicit namespace ('trak init trak/lang/go'), community author tracks ('trak init <username>/<category>/<tool>'), and pinned version releases ('trak init <username>/<category>/<tool>@<version>'). If --path is omitted, it defaults to './learn-<template>' in the current working directory.
Execution Lifecycle
Available Flags
Target directory path where the workspace will be materialized.
Show help message and command examples.
Usage Examples
Generates the official Go workspace in ./learn-go in your current folder.
Fetches community track from users/alice/db/postgres.json in the registry.
Pulls tagged release postgres@v2.0.0.json, preserving stability for learners.
Materializes the Rust workspace inside custom ./my-rust-lab directory.
Important Technical Guidelines
The initialization process generates a trak.json manifest at the root of the new folder. This receipt is essential for all tracking commands (trak verify, trak next, trak status, trak done).
Trak safely writes to target directories and preserves folder structure. Use the --path flag if you want to isolate workspaces in custom locations.