[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQWTC0SVMEP8C74PDPWS6J":3,"skill-same:01M7AQWTC0SVMEP8C74PDPWS6J":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AQWTC0SVMEP8C74PDPWS6J","azure-cloud-architect",null,"Design Azure architectures for startups and enterprises. Use when asked to design Azure infrastructure, create Bicep\u002FARM templates, optimize Azure costs, set up Azure DevOps pipelines, or migrate to Azure. Covers AKS, App Service, Azure Functions, Cosmos DB, and cost optimization.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"azure-cloud-architect\"\ndescription: \"Design Azure architectures for startups and enterprises. Use when asked to design Azure infrastructure, create Bicep\u002FARM templates, optimize Azure costs, set up Azure DevOps pipelines, or migrate to Azure. Covers AKS, App Service, Azure Functions, Cosmos DB, and cost optimization.\"\n---\n\n# Azure Cloud Architect\n\nDesign scalable, cost-effective Azure architectures for startups and enterprises with Bicep infrastructure-as-code templates.\n\n---\n\n## Workflow\n\n### Step 1: Gather Requirements\n\nCollect application specifications:\n\n```\n- Application type (web app, mobile backend, data pipeline, SaaS, microservices)\n- Expected users and requests per second\n- Budget constraints (monthly spend limit)\n- Team size and Azure experience level\n- Compliance requirements (GDPR, HIPAA, SOC 2, ISO 27001)\n- Availability requirements (SLA, RPO\u002FRTO)\n- Region preferences (data residency, latency)\n```\n\n### Step 2: Design Architecture\n\nRun the architecture designer to get pattern recommendations:\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 10000 \\\n  --requirements '{\"budget_monthly_usd\": 500, \"compliance\": [\"SOC2\"]}'\n```\n\n**Example output:**\n\n```json\n{\n  \"recommended_pattern\": \"app_service_web\",\n  \"service_stack\": [\"App Service\", \"Azure SQL\", \"Front Door\", \"Key Vault\", \"Entra ID\"],\n  \"estimated_monthly_cost_usd\": 280,\n  \"pros\": [\"Managed platform\", \"Built-in autoscale\", \"Deployment slots\"],\n  \"cons\": [\"Less control than VMs\", \"Platform constraints\", \"Cold start on consumption plans\"]\n}\n```\n\nSelect from recommended patterns:\n- **App Service Web**: Front Door + App Service + Azure SQL + Redis Cache\n- **Microservices on AKS**: AKS + Service Bus + Cosmos DB + API Management\n- **Serverless Event-Driven**: Functions + Event Grid + Service Bus + Cosmos DB\n- **Data Pipeline**: Data Factory + Synapse Analytics + Data Lake Storage + Event Hubs\n\nSee `references\u002Farchitecture_patterns.md` for detailed pattern specifications.\n\n**Validation checkpoint:** Confirm the recommended pattern matches the team's operational maturity and compliance requirements before proceeding to Step 3.\n\n### Step 3: Generate IaC Templates\n\nCreate infrastructure-as-code for the selected pattern:\n\n```bash\n# Web app stack (Bicep)\npython scripts\u002Fbicep_generator.py --arch-type web-app --output main.bicep\n```\n\n**Example Bicep output (core web app resources):**\n\n```bicep\n@description('The environment name')\nparam environment string = 'dev'\n\n@description('The Azure region for resources')\nparam location string = resourceGroup().location\n\n@description('The application name')\nparam appName string = 'myapp'\n\n\u002F\u002F App Service Plan\nresource appServicePlan 'Microsoft.Web\u002Fserverfarms@2023-01-01' = {\n  name: '${environment}-${appName}-plan'\n  location: location\n  sku: {\n    name: 'P1v3'\n    tier: 'PremiumV3'\n    capacity: 1\n  }\n  properties: {\n    reserved: true \u002F\u002F Linux\n  }\n}\n\n\u002F\u002F App Service\nresource appService 'Microsoft.Web\u002Fsites@2023-01-01' = {\n  name: '${environment}-${appName}-web'\n  location: location\n  properties: {\n    serverFarmId: appServicePlan.id\n    httpsOnly: true\n    siteConfig: {\n      linuxFxVersion: 'NODE|20-lts'\n      minTlsVersion: '1.2'\n      ftpsState: 'Disabled'\n      alwaysOn: true\n    }\n  }\n  identity: {\n    type: 'SystemAssigned'\n  }\n}\n\n\u002F\u002F Azure SQL Database\nresource sqlServer 'Microsoft.Sql\u002Fservers@2023-05-01-preview' = {\n  name: '${environment}-${appName}-sql'\n  location: location\n  properties: {\n    administrators: {\n      azureADOnlyAuthentication: true\n    }\n    minimalTlsVersion: '1.2'\n  }\n}\n\nresource sqlDatabase 'Microsoft.Sql\u002Fservers\u002Fdatabases@2023-05-01-preview' = {\n  parent: sqlServer\n  name: '${appName}-db'\n  location: location\n  sku: {\n    name: 'GP_S_Gen5_2'\n    tier: 'GeneralPurpose'\n  }\n  properties: {\n    autoPauseDelay: 60\n    minCapacity: json('0.5')\n  }\n}\n```\n\n> Full templates including Front Door, Key Vault, Managed Identity, and monitoring are generated by `bicep_generator.py` and also available in `references\u002Farchitecture_patterns.md`.\n\n**Bicep is the recommended IaC language for Azure.** Prefer Bicep over ARM JSON templates: Bicep compiles to ARM JSON, has cleaner syntax, supports modules, and is first-party supported by Microsoft.\n\n### Step 4: Review Costs\n\nAnalyze estimated costs and optimization opportunities:\n\n```bash\npython scripts\u002Fcost_optimizer.py \\\n  --config current_resources.json \\\n  --json\n```\n\n**Example output:**\n\n```json\n{\n  \"current_monthly_usd\": 2000,\n  \"recommendations\": [\n    { \"action\": \"Right-size SQL Database GP_S_Gen5_8 to GP_S_Gen5_2\", \"savings_usd\": 380, \"priority\": \"high\" },\n    { \"action\": \"Purchase 1-year Reserved Instances for AKS node pools\", \"savings_usd\": 290, \"priority\": \"high\" },\n    { \"action\": \"Move Blob Storage to Cool tier for objects >30 days old\", \"savings_usd\": 65, \"priority\": \"medium\" }\n  ],\n  \"total_potential_savings_usd\": 735\n}\n```\n\nOutput includes:\n- Monthly cost breakdown by service\n- Right-sizing recommendations\n- Reserved Instance and Savings Plan opportunities\n- Potential monthly savings\n\n### Step 5: Configure CI\u002FCD\n\nSet up Azure DevOps Pipelines or GitHub Actions with Azure:\n\n```yaml\n# GitHub Actions — deploy Bicep to Azure\nname: Deploy Infrastructure\non:\n  push:\n    branches: [main]\n\npermissions:\n  id-token: write\n  contents: read\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - uses: azure\u002Flogin@v2\n        with:\n          client-id: ${{ secrets.AZURE_CLIENT_ID }}\n          tenant-id: ${{ secrets.AZURE_TENANT_ID }}\n          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}\n\n      - uses: azure\u002Farm-deploy@v2\n        with:\n          resourceGroupName: rg-myapp-dev\n          template: .\u002Finfra\u002Fmain.bicep\n          parameters: environment=dev\n```\n\n```yaml\n# Azure DevOps Pipeline\ntrigger:\n  branches:\n    include:\n      - main\n\npool:\n  vmImage: 'ubuntu-latest'\n\nsteps:\n  - task: AzureCLI@2\n    inputs:\n      azureSubscription: 'MyServiceConnection'\n      scriptType: 'bash'\n      scriptLocation: 'inlineScript'\n      inlineScript: |\n        az deployment group create \\\n          --resource-group rg-myapp-dev \\\n          --template-file infra\u002Fmain.bicep \\\n          --parameters environment=dev\n```\n\n### Step 6: Security Review\n\nValidate security posture before production:\n\n- **Identity**: Entra ID (Azure AD) with RBAC, Managed Identity for service-to-service auth — never store credentials in code\n- **Secrets**: Key Vault for all secrets, certificates, and connection strings\n- **Network**: NSGs on all subnets, Private Endpoints for PaaS services, Application Gateway with WAF\n- **Encryption**: TLS 1.2+ in transit, Azure-managed or customer-managed keys at rest\n- **Monitoring**: Microsoft Defender for Cloud enabled, Azure Policy for guardrails\n- **Compliance**: Azure Policy assignments for SOC 2 \u002F HIPAA \u002F ISO 27001 initiatives\n\n**If deployment fails:**\n\n1. Check the deployment status:\n   ```bash\n   az deployment group show \\\n     --resource-group rg-myapp-dev \\\n     --name main \\\n     --query 'properties.error'\n   ```\n2. Review Activity Log for RBAC or policy errors.\n3. Validate the Bicep template before deploying:\n   ```bash\n   az bicep build --file main.bicep\n   az deployment group validate \\\n     --resource-group rg-myapp-dev \\\n     --template-file main.bicep\n   ```\n\n**Common failure causes:**\n- RBAC permission errors — verify the deploying principal has Contributor on the resource group\n- Resource provider not registered — run `az provider register --namespace Microsoft.Web`\n- Naming conflicts — Azure resource names are often globally unique (storage accounts, web apps)\n- Quota exceeded — request quota increase via Azure Portal > Subscriptions > Usage + quotas\n\n---\n\n## Tools\n\n### architecture_designer.py\n\nGenerates architecture pattern recommendations based on requirements.\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 50000 \\\n  --requirements '{\"budget_monthly_usd\": 1000, \"compliance\": [\"HIPAA\"]}' \\\n  --json\n```\n\n**Input:** Application type, expected users, JSON requirements\n**Output:** Recommended pattern, service stack, cost estimate, pros\u002Fcons\n\n### cost_optimizer.py\n\nAnalyzes Azure resource configurations for cost savings.\n\n```bash\npython scripts\u002Fcost_optimizer.py --config resources.json --json\n```\n\n**Input:** JSON file with current Azure resource inventory\n**Output:** Recommendations for:\n- Idle resource removal\n- VM and database right-sizing\n- Reserved Instance purchases\n- Storage tier transitions\n- Unused public IPs and load balancers\n\n### bicep_generator.py\n\nGenerates Bicep template scaffolds from architecture type.\n\n```bash\npython scripts\u002Fbicep_generator.py --arch-type microservices --output main.bicep\n```\n\n**Output:** Production-ready Bicep templates with:\n- Managed Identity (no passwords)\n- Key Vault integration\n- Diagnostic settings for Azure Monitor\n- Network security groups\n- Tags for cost allocation\n\n---\n\n## Quick Start\n\n### Web App Architecture (\u003C $100\u002Fmonth)\n\n```\nAsk: \"Design an Azure web app for a startup with 5000 users\"\n\nResult:\n- App Service (B1 Linux) for the application\n- Azure SQL Serverless for relational data\n- Azure Blob Storage for static assets\n- Front Door (free tier) for CDN and routing\n- Key Vault for secrets\n- Estimated: $40-80\u002Fmonth\n```\n\n### Microservices on AKS ($500-2000\u002Fmonth)\n\n```\nAsk: \"Design a microservices architecture on Azure for a SaaS platform with 50k users\"\n\nResult:\n- AKS cluster with 3 node pools (system, app, jobs)\n- API Management for gateway and rate limiting\n- Cosmos DB for multi-model data\n- Service Bus for async messaging\n- Azure Monitor + Application Insights for observability\n- Multi-zone deployment\n```\n\n### Serverless Event-Driven (\u003C $200\u002Fmonth)\n\n```\nAsk: \"Design an event-driven backend for processing orders\"\n\nResult:\n- Azure Functions (Consumption plan) for compute\n- Event Grid for event routing\n- Service Bus for reliable messaging\n- Cosmos DB for order data\n- Application Insights for monitoring\n- Estimated: $30-150\u002Fmonth depending on volume\n```\n\n### Data Pipeline ($300-1500\u002Fmonth)\n\n```\nAsk: \"Design a data pipeline for ingesting 10M events\u002Fday\"\n\nResult:\n- Event Hubs for ingestion\n- Stream Analytics or Functions for processing\n- Data Lake Storage Gen2 for raw data\n- Synapse Analytics for warehouse\n- Power BI for dashboards\n```\n\n---\n\n## Input Requirements\n\nProvide these details for architecture design:\n\n| Requirement | Description | Example |\n|-------------|-------------|---------|\n| Application type | What you're building | SaaS platform, mobile backend |\n| Expected scale | Users, requests\u002Fsec | 10k users, 100 RPS |\n| Budget | Monthly Azure limit | $500\u002Fmonth max |\n| Team context | Size, Azure experience | 3 devs, intermediate |\n| Compliance | Regulatory needs | HIPAA, GDPR, SOC 2 |\n| Availability | Uptime requirements | 99.9% SLA, 1hr RPO |\n\n**JSON Format:**\n\n```json\n{\n  \"application_type\": \"saas_platform\",\n  \"expected_users\": 10000,\n  \"requests_per_second\": 100,\n  \"budget_monthly_usd\": 500,\n  \"team_size\": 3,\n  \"azure_experience\": \"intermediate\",\n  \"compliance\": [\"SOC2\"],\n  \"availability_sla\": \"99.9%\"\n}\n```\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Do This Instead |\n|---|---|---|\n| ARM JSON templates for new projects | Verbose, hard to read, no modules | Use Bicep — compiles to ARM, cleaner syntax |\n| Storing secrets in App Settings | Secrets visible in portal, no rotation | Use Key Vault references in App Settings |\n| Single large AKS node pool | Cannot optimize for different workloads | Use multiple node pools: system, app, jobs |\n| Public endpoints on PaaS services | Exposed attack surface | Use Private Endpoints + VNet integration |\n| Over-provisioning \"just in case\" | Wastes budget month one | Start small, use autoscale, right-size monthly |\n| Shared resource groups for everything | Blast radius, RBAC nightmares | One resource group per environment per workload |\n| No tagging strategy | Cannot track costs or ownership | Tag: environment, owner, cost-center, app-name |\n| Using classic resources | Deprecated, limited features | Use ARM\u002FBicep resources exclusively |\n\n---\n\n## Output Formats\n\n### Architecture Design\n\n- Pattern recommendation with rationale\n- Service stack diagram (ASCII)\n- Monthly cost estimate and trade-offs\n\n### IaC Templates\n\n- **Bicep**: Recommended — first-party, module support, clean syntax\n- **ARM JSON**: Generated from Bicep when needed\n- **Terraform HCL**: Multi-cloud compatible using azurerm provider\n\n### Cost Analysis\n\n- Current spend breakdown with optimization recommendations\n- Priority action list (high\u002Fmedium\u002Flow) and implementation checklist\n\n---\n\n## Cross-References\n\n| Skill | Relationship |\n|-------|-------------|\n| `engineering-team\u002Faws-solution-architect` | AWS equivalent — same 6-step workflow, different services |\n| `engineering-team\u002Fgcp-cloud-architect` | GCP equivalent — completes the cloud trifecta |\n| `engineering-team\u002Fsenior-devops` | Broader DevOps scope — pipelines, monitoring, containerization |\n| `engineering\u002Fterraform-patterns` | IaC implementation — use for Terraform modules targeting Azure |\n| `engineering\u002Fci-cd-pipeline-builder` | Pipeline construction — automates Azure DevOps and GitHub Actions |\n\n---\n\n## Reference Documentation\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Farchitecture_patterns.md` | 5 patterns: web app, microservices\u002FAKS, serverless, data pipeline, multi-region |\n| `references\u002Fservice_selection.md` | Decision matrices for compute, database, storage, messaging, networking |\n| `references\u002Fbest_practices.md` | Naming conventions, tagging, RBAC, network security, monitoring, DR |\n","# Azure Cloud Architect\n\nDesign scalable, cost-effective Azure architectures for startups and enterprises with Bicep infrastructure-as-code templates.\n\n---\n\n## Workflow\n\n### Step 1: Gather Requirements\n\nCollect application specifications:\n\n```\n- Application type (web app, mobile backend, data pipeline, SaaS, microservices)\n- Expected users and requests per second\n- Budget constraints (monthly spend limit)\n- Team size and Azure experience level\n- Compliance requirements (GDPR, HIPAA, SOC 2, ISO 27001)\n- Availability requirements (SLA, RPO\u002FRTO)\n- Region preferences (data residency, latency)\n```\n\n### Step 2: Design Architecture\n\nRun the architecture designer to get pattern recommendations:\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 10000 \\\n  --requirements '{\"budget_monthly_usd\": 500, \"compliance\": [\"SOC2\"]}'\n```\n\n**Example output:**\n\n```json\n{\n  \"recommended_pattern\": \"app_service_web\",\n  \"service_stack\": [\"App Service\", \"Azure SQL\", \"Front Door\", \"Key Vault\", \"Entra ID\"],\n  \"estimated_monthly_cost_usd\": 280,\n  \"pros\": [\"Managed platform\", \"Built-in autoscale\", \"Deployment slots\"],\n  \"cons\": [\"Less control than VMs\", \"Platform constraints\", \"Cold start on consumption plans\"]\n}\n```\n\nSelect from recommended patterns:\n- **App Service Web**: Front Door + App Service + Azure SQL + Redis Cache\n- **Microservices on AKS**: AKS + Service Bus + Cosmos DB + API Management\n- **Serverless Event-Driven**: Functions + Event Grid + Service Bus + Cosmos DB\n- **Data Pipeline**: Data Factory + Synapse Analytics + Data Lake Storage + Event Hubs\n\nSee `references\u002Farchitecture_patterns.md` for detailed pattern specifications.\n\n**Validation checkpoint:** Confirm the recommended pattern matches the team's operational maturity and compliance requirements before proceeding to Step 3.\n\n### Step 3: Generate IaC Templates\n\nCreate infrastructure-as-code for the selected pattern:\n\n```bash\n# Web app stack (Bicep)\npython scripts\u002Fbicep_generator.py --arch-type web-app --output main.bicep\n```\n\n**Example Bicep output (core web app resources):**\n\n```bicep\n@description('The environment name')\nparam environment string = 'dev'\n\n@description('The Azure region for resources')\nparam location string = resourceGroup().location\n\n@description('The application name')\nparam appName string = 'myapp'\n\n\u002F\u002F App Service Plan\nresource appServicePlan 'Microsoft.Web\u002Fserverfarms@2023-01-01' = {\n  name: '${environment}-${appName}-plan'\n  location: location\n  sku: {\n    name: 'P1v3'\n    tier: 'PremiumV3'\n    capacity: 1\n  }\n  properties: {\n    reserved: true \u002F\u002F Linux\n  }\n}\n\n\u002F\u002F App Service\nresource appService 'Microsoft.Web\u002Fsites@2023-01-01' = {\n  name: '${environment}-${appName}-web'\n  location: location\n  properties: {\n    serverFarmId: appServicePlan.id\n    httpsOnly: true\n    siteConfig: {\n      linuxFxVersion: 'NODE|20-lts'\n      minTlsVersion: '1.2'\n      ftpsState: 'Disabled'\n      alwaysOn: true\n    }\n  }\n  identity: {\n    type: 'SystemAssigned'\n  }\n}\n\n\u002F\u002F Azure SQL Database\nresource sqlServer 'Microsoft.Sql\u002Fservers@2023-05-01-preview' = {\n  name: '${environment}-${appName}-sql'\n  location: location\n  properties: {\n    administrators: {\n      azureADOnlyAuthentication: true\n    }\n    minimalTlsVersion: '1.2'\n  }\n}\n\nresource sqlDatabase 'Microsoft.Sql\u002Fservers\u002Fdatabases@2023-05-01-preview' = {\n  parent: sqlServer\n  name: '${appName}-db'\n  location: location\n  sku: {\n    name: 'GP_S_Gen5_2'\n    tier: 'GeneralPurpose'\n  }\n  properties: {\n    autoPauseDelay: 60\n    minCapacity: json('0.5')\n  }\n}\n```\n\n> Full templates including Front Door, Key Vault, Managed Identity, and monitoring are generated by `bicep_generator.py` and also available in `references\u002Farchitecture_patterns.md`.\n\n**Bicep is the recommended IaC language for Azure.** Prefer Bicep over ARM JSON templates: Bicep compiles to ARM JSON, has cleaner syntax, supports modules, and is first-party supported by Microsoft.\n\n### Step 4: Review Costs\n\nAnalyze estimated costs and optimization opportunities:\n\n```bash\npython scripts\u002Fcost_optimizer.py \\\n  --config current_resources.json \\\n  --json\n```\n\n**Example output:**\n\n```json\n{\n  \"current_monthly_usd\": 2000,\n  \"recommendations\": [\n    { \"action\": \"Right-size SQL Database GP_S_Gen5_8 to GP_S_Gen5_2\", \"savings_usd\": 380, \"priority\": \"high\" },\n    { \"action\": \"Purchase 1-year Reserved Instances for AKS node pools\", \"savings_usd\": 290, \"priority\": \"high\" },\n    { \"action\": \"Move Blob Storage to Cool tier for objects >30 days old\", \"savings_usd\": 65, \"priority\": \"medium\" }\n  ],\n  \"total_potential_savings_usd\": 735\n}\n```\n\nOutput includes:\n- Monthly cost breakdown by service\n- Right-sizing recommendations\n- Reserved Instance and Savings Plan opportunities\n- Potential monthly savings\n\n### Step 5: Configure CI\u002FCD\n\nSet up Azure DevOps Pipelines or GitHub Actions with Azure:\n\n```yaml\n# GitHub Actions — deploy Bicep to Azure\nname: Deploy Infrastructure\non:\n  push:\n    branches: [main]\n\npermissions:\n  id-token: write\n  contents: read\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - uses: azure\u002Flogin@v2\n        with:\n          client-id: ${{ secrets.AZURE_CLIENT_ID }}\n          tenant-id: ${{ secrets.AZURE_TENANT_ID }}\n          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}\n\n      - uses: azure\u002Farm-deploy@v2\n        with:\n          resourceGroupName: rg-myapp-dev\n          template: .\u002Finfra\u002Fmain.bicep\n          parameters: environment=dev\n```\n\n```yaml\n# Azure DevOps Pipeline\ntrigger:\n  branches:\n    include:\n      - main\n\npool:\n  vmImage: 'ubuntu-latest'\n\nsteps:\n  - task: AzureCLI@2\n    inputs:\n      azureSubscription: 'MyServiceConnection'\n      scriptType: 'bash'\n      scriptLocation: 'inlineScript'\n      inlineScript: |\n        az deployment group create \\\n          --resource-group rg-myapp-dev \\\n          --template-file infra\u002Fmain.bicep \\\n          --parameters environment=dev\n```\n\n### Step 6: Security Review\n\nValidate security posture before production:\n\n- **Identity**: Entra ID (Azure AD) with RBAC, Managed Identity for service-to-service auth — never store credentials in code\n- **Secrets**: Key Vault for all secrets, certificates, and connection strings\n- **Network**: NSGs on all subnets, Private Endpoints for PaaS services, Application Gateway with WAF\n- **Encryption**: TLS 1.2+ in transit, Azure-managed or customer-managed keys at rest\n- **Monitoring**: Microsoft Defender for Cloud enabled, Azure Policy for guardrails\n- **Compliance**: Azure Policy assignments for SOC 2 \u002F HIPAA \u002F ISO 27001 initiatives\n\n**If deployment fails:**\n\n1. Check the deployment status:\n   ```bash\n   az deployment group show \\\n     --resource-group rg-myapp-dev \\\n     --name main \\\n     --query 'properties.error'\n   ```\n2. Review Activity Log for RBAC or policy errors.\n3. Validate the Bicep template before deploying:\n   ```bash\n   az bicep build --file main.bicep\n   az deployment group validate \\\n     --resource-group rg-myapp-dev \\\n     --template-file main.bicep\n   ```\n\n**Common failure causes:**\n- RBAC permission errors — verify the deploying principal has Contributor on the resource group\n- Resource provider not registered — run `az provider register --namespace Microsoft.Web`\n- Naming conflicts — Azure resource names are often globally unique (storage accounts, web apps)\n- Quota exceeded — request quota increase via Azure Portal > Subscriptions > Usage + quotas\n\n---\n\n## Tools\n\n### architecture_designer.py\n\nGenerates architecture pattern recommendations based on requirements.\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 50000 \\\n  --requirements '{\"budget_monthly_usd\": 1000, \"compliance\": [\"HIPAA\"]}' \\\n  --json\n```\n\n**Input:** Application type, expected users, JSON requirements\n**Output:** Recommended pattern, service stack, cost estimate, pros\u002Fcons\n\n### cost_optimizer.py\n\nAnalyzes Azure resource configurations for cost savings.\n\n```bash\npython scripts\u002Fcost_optimizer.py --config resources.json --json\n```\n\n**Input:** JSON file with current Azure resource inventory\n**Output:** Recommendations for:\n- Idle resource removal\n- VM and database right-sizing\n- Reserved Instance purchases\n- Storage tier transitions\n- Unused public IPs and load balancers\n\n### bicep_generator.py\n\nGenerates Bicep template scaffolds from architecture type.\n\n```bash\npython scripts\u002Fbicep_generator.py --arch-type microservices --output main.bicep\n```\n\n**Output:** Production-ready Bicep templates with:\n- Managed Identity (no passwords)\n- Key Vault integration\n- Diagnostic settings for Azure Monitor\n- Network security groups\n- Tags for cost allocation\n\n---\n\n## Quick Start\n\n### Web App Architecture (\u003C $100\u002Fmonth)\n\n```\nAsk: \"Design an Azure web app for a startup with 5000 users\"\n\nResult:\n- App Service (B1 Linux) for the application\n- Azure SQL Serverless for relational data\n- Azure Blob Storage for static assets\n- Front Door (free tier) for CDN and routing\n- Key Vault for secrets\n- Estimated: $40-80\u002Fmonth\n```\n\n### Microservices on AKS ($500-2000\u002Fmonth)\n\n```\nAsk: \"Design a microservices architecture on Azure for a SaaS platform with 50k users\"\n\nResult:\n- AKS cluster with 3 node pools (system, app, jobs)\n- API Management for gateway and rate limiting\n- Cosmos DB for multi-model data\n- Service Bus for async messaging\n- Azure Monitor + Application Insights for observability\n- Multi-zone deployment\n```\n\n### Serverless Event-Driven (\u003C $200\u002Fmonth)\n\n```\nAsk: \"Design an event-driven backend for processing orders\"\n\nResult:\n- Azure Functions (Consumption plan) for compute\n- Event Grid for event routing\n- Service Bus for reliable messaging\n- Cosmos DB for order data\n- Application Insights for monitoring\n- Estimated: $30-150\u002Fmonth depending on volume\n```\n\n### Data Pipeline ($300-1500\u002Fmonth)\n\n```\nAsk: \"Design a data pipeline for ingesting 10M events\u002Fday\"\n\nResult:\n- Event Hubs for ingestion\n- Stream Analytics or Functions for processing\n- Data Lake Storage Gen2 for raw data\n- Synapse Analytics for warehouse\n- Power BI for dashboards\n```\n\n---\n\n## Input Requirements\n\nProvide these details for architecture design:\n\n| Requirement | Description | Example |\n|-------------|-------------|---------|\n| Application type | What you're building | SaaS platform, mobile backend |\n| Expected scale | Users, requests\u002Fsec | 10k users, 100 RPS |\n| Budget | Monthly Azure limit | $500\u002Fmonth max |\n| Team context | Size, Azure experience | 3 devs, intermediate |\n| Compliance | Regulatory needs | HIPAA, GDPR, SOC 2 |\n| Availability | Uptime requirements | 99.9% SLA, 1hr RPO |\n\n**JSON Format:**\n\n```json\n{\n  \"application_type\": \"saas_platform\",\n  \"expected_users\": 10000,\n  \"requests_per_second\": 100,\n  \"budget_monthly_usd\": 500,\n  \"team_size\": 3,\n  \"azure_experience\": \"intermediate\",\n  \"compliance\": [\"SOC2\"],\n  \"availability_sla\": \"99.9%\"\n}\n```\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Do This Instead |\n|---|---|---|\n| ARM JSON templates for new projects | Verbose, hard to read, no modules | Use Bicep — compiles to ARM, cleaner syntax |\n| Storing secrets in App Settings | Secrets visible in portal, no rotation | Use Key Vault references in App Settings |\n| Single large AKS node pool | Cannot optimize for different workloads | Use multiple node pools: system, app, jobs |\n| Public endpoints on PaaS services | Exposed attack surface | Use Private Endpoints + VNet integration |\n| Over-provisioning \"just in case\" | Wastes budget month one | Start small, use autoscale, right-size monthly |\n| Shared resource groups for everything | Blast radius, RBAC nightmares | One resource group per environment per workload |\n| No tagging strategy | Cannot track costs or ownership | Tag: environment, owner, cost-center, app-name |\n| Using classic resources | Deprecated, limited features | Use ARM\u002FBicep resources exclusively |\n\n---\n\n## Output Formats\n\n### Architecture Design\n\n- Pattern recommendation with rationale\n- Service stack diagram (ASCII)\n- Monthly cost estimate and trade-offs\n\n### IaC Templates\n\n- **Bicep**: Recommended — first-party, module support, clean syntax\n- **ARM JSON**: Generated from Bicep when needed\n- **Terraform HCL**: Multi-cloud compatible using azurerm provider\n\n### Cost Analysis\n\n- Current spend breakdown with optimization recommendations\n- Priority action list (high\u002Fmedium\u002Flow) and implementation checklist\n\n---\n\n## Cross-References\n\n| Skill | Relationship |\n|-------|-------------|\n| `engineering-team\u002Faws-solution-architect` | AWS equivalent — same 6-step workflow, different services |\n| `engineering-team\u002Fgcp-cloud-architect` | GCP equivalent — completes the cloud trifecta |\n| `engineering-team\u002Fsenior-devops` | Broader DevOps scope — pipelines, monitoring, containerization |\n| `engineering\u002Fterraform-patterns` | IaC implementation — use for Terraform modules targeting Azure |\n| `engineering\u002Fci-cd-pipeline-builder` | Pipeline construction — automates Azure DevOps and GitHub Actions |\n\n---\n\n## Reference Documentation\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Farchitecture_patterns.md` | 5 patterns: web app, microservices\u002FAKS, serverless, data pipeline, multi-region |\n| `references\u002Fservice_selection.md` | Decision matrices for compute, database, storage, messaging, networking |\n| `references\u002Fbest_practices.md` | Naming conventions, tagging, RBAC, network security, monitoring, DR |\n",{"name":5,"description":7},"main","992d25a425dee442a1f6a628d00a4fed33efe839","engineering-team\u002Fskills\u002Fazure-cloud-architect","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill azure-cloud-architect",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill azure-cloud-architect",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill azure-cloud-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002FSKILL.md",true,[45,51,55,59,65,69],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Farchitecture_patterns.md","REFERENCE","参考文档",17911,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002Freferences\u002Farchitecture_patterns.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fbest_practices.md",12257,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002Freferences\u002Fbest_practices.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fservice_selection.md",11119,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002Freferences\u002Fservice_selection.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Farchitecture_designer.py","SCRIPT","脚本",21966,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002Fscripts\u002Farchitecture_designer.py",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fbicep_generator.py",23663,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002Fscripts\u002Fbicep_generator.py",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fcost_optimizer.py",21203,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fazure-cloud-architect\u002Fscripts\u002Fcost_optimizer.py",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]