Azure Deploy

This is essentially a design system and UI audit tool rolled into one skill. It runs accessibility checks (contrast ratios, focus states, ARIA labels), validates touch targets and spacing, and suggests specific color palettes and font pairings from its database of 161 palettes and 57 combinations. The real value is in the priority-based rule system that catches common UX problems like missing loading states, poor responsive breakpoints, and platform-specific interaction patterns. It covers 10 tech stacks so you get relevant code whether you're building in React, SwiftUI, or Flutter. Use it when designing new interfaces or when your UI feels off but you can't pinpoint why.

When you need to architect enterprise Azure infrastructure from scratch rather than deploy individual apps, this skill walks you through the full planning process. It pulls Azure best practices and Well-Architected Framework guidance via MCP tools, generates detailed infrastructure plans as JSON, then outputs production-ready Bicep or Terraform code. Handles complex scenarios like hub-spoke networks, multi-region DR topologies, and compliance-driven designs that span multiple resource groups or subscriptions. The workflow enforces approval gates before any code generation, so you review the architecture plan before committing to infrastructure-as-code. Best for platform engineers who need systematic infrastructure planning rather than quick app deployments.

The azure-deploy skill executes deployment operations for applications that have already been prepared with infrastructure files and a deployment plan, running commands like `azd up`, `azd deploy`, and `terraform apply` with built-in error recovery. It is designed for developers who need to push prepared applications to Azure production environments, but requires that the azure-prepare and azure-validate skills have been completed first to ensure infrastructure readiness. This skill solves the problem of safely deploying pre-validated Azure applications while preventing users from skipping critical validation steps that would cause deployment failures.

Microsoft's production-ready guide for standing up AKS clusters without the usual trial-and-error cycle. It walks you through the critical Day-0 decisions that are expensive to change later, like networking models and API server configuration, while distinguishing them from Day-1 features you can enable post-creation. The skill generates concrete cluster configurations with rationale, covers the Automatic vs Standard SKU decision tree, and includes specific guidance on Azure CNI Overlay, egress gateways, and Node Auto Provisioning. Honest take: this saves you from the common mistake of realizing your networking choices were wrong after you've already deployed workloads.

This grounds GitHub Actions answers in official documentation instead of letting you wing it from memory. It searches docs.github.com first, finds the most relevant page for workflow syntax or runner configs or OIDC setup, then gives you the exact link alongside a direct answer. Useful when someone asks about workflow triggers, matrix builds, secret management, or migrating from Jenkins and you need the current official guidance, not outdated Stack Overflow advice. It won't debug specific failing workflows but handles the "how do I actually configure this" questions with proper documentation backing.