style-guide

Consolidate infrastructure styling guidelines for blueprints, Terraform, and naming.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/poc-micro-frontends/terraform-infrastructure --skill style-guide-poc-micro-frontends
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-guide
Source: https://github.com/poc-micro-frontends/terraform-infrastructure/tree/main/skills/style-guide
Command: npx skills add https://github.com/poc-micro-frontends/terraform-infrastructure --skill style-guide-poc-micro-frontends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes infrastructure styling guidelines to streamline decision-making and ensure consistent patterns across blueprints, Terraform code, and architectural choices.

Core Features & Use Cases

  • Decision workflow and priority-based guidance for security, cost, naming, and code quality.
  • Catalog references, naming conventions, and tagging standards to enforce consistency across environments.
  • Architecturally-informed best practices for blueprint selection, resource organization, and code patterns.

Quick Start

Review project requirements and apply the catalog and priority guidance to align naming, security, and Terraform patterns.

Frequently Asked Questions about style-guide

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

FAQPage Schema
What are infrastructure style guidelines for Terraform?

Infrastructure style guidelines are standardized rules for resource naming, tagging, and code quality that ensure consistent Terraform patterns and architectural choices across multiple environments and teams.

How do I standardize resource naming conventions across cloud environments?

You can standardize resource naming by applying centralized catalog references and priority-based guidance to align naming tags and security patterns across all your cloud environments.

How do I prioritize security and cost when selecting infrastructure blueprints?

Prioritize security and cost by following a decision workflow that enforces priority-based guidance for security, cost, naming, and code quality during blueprint selection and architectural planning.

Can I use these styling guidelines for existing Terraform codebases?

Yes, you can apply the architecturally-informed best practices and catalog references to existing Terraform codebases to enforce code quality, resource organization, and consistent coding patterns.

What is the best way to reduce decision friction in infrastructure architecture?

The best way to reduce decision friction is to consolidate infrastructure styling guidelines into a centralized reference, streamlining blueprint selection and architectural decisions across teams.

When should I not use a centralized infrastructure style guide?

A centralized infrastructure style guide may not suit isolated projects requiring highly customized architectural decisions outside standard security, cost, and naming conventions applied across multiple teams.