infra-conventions

Standardizes Terraform and AWS infrastructure conventions for multi-environment deployments.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/johwer/marketplace --skill infra-conventions-johwer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-conventions
Source: https://github.com/johwer/marketplace/tree/main/skills/infra-conventions
Command: npx skills add https://github.com/johwer/marketplace --skill infra-conventions-johwer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lack of standardized infrastructure practices leads to misconfigurations, security gaps, and inconsistent deployments. This skill codifies Terraform and AWS conventions, CI/CD standards, monitoring patterns, and security practices to improve reliability, audibility, and maintainability.

Core Features & Use Cases

  • Terraform conventions: one module per logical resource group, strict provider pinning, lock files, descriptive variables and outputs, and safe state management.
  • AWS conventions: enforce security via KMS keys, SSL enforcement, ECR scanning, least-privilege access, and monitoring integrations.
  • WAF, monitoring, and CI/CD guidance: standardized WAF rate limiting, CloudWatch alarms, SNS notifications, and GitHub Actions workflow guardrails.
  • RDS/ECR/RDW security and naming: naming conventions, encryption, backups, rotation, and access controls.
  • CI/CD workflows: separate pipelines for plan/apply, codeowners, and automated quality checks tied to infra changes.
  • Automated quality scripts: provide scripts to audit infra plans and validate workflows.
  • Use with existing platforms to enforce governance across environments (dev/accept/prod).

Quick Start

Apply these conventions to Terraform and AWS projects to enforce standardized infrastructure practices across environments and teams.

Frequently Asked Questions about infra-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce standardized Terraform conventions for AWS infrastructure?

To enforce standardized Terraform conventions for AWS, apply strict provider pinning, use lock files, maintain safe state management, and structure one module per logical resource group to improve security and reliability.

What are the best practices for securing AWS resources and ECR in CI/CD pipelines?

Securing AWS resources and ECR in CI/CD pipelines requires enforcing least-privilege access, enabling ECR image scanning, applying KMS encryption, and separating plan and apply workflows with automated quality checks.

Does this infra conventions approach work for multi-environment Terraform deployments?

Yes, this infra conventions approach works for multi-environment Terraform deployments by codifying governance across dev, accept, and prod environments to ensure consistent security, reliability, and auditing standards.

How do I configure CloudWatch alarms and WAF rate limiting for AWS infrastructure?

Configuring CloudWatch alarms and WAF rate limiting involves setting standardized WAF rate limits, defining CloudWatch alarm thresholds, and configuring SNS notifications to centralize monitoring for your AWS infrastructure.

Can I automate Terraform plan auditing and workflow validation for compliance?

Yes, you can automate Terraform plan auditing and workflow validation using provided quality scripts that check infra plans and validate GitHub Actions workflows to meet strict compliance and governance needs.

Why do I need strict provider pinning and lock files for Terraform state management?

Strict provider pinning and lock files are needed for Terraform state management to prevent unexpected breaking changes from upstream providers, ensuring maintainable, reliable, and auditable infrastructure deployments.