What problem does it solve? Writing a Terraform provider involves many moving parts — provider server setup, schema design, CRUD lifecycle, drift detection, acceptance testing, and Registry publishing — and getting any of them wrong leads to broken plans, lost state, or rejected releases. This Skill provides the conventions and patterns for doing it correctly with the modern Plugin Framework. ## Core Features & Use Cases - Provider & Schema Design: Structure the provider server, resources, and data sources with correct Required/Optional/Computed attributes, validators, and plan modifiers like UseStateForUnknown and RequiresReplace. - CRUD, State & Drift Detection: Implement Create/Read/Update/Delete with diagnostics, ImportState support, and proper RemoveResource handling so Terraform detects drift when remote objects disappear. - Testing & Publishing: Write TF_ACC-gated acceptance tests with terraform-plugin-testing, generate docs with tfplugindocs, and release via GoReleaser with GPG signing and terraform-registry-manifest.json. - Use Case: You need to add a new resource to your organization's Terraform provider. Use this Skill to scaffold the resource schema, implement CRUD against your API client, add an import test step, and wire the release pipeline for the Terraform Registry. ## Quick Start Use the terraform-provider skill to scaffold a new resource with schema, CRUD methods, and an acceptance test for my provider.
