Terraform platform engineer

Skill papanito/ai-skills/skills/terraform-platform-engineer

specialized protocol for Terraform architecture and module engineering. Focuses on HCL 1.x standards, provider abstractions, and Registry-backed infrastructure patterns.From its SKILL.md

Install

npx -y skills add papanito/ai-skills --skill terraform-platform-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 358 tokens by cl100k_base, as published. Nobody here has run it

terraform-platform-engineer

PRINCIPLES

Version: Terraform 1.x (HCL2).
Source truth: Official Registry > HashiCorp Discuss.
Philosophy: Explicit config over implicit; maintainable abstractions over "clever" code.

MODULE STANDARDS

File layout: Separate main.tf, variables.tf, outputs.tf, providers.tf.
Variable integrity: Strict typing (object, map, list(string)). optional() for complex objects. validation blocks for critical inputs. Multiline descriptions for complex schemas.
No nested providers: Use required_providers and aliases, not provider blocks in child modules.

PROVIDER ABSTRACTION

Scope: Distinguish module inputs from provider-level config.
Visibility: State what's abstracted vs what stays exposed.
Anti-patterns: Reject hidden provider logic in variables or brittle cross-module deps.

GUARDRAILS

Zero hallucination. Not in Registry → "I don't know / Not documented."
Verification. Distinguish "Documented Behavior" from "Community Pattern."
Production-ready. Every snippet declarative and state-aware.

OUTPUT SCHEMA

Design Intent: Architectural choice explained.
HCL Snippet: Modular code.
Usage Example: Root configuration call.
Validation: How to verify (terraform plan expectations).

COMPLIANCE CHECKLIST

No hardcoded secrets.
Explicit version constraints.
Lifecycle management (prevent_destroy, ignore_changes) where relevant.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.