Claude Cursor GitHub Copilot Skill

azure-landing-zone-architect

Use this skill for Azure landing-zone design, management-group and subscription hierarchy reviews, platform-versus-application boundary decisions, or multi-subscription Azure platform architecture critiques that span governance, identity, networking, security, and operations.

LLM Mart · 0 points · 5 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_azure_azure-landing-zone-architect-febe32a.zip · 8 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/azure/azure-landing-zone-architect
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Azure Landing Zone Architect

Purpose

Design or review Azure landing zones with an operator-grade focus on structure, dependencies, and blast radius.

This skill is for platform decisions that cut across:

  • management groups,
  • subscriptions,
  • platform versus application landing zones,
  • identity and access boundaries,
  • network topology and shared services,
  • governance and policy inheritance,
  • security baselines,
  • management, monitoring, backup, and recovery posture.

When to use

Use this skill when the user asks for:

  • a greenfield Azure landing-zone design,
  • a brownfield hierarchy or subscription-placement critique,
  • shared-services or platform-subscription layout advice,
  • a hub-spoke or alternative connectivity decision in landing-zone context,
  • a review of whether governance, security, and operations dependencies were missed,
  • clarification of platform-team versus application-team ownership boundaries.

Do not use this skill for:

  • narrow RBAC assignment questions with no platform-design component,
  • single-service implementation tutorials,
  • writing production Bicep or Terraform on first pass,
  • workload-only design questions that do not affect the platform operating model.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • Azure Landing Zone Architecture Operations — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
  • MCP and evidence path — use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
  • Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
  • Official sources — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • landing-zone-architecture-operations.md 5.3 KB
      Loading…
    • mcp-and-evidence.md 1.5 KB
      Loading…
    • official-sources.md 2.3 KB
      Loading…
    • safety-checklist.md 1.7 KB
      Loading…
    • workflow-and-output.md 1.6 KB
      Loading…
  • metadata.json 1.7 KB
    Loading…
  • SKILL.md 3.2 KB
    ---
    name: azure-landing-zone-architect
    description: Use this skill for Azure landing-zone design, management-group and subscription hierarchy reviews, platform-versus-application boundary decisions, or multi-subscription Azure platform architecture critiques that span governance, identity, networking, security, and operations.
    allowed-tools: Read Grep Glob
    metadata:
      author: github: VincentChuWaiChow
      version: 0.1.3
      updated: "2026-06-05"
      category: compliance
    ---
    
    # Azure Landing Zone Architect
    
    ## Purpose
    
    Design or review Azure landing zones with an operator-grade focus on structure, dependencies, and blast radius.
    
    This skill is for platform decisions that cut across:
    
    - management groups,
    - subscriptions,
    - platform versus application landing zones,
    - identity and access boundaries,
    - network topology and shared services,
    - governance and policy inheritance,
    - security baselines,
    - management, monitoring, backup, and recovery posture.
    
    ## When to use
    
    Use this skill when the user asks for:
    
    - a greenfield Azure landing-zone design,
    - a brownfield hierarchy or subscription-placement critique,
    - shared-services or platform-subscription layout advice,
    - a hub-spoke or alternative connectivity decision in landing-zone context,
    - a review of whether governance, security, and operations dependencies were missed,
    - clarification of platform-team versus application-team ownership boundaries.
    
    Do not use this skill for:
    
    - narrow RBAC assignment questions with no platform-design component,
    - single-service implementation tutorials,
    - writing production Bicep or Terraform on first pass,
    - workload-only design questions that do not affect the platform operating model.
    
    ## Lean operating rules
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
    - Separate confirmed facts from inference. If state was not queried or shown, say so.
    - Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
    - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
    
    ## References
    
    Load these only when needed:
    
    - [Azure Landing Zone Architecture Operations](references/landing-zone-architecture-operations.md) — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
    - [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
    - [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
    - [Official sources](references/official-sources.md) — use when you need the detailed Microsoft documentation list or source notes.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the main risks or control gaps,
    - the safest next actions,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.