| name | terramate-expert | ||||||
|---|---|---|---|---|---|---|---|
| description | Terramate CLI, Cloud, and Catalyst best practices and usage guides. This skill should be used when working with Terramate stacks, orchestration, code generation, Cloud integration, or Catalyst components and bundles. | ||||||
| license | MIT | ||||||
| metadata |
|
Comprehensive guide for Terramate CLI, Cloud, and Catalyst, maintained by Terramate. Contains best practices and usage patterns for stack management, orchestration, code generation, Cloud integration, and Catalyst components/bundles.
Reference these guidelines when:
- Creating and organizing Terramate stacks
- Orchestrating commands across multiple stacks
- Using code generation to keep configurations DRY
- Integrating with Terramate Cloud for observability
- Creating Catalyst components and bundles
- Setting up CI/CD workflows with Terramate
- Managing stack dependencies and execution order
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | CLI Fundamentals | CRITICAL | cli- |
| 2 | CLI Orchestration | HIGH | cli-orchestration- |
| 3 | CLI Code Generation | HIGH | cli-codegen- |
| 4 | CLI Configuration | MEDIUM-HIGH | cli-config- |
| 5 | Terramate Cloud | MEDIUM-HIGH | cloud- |
| 6 | Terramate Catalyst | MEDIUM | catalyst- |
| 7 | CI/CD Integration | MEDIUM | cicd- |
| 8 | Advanced Patterns | LOW-MEDIUM | advanced- |
cli-stack-structure— Organize stacks with clear directory structurecli-stack-config— Configure stacks with proper stack blockscli-stack-metadata— Use metadata for stack identification and filtering
cli-orchestration-run— Run commands across stacks efficientlycli-orchestration-change-detection— Use change detection to limit execution scopecli-orchestration-parallel— Leverage parallel execution for independent stackscli-orchestration-dependencies— Manage stack dependencies and execution order
cli-codegen-hcl— Usegenerate_hclfor DRY Terraform codecli-codegen-file— Usegenerate_filefor file generation patternscli-codegen-provider— Generate provider configurations dynamically
cli-config-globals— Use globals for shared configuration across stackscli-config-lets— Use lets for stack-local computed valuescli-config-metadata— Leverage metadata for stack information
cloud-integration— Set up Cloud connection and authenticationcloud-drift-management— Configure drift detection and reconciliationcloud-observability— Use Cloud dashboard for stack visibility
catalyst-components— Create reusable component blueprintscatalyst-bundles— Define bundles for component compositioncatalyst-instantiation— Instantiate bundles correctly
cicd-github-actions— Set up GitHub Actions workflowscicd-preview-workflows— Create preview workflows for PRscicd-deployment-workflows— Configure deployment automation
advanced-workflows— Create complex multi-step workflowsadvanced-codegen-patterns— Advanced code generation techniques
Apply rules by ID when working with Terramate configurations. Each rule ID maps to a specific pattern:
- CRITICAL rules — always apply; these are foundational to correct Terramate usage
- HIGH rules — apply by default for any orchestration or code generation task
- MEDIUM-HIGH rules — apply when configuring Cloud integration or complex globals
- MEDIUM rules — apply for CI/CD setup and Catalyst work
- LOW-MEDIUM rules — apply for advanced workflows and complex code generation
Read individual rule files in references/ for detailed explanations and code examples:
references/cli-stack-structure.md
references/cli-orchestration-change-detection.md
references/cli-codegen-hcl.md
references/cloud-integration.md
See references/rule-index.md for the full list of all rules mapped to their local files. Rules without a local file can be applied using the summary in the Quick Reference above.