Skip to content
Skills Library
DevOps & cloud · Building & coding

tf-web

/tf-web

Scaffold Terraform (Azure) for a web app running in a container, for UAT and prod, from a project prefix. Creates the resource group, Log Analytics, Container Apps environment, container registry, externally ingressed container app and state bootstrap doc, then offers optional add-ons (private or public blob storage, Foundry AI models, PostgreSQL). Use when the user wants infrastructure for a new web app or a new environment of one.

Repository
skills ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Scaffold Terraform (Azure) for a web app running in a container, for UAT and prod, from a project prefix. Creates the resource group, Log Analytics, Container Apps environment, container registry, externally ingressed container app and state bootstrap doc, then offers optional add-ons (private or public blob storage, Foundry AI models, PostgreSQL). Use when the user wants infrastructure for a new web app or a new environment of one.

Arguments

/tf-web [prefix]
Original author description

Scaffold Terraform (Azure) for a web app running in a container, for UAT and prod, from a project prefix. Creates the resource group, Log Analytics, Container Apps environment, container registry, externally ingressed container app and state bootstrap doc, then offers optional add-ons (private or public blob storage, Foundry AI models, PostgreSQL). Use when the user wants infrastructure for a new web app or a new environment of one.

How it works

  1. Steps
  2. Notes
Original SKILL.md headings · 26 lines, 235 words
SKILL.md preview
---
name: tf-web
description: Scaffold Terraform (Azure) for a web app running in a container, for UAT and prod, from a project prefix. Creates the resource group, Log Analytics, Container Apps environment, container registry, externally ingressed container app and state bootstrap doc, then offers optional add-ons (private or public blob storage, Foundry AI models, PostgreSQL). Use when the user wants infrastructure for a new web app or a new environment of one.
argument-hint: [prefix]
---

# Terraform: web app

Create the Terraform for a containerised web app, one directory per environment.

## Steps

1. Read [../_shared/terraform-base.md](../_shared/terraform-base.md) and follow it with `service` = `web`. Check the repo's existing layout and `CLAUDE.md` conventions first.
2. Collect the inputs. The first argument, if given, is the `prefix`.
3. Ask which add-ons to include, all optional:
   - Blob storage: private, public, both or none (`/tf-blob`)
   - Foundry AI models (`/tf-foundry`)
   - PostgreSQL (`/tf-pgsql`)
   For each chosen add-on, ask its own inputs now, as that skill lists them.
4. **Confirm** the plan before writing: the directories, the files, the generated names, and the add-ons.
5. Write the base files for each environment, using this skill's [container_app.tf.tmpl](container_app.tf.tmpl) and appending [vars-extra.tf.tmpl](vars-extra.tf.tmpl) to `vars.tf`.
6. Apply each chosen add-on to each environment by following its skill's "Add" steps, reusing the inputs already collected. The add-ons assume the base files above exist.
7. Write or extend `docs/state-bootstrap.md` and `.gitignore`.
8. Run the checks from the base doc and report.

## Notes

- The ingress is external on port 8080 (`ingress_target_port`). Change it to the port the app listens on.
- The container runs the Microsoft quickstart image as a placeholder. `ignore_changes` on the image stops Terraform fighting the app pipeline.
- The names the app pipeline hardcodes (resource group, container app, registry) are listed in the final report so they can be recorded as the contract with the application.
Files in this package (3)
  • SKILL.md 2 KB
  • container_app.tf.tmpl 1 KB
  • vars-extra.tf.tmpl 1 KB

Versions

The database has no other skills named tf-web.

Database snapshot: 13.11.2026 · package version 9867aedc187a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90tf-worker
    Scaffold Terraform (Azure) for a console worker running in a container, for UAT and prod, from a project prefix. Same base as the web app but with no ingress, plus optional add-ons (private or public blob storage, Foundry AI models, PostgreSQL). Use when the user wants…
  • 90tf-blob
    Add Azure blob storage to an existing Terraform web or worker environment created by tf-web or tf-worker, private, public (anonymous read of blobs) or both. Use when the user wants file or asset storage on an existing service.
  • 100aztfexport
    Use when exporting existing Azure resources to Terraform using aztfexport. Triggers on aztfexport, Azure import to Terraform, export Azure resource, bring Azure under Terraform management, reverse-engineer Azure infrastructure, bootstrap IaC from live Azure resources. Covers…
  • 100terraform-azure
    Provision Azure infrastructure with Terraform. Configure providers, manage state, and deploy resources. Use when implementing IaC for Azure.
  • 100terraform-azure
    Provision Azure infrastructure with Terraform. Configure providers, manage state, and deploy resources. Use when implementing IaC for Azure.
  • 100azure-integrations
    Azure deployment for web apps — Static Web Apps, App Service, Blob Storage, Bicep/ARM, GitHub Actions CI/CD. Use when deploying Next.js/Vite to Azure or configuring Azure resources for full-stack apps.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.