Concepts
Mental models shared by SKMTC users and generator authors. These pages are routed just-in-time from the tutorials and how-to guides — read the one a task links you to; this is not a syllabus.
Start here
- Definitions and files — the create-or-reuse mechanism that makes SKMTC composable, in one page
- The three phases — Parse → Generate → Render
Using SKMTC
- Projects and workspaces — the on-disk model
- Clone vs install — the customization gradient
- Enrichments — per-operation configuration
- The worker runtime — the sandbox model
- The manifest — the run record
Authoring generators
- Generators as packages — the package layout
- Projections and Snippets — the two-level DSL
- How generators produce output — the pull-based model
- Composing output with Stringable — how templates compose
- Cross-generator coordination — memoized composition
- Files, deduplication, and integrity — the file object in depth
- The type system — schema-to-value dispatch
- Variants — one source item, several artifacts
- The GraphQL pipeline — the SDL path
- Languages — where the target language enters
Design system across many APIs
Architectural pattern for sharing a customized generator set across multiple APIs (multiple projects, multiple repos, or multiple teams).
The three phases
A generation run is a pipeline of three sequential phases — Parse, Generate, and Render — each producing an immutable artifact the next consumes.