Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-enterprise-infra-planner

azure-enterprise-infra-planner

Verified

Architect 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.

FileKindSize
SKILL.mdskill md3.5 KB
references/bicep-generation.mdmarkdown3.5 KB
references/constraints/README.mdmarkdown1.2 KB
references/constraints/ai-ml.mdmarkdown3.2 KB
references/constraints/compute-apps.mdmarkdown7.8 KB
references/constraints/compute-infra.mdmarkdown4.5 KB
references/constraints/data-analytics.mdmarkdown6.3 KB
references/constraints/data-relational.mdmarkdown4.9 KB
references/constraints/messaging.mdmarkdown2.5 KB
references/constraints/monitoring.mdmarkdown1.7 KB
references/constraints/networking-connectivity.mdmarkdown6.1 KB
references/constraints/networking-core.mdmarkdown7.0 KB
references/constraints/networking-traffic.mdmarkdown4.6 KB
references/constraints/security.mdmarkdown2.4 KB
references/deployment.mdmarkdown3.7 KB
references/pairing-checks.mdmarkdown3.7 KB
references/phases/1-extract-insights.mdmarkdown1.8 KB
references/phases/2-research-best-practices.mdmarkdown2.8 KB
references/phases/3-research-resources.mdmarkdown3.3 KB
references/phases/4-generate-plan.mdmarkdown792 B
references/phases/5-verify.mdmarkdown814 B
references/phases/6-generate-iac.mdmarkdown675 B
references/phases/7-deploy.mdmarkdown1.3 KB
references/resources/README.mdmarkdown1.6 KB
references/resources/ai-ml.mdmarkdown2.1 KB
references/resources/compute-apps.mdmarkdown4.0 KB
references/resources/compute-infra.mdmarkdown2.8 KB
references/resources/data-analytics.mdmarkdown3.0 KB
references/resources/data-relational.mdmarkdown2.6 KB
references/resources/messaging.mdmarkdown2.0 KB
references/resources/monitoring.mdmarkdown1.5 KB
references/resources/networking-connectivity.mdmarkdown3.6 KB
references/resources/networking-core.mdmarkdown4.3 KB
references/resources/networking-traffic.mdmarkdown2.6 KB
references/resources/security.mdmarkdown1.5 KB
references/schema.mdmarkdown2.7 KB
references/terraform-generation.mdmarkdown2.7 KB
references/verification.mdmarkdown2.6 KB
references/waf-checklist.mdmarkdown1.9 KB
references/workflow.mdmarkdown2.6 KB

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`.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall