Add terramate skills (#51)

<!-- CURSOR_SUMMARY -->
> [!NOTE]
> <sup>[Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) is
generating a summary for commit
0d1b456. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: soerenmartius

.agents/skills/terramate-best-practices/AGENTS.md

@@ -0,0 +1,108 @@
+---
+name: terramate-best-practices
+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:
+  author: terramate
+  version: "1.0.0"
+---
+
+# 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-` |
+
+## Quick Reference
+
+### 1. CLI Fundamentals (CRITICAL)
+
+- `cli-stack-structure` - Organize stacks with clear directory structure
+- `cli-stack-config` - Configure stacks with proper stack blocks
+- `cli-stack-metadata` - Use metadata for stack identification and filtering
+
+### 2. CLI Orchestration (HIGH)
+
+- `cli-orchestration-run` - Run commands across stacks efficiently
+- `cli-orchestration-change-detection` - Use change detection to limit execution scope
+- `cli-orchestration-parallel` - Leverage parallel execution for independent stacks
+- `cli-orchestration-dependencies` - Manage stack dependencies and execution order
+
+### 3. CLI Code Generation (HIGH)
+
+- `cli-codegen-hcl` - Use generate_hcl for DRY Terraform code
+- `cli-codegen-file` - Use generate_file for file generation patterns
+- `cli-codegen-provider` - Generate provider configurations dynamically
+
+### 4. CLI Configuration (MEDIUM-HIGH)
+
+- `cli-config-globals` - Use globals for shared configuration across stacks
+- `cli-config-lets` - Use lets for stack-local computed values
+- `cli-config-metadata` - Leverage metadata for stack information
+
+### 5. Terramate Cloud (MEDIUM-HIGH)
+
+- `cloud-integration` - Set up Cloud connection and authentication
+- `cloud-drift-management` - Configure drift detection and reconciliation
+- `cloud-observability` - Use Cloud dashboard for stack visibility
+
+### 6. Terramate Catalyst (MEDIUM)
+
+- `catalyst-components` - Create reusable component blueprints
+- `catalyst-bundles` - Define bundles for component composition
+- `catalyst-instantiation` - Instantiate bundles correctly
+
+### 7. CI/CD Integration (MEDIUM)
+
+- `cicd-github-actions` - Set up GitHub Actions workflows
+- `cicd-preview-workflows` - Create preview workflows for PRs
+- `cicd-deployment-workflows` - Configure deployment automation
+
+### 8. Advanced Patterns (LOW-MEDIUM)
+
+- `advanced-workflows` - Create complex multi-step workflows
+- `advanced-codegen-patterns` - Advanced code generation techniques
+
+## How to Use
+
+Read individual rule files for detailed explanations and code examples:
+
+```
+rules/cli-stack-structure.md
+rules/cli-orchestration-run.md
+rules/cli-codegen-hcl.md
+rules/cloud-integration.md
+rules/catalyst-components.md
+```
+
+Each rule file contains:
+- Brief explanation of why it matters
+- Incorrect/anti-pattern example with explanation
+- Correct/best practice example with explanation
+- Additional context and references
+
+## Full Compiled Document
+
+For the complete guide with all rules expanded: `AGENTS.md`

.agents/skills/terramate-best-practices/SKILL.md

@@ -0,0 +1,148 @@
+# catalyst-bundles
+
+**Priority:** MEDIUM  
+**Category:** Terramate Catalyst
+
+## Why It Matters
+
+Bundles compose multiple components into ready-to-use, deployable units. They abstract infrastructure complexity and enable developers to provision complete solutions without deep infrastructure knowledge.
+
+## Incorrect
+
+```hcl
+# Developers manually compose components
+# No standardization
+# Missing dependencies
+# Inconsistent patterns
+
+# app-team/stack.tm.hcl
+tm_bundle "database" {
+  component = "rds-postgres"
+  # ...
+}
+
+tm_bundle "cache" {
+  component = "redis"
+  # ...
+}
+
+tm_bundle "storage" {
+  component = "s3-bucket"
+  # ...
+}
+
+# Missing: VPC, networking, security groups
+# Missing: Component dependencies
+# Missing: Consistent configuration
+```
+
+**Problem:** Manual composition, missing dependencies, inconsistent patterns, developers need deep infrastructure knowledge.
+
+## Correct
+
+**Bundle definition:**
+
+```hcl
+# bundles/web-app/bundle.tm.hcl
+bundle {
+  name        = "web-app"
+  description = "Complete web application infrastructure"
+  
+  component "networking" {
+    source = "vpc"
+    input = {
+      cidr_block = "10.0.0.0/16"
+    }
+  }
+  
+  component "database" {
+    source = "rds-postgres"
+    input = {
+      instance_class = "db.t3.micro"
+      allocated_storage = 20
+    }
+    
+    depends_on = ["networking"]
+  }
+  
+  component "cache" {
+    source = "redis"
+    input = {
+      node_type = "cache.t3.micro"
+    }
+    
+    depends_on = ["networking"]
+  }
+  
+  component "storage" {
+    source = "s3-bucket"
+    input = {
+      name = "${bundle.name}-storage"
+    }
+  }
+  
+  component "compute" {
+    source = "ecs-service"
+    input = {
+      cluster_name = "${bundle.name}-cluster"
+      vpc_id       = component.networking.output.vpc_id
+      subnet_ids   = component.networking.output.private_subnet_ids
+    }
+    
+    depends_on = ["networking", "database", "cache"]
+  }
+}
+```
+
+**Bundle instantiation:**
+
+```hcl
+# stacks/prod-web-app/stack.tm.hcl
+stack {
+  name = "prod-web-app"
+}
+
+# Instantiate bundle
+tm_bundle "web-app" {
+  bundle = "web-app"
+  
+  input = {
+    # Bundle-level overrides if needed
+  }
+}
+```
+
+**Benefits:**
+- Complete solutions in one bundle
+- Automatic dependency management
+- Consistent patterns across teams
+- Abstracted complexity
+- Easy to instantiate
+- Platform team maintains bundles
+
+## Additional Context
+
+Bundle composition:
+- Combines multiple components
+- Manages component dependencies
+- Provides bundle-level configuration
+- Supports component outputs as inputs
+
+Bundle vs Component:
+- **Component** - Single infrastructure resource/pattern
+- **Bundle** - Multiple components composed together
+- Use bundles for complete solutions
+- Use components for individual resources
+
+Converting existing Terraform modules to components:
+- Run `terramate component create` inside an existing Terraform module directory
+- This automatically generates the component structure from your module
+- Converts module variables to component inputs
+- Converts module outputs to component outputs
+- Preserves existing Terraform code
+
+## References
+
+- [Terramate Catalyst Bundles](https://terramate.io/docs/catalyst/concepts/bundles/)
+- [Instantiate Your First Bundle](https://terramate.io/docs/catalyst/tutorials/instantiate-your-first-bundle/)
+- [Bundle Definition](https://terramate.io/docs/catalyst/reference/bundle-definition/)