infra

Automate Azure infrastructure deployment with CAF-compliant Bicep templates.

Updated Apr 19, 2026

Search Tags:#azure #iac #naming #modular #bicep #caf

Ready to run

npx skills add https://github.com/lcmassena/AI_Skills --skill infra-lcmassena

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: infra
Source: https://github.com/lcmassena/AI_Skills/tree/main/hexagonal-architect/infra
Command: npx skills add https://github.com/lcmassena/AI_Skills --skill infra-lcmassena

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying Azure infrastructure consistently is complex without a standardized, modular approach; this skill provides a blueprint to implement CAF-aligned naming, modular Bicep templates, and environment-specific configurations.

Core Features & Use Cases

Modular Design: Separate files per resource type; reusable templates and clear composition.
CAF Naming & Environments: Enforces CAF naming conventions and supports DEV, QA, PROD deployments.
Parameterization & Outputs: Environment-specific parameters and exported outputs for integration.
What-If & Validation: Guidance to validate deployments before applying changes.
Use Case: Teams deploying multi-environment Azure infrastructure with Azure Bicep templates.

Quick Start

Create a main.bicep with parameterized modules and deploy using a dev parameter file.

Frequently Asked Questions about infra

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

FAQPage Schema

How do I deploy multi-environment Azure infrastructure using Bicep templates?▼

You deploy multi-environment Azure infrastructure using Bicep by structuring a modular main.bicep file with environment-specific parameter files. This approach supports DEV, QA, and PROD environments while enforcing CAF naming conventions and exporting outputs for integration.

What is a CAF-aligned naming convention for Azure Bicep deployments?▼

A CAF-aligned naming convention standardizes resource names across Azure deployments to ensure consistency. Using Bicep templates, this approach applies standardized naming across multi-environment setups and provides guidelines for resource validation before deployment.

Can I validate Bicep templates before applying changes to my Azure environment?▼

Yes, you can validate Bicep templates before applying changes by using What-If validation workflows. This Bicep deployment skill provides specific guidance on validation steps to test modular resource configurations and parameters safely prior to execution.

Does this Bicep approach support modular files for separate Azure resource types?▼

Yes, this Bicep approach supports modular design by using separate files for each Azure resource type. These reusable templates allow clear composition and parameterization, creating distinct main Bicep structures that integrate with environment-specific configurations.