by hashicorp
Use the provider-actions skill to implement Terraform Provider actions with the Plugin Framework for backend development. It covers lifecycle-based imperative behavior, repository file layout, schema shape, tests, docs, and changelog guidance.
by hashicorp
The new-terraform-provider skill helps backend and infrastructure developers scaffold a new Terraform provider with the Plugin Framework. It guides workspace creation, Go module setup, main.go wiring, and build/test validation for a clean provider bootstrap.
by hashicorp
terraform-stacks is a practical skill for HashiCorp Terraform Stacks. Use it to create, modify, and validate .tfcomponent.hcl and .tfdeploy.hcl files, wire components and deployments, manage multi-environment or multi-region infrastructure, and troubleshoot Stack syntax, dependencies, and layout. Strong fit for backend development and platform engineering workflows.
by hashicorp
refactor-module skill for Refactoring monolithic Terraform into reusable modules with clear inputs, outputs, encapsulation, and state migration planning.
by hashicorp
terraform-test is a practical guide for writing and running Terraform tests with .tftest.hcl files, run blocks, assertions, mocks, and CI-friendly workflows. Use it to validate module outputs, resource arguments, conditional logic, and plan or apply behavior before merge.
by hashicorp
terraform-style-guide helps generate and review Terraform HCL using HashiCorp style conventions, file layout, and security-minded defaults. Use it for Terraform-native code generation, module structure, variables, outputs, and safer configuration in real repositories.
by hashicorp
provider-resources is a Terraform Provider development skill for implementing resources and data sources with the Plugin Framework. Use it for CRUD operations, schema design, state management, and acceptance testing in backend development workflows.
by hashicorp
The provider-docs skill helps you create, update, and verify Terraform Registry documentation for Terraform providers. Use it for provider-docs guide work, provider-docs for Technical Writing, and for keeping schema descriptions, tfplugindocs templates, and Registry output in sync when docs change.
