Robertjam954/multimodal_rag_application / .claude/skills/azure-enterprise-infra-planner
azure-enterprise-infra-planner
VerifiedArchitect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
references/waf-checklist.md
View on GitHub# WAF Cross-Cutting Checklist
Walk through every row and decide if resources or properties are needed.
| Concern | Question | Resources / Properties to Add |
|---------|----------|-------------------------------|
| Identity | How do services authenticate to each other? | Managed identity, RBAC role assignments |
| Secrets | Are there connection strings, API keys, credentials? | Key Vault with RBAC authorization, soft-delete, and purge protection enabled |
| Monitoring | How will operators observe the system? | Application Insights for compute, Log Analytics workspace, diagnostic settings on data resources |
| Network | Should resources have public endpoints? | Prefer private connectivity (VNet integration, private endpoints, `publicNetworkAccess: "Disabled"`). Only expose endpoints publicly when the workload requires it, and document the decision as a tradeoff. |
| Encryption | Is data encrypted at rest and in transit? | HTTPS-only, modern minimum TLS, Key Vault for customer-managed keys |
| Resilience | Single points of failure? | Zone-redundant SKUs where supported; compute distributed across ≥2 zones for production. Document deviations as tradeoffs. |
| Auth hardening | Can local/key-based auth be disabled? | Disable local auth on services that support it (e.g. Event Grid, Service Bus, Storage) |
| Tagging | Resources tagged for cost tracking? | Tags on every resource |
## Common Additions
Most workloads should include these unless sub-goals justify omission:
- Key Vault — secrets, certificates, customer-managed keys
- Managed Identity — prefer over keys for service-to-service auth
- Application Insights — for App Service, Functions, Container Apps, AKS
- Log Analytics — centralized log aggregation
- Diagnostic Settings — wire data resources to Log Analytics
If you intentionally skip a concern (e.g., no VNet for cost reasons), document it in `overallReasoning.tradeoffs` and `inputs.subGoals`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |