// Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use azure-defaults), Bicep/Terraform patterns (use bicep-patterns or terraform-patterns).
| name | azure-artifacts |
| description | Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use azure-defaults), Bicep/Terraform patterns (use bicep-patterns or terraform-patterns). |
| compatibility | Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool. |
| license | MIT |
| metadata | {"author":"jonathan-vella","version":"2.0","category":"workflow-automation"} |
Single source of truth for artifact template structures and styling.
Per-step H2 definitions live in references/ — load only the step
you are generating.
| Rule | Requirement |
|---|---|
| Template skeleton | Read step template from references/ and replicate |
| Exact text | Use H2 text from templates verbatim |
| Exact order | Required H2s appear in the order listed |
| Anchor rule | Extra sections allowed ONLY after last required H2 |
| No omissions | Every H2 listed must appear in output |
| Attribution | > Generated by {agent} agent | {YYYY-MM-DD} |
agent-output/{project}/Every project in agent-output/{project}/ MUST have a
README.md.
After saving step artifact(s), update the README:
## ✅ Workflow Progress## 📄 Generated ArtifactsLast Updated date and progress bar percentageAll templates use single-brace {placeholder-name} syntax:
{project-name}, {monthly-cost}{{double-braces}}npm run lint:artifact-templates # H2 order and required headings
npm run lint:h2-sync # Template ↔ artifact sync
npm run validate:all # All validators together
agent-output/{project}/ with correct name<details open> block after badge row)<details> blocks present (if template contains them)When generating a Step N artifact, read the corresponding template:
| Reference | When to Load |
|---|---|
references/01-requirements-template.md | Generating Step 1 requirements |
references/02-architecture-template.md | Generating Step 2 assessment or Step 3 cost estimate |
references/04-plan-template.md | Generating Step 4 plan, governance, or preflight |
references/05-code-template.md | Generating Step 5 implementation reference |
references/06-deploy-template.md | Generating Step 6 deployment summary |
references/07-docs-template.md | Generating Step 7 workload documentation |
references/styling-standards.md | Applying callouts, badges, emoji, navigation |
references/cost-estimate-sections.md | Cost estimate H2 structure and formatting rules |
Shared IaC deploy patterns for Bicep and Terraform deploy agents: deployment strategies, circuit breaker, known deploy issues. For preflight validation (auth, governance, stop rules), see azure-validate. USE FOR: Phased deployment, circuit breaker, deploy-specific known issues. DO NOT USE FOR: Preflight validation (use azure-validate), code generation (use azure-bicep-patterns or terraform-patterns).
Reusable Azure Bicep patterns: hub-spoke, private endpoints, diagnostics, AVM composition. USE FOR: Bicep template design, hub-spoke networking, private endpoint patterns, AVM modules. DO NOT USE FOR: Terraform code, architecture decisions, troubleshooting, diagram generation.
Azure infrastructure defaults: regions, tags, naming (CAF), AVM-first policy, security baseline, unique suffix patterns. USE FOR: any agent generating or planning Azure resources. DO NOT USE FOR: artifact template structures (use azure-artifacts), pricing lookups (read references/pricing-guidance.md on demand).
Execute Azure deployments for ALREADY-PREPARED applications that have existing infra/{iac}/{project}/.azure/plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires infra/{iac}/{project}/.azure/plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
ROUTING SKILL — delegates to specialized diagram skills. USE FOR: any diagram request when the caller does not know which tool to use. Routes to drawio, python-diagrams, or mermaid based on diagram type.
Prepare Azure apps for deployment (infra Bicep/Terraform, azure.yaml, Dockerfiles). Use for create/modernize or create+deploy; not cross-cloud migration (use azure-cloud-migrate). WHEN: "create app", "build web app", "create API", "create serverless HTTP API", "create frontend", "create back end", "build a service", "modernize application", "update application", "add authentication", "add caching", "host on Azure", "create and deploy", "deploy to Azure", "deploy to Azure using Terraform", "deploy to Azure App Service", "deploy to Azure App Service using Terraform", "deploy to Azure Container Apps", "deploy to Azure Container Apps using Terraform", "generate Terraform", "generate Bicep", "function app", "timer trigger", "service bus trigger", "event-driven function", "containerized Node.js app", "social media app", "static portfolio website", "todo list with frontend and API", "prepare my Azure application to use Key Vault", "managed identity".