Terramate Best Practices

This compiles best practices for Terramate's three main products: the CLI for stack orchestration and code generation, Cloud for drift detection and observability, and Catalyst for reusable infrastructure components. You'll want this when setting up stack hierarchies, running commands across multiple stacks with change detection, or generating Terraform configurations to stay DRY. The rules are prioritized by impact, from critical CLI fundamentals down to advanced workflow patterns. What stands out is the emphasis on orchestration over individual stack management. If you're already using Terramate and want to move past the basics, or you're evaluating it and need to understand the workflow philosophy, this covers the terrain.

skills.sh installs: 361
GitHub stars: 35
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add terramate-io/agent-skills --skill terramate-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

Terramate Best Practices

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.

When to Apply

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

Rule Categories by Priority

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-`