scaffolding-azure-bicep-infrastructurelisted

# Scaffolding Azure Bicep Infrastructure Generates the Bicep + workflow files for a new Azure web app. Modular by default: every component (SQL, Storage, Observability) is an opt-in boolean toggle on `main.bicep`, so projects only provision what they actually use. ## When to invoke - New project: generate `infra/`, `infra/environments/`, `.github/workflows/` - Existing project: add a new module or refactor into the modular-toggle pattern ## Workflow checklist Copy this checklist into your response and check items off as you complete them: ``` Azure Bicep scaffolding: - [ ] Step 1: Collect inputs (org, project, GitHub repo, components) - [ ] Step 2: Generate infra/main.bicep with modular toggles - [ ] Step 3: Generate infra/modules/ (resourceGroup, staticWebApp, sqlServer; add storage/observability/aca if toggled) - [ ] Step 4: Generate infra/environments/test.parameters.json + prod.parameters.json - [ ] Step 5: Generate .github/workflows/ (deploy-test.yml, deploy-prod.yml, pr-checks.yml) - [ ] Step 6: Generate infra/sql/migrations/000_migration_history.sql + 001_create_items_table.sql - [ ] Step 7: Verify naming consistency — every resource uses {org}-{project}-{component}-{env} - [ ] Step 8: Run cost-guardrails audit before first deploy (skill: applying-azure-cost-guardrails) ``` ## Before starting, collect 1. **org** — short org/company prefix (e.g. `acme`) 2. **project** — short app name (e.g. `taskapp`) 3. **GitHub repo** — `owner/repo-name` 4. **Components needed