- Squad ConventionsCore conventions and patterns used in the Squad codebasemicrosoft/fsi-banking-payments-dispute-resolution-accelerator
- Squad ConventionsCore conventions and patterns used in the Squad codebasemicrosoft/frontier-ghcp-hackathon
- Squad HelpHow to actually use Squad — Squad is a custom Copilot agent (invoked via the task tool with agent_type='Squad'), not a skill. This file explains the right invocation paths for setting up a team, listing squad commands, and initializing Squad in a new project.microsoft/fsi-banking-payments-dispute-resolution-accelerator
- Squad Version CheckInternals of how @bradygaster/squad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.microsoft/fsi-banking-payments-dispute-resolution-accelerator
- System Type AzureDomain patterns for Azure cloud architecture — compute selection, managed services, identity (Entra ID), networking, data platform, messaging, deployment, cost management, and operational patterns. Use when designing or evaluating a system deployed on Microsoft Azure.microsoft/amplifier-bundle-systems-design
- System Type Cli ToolDomain patterns for CLI tools and developer SDKs — command structure, configuration layering, plugin architecture, distribution, backward compatibility, shell integration, and failure modes. Use when designing or evaluating command-line tools, developer platforms, or SDK libraries.microsoft/amplifier-bundle-systems-design
- System Type Data PipelineDomain patterns for data pipeline architecture — batch processing, stream processing, ETL/ELT, DAG scheduling, data quality, schema evolution, backfill strategies, and failure modes. Use when designing or evaluating data pipelines, ETL systems, or streaming data infrastructure.microsoft/amplifier-bundle-systems-design
- System Type DistributedFoundational patterns for distributed systems — consensus, consistency models, replication, partitioning, clock synchronization, distributed transactions, and failure modes. Use when designing or evaluating any system that spans multiple nodes, processes, or failure domains.microsoft/amplifier-bundle-systems-design
- System Type Edge OfflineDomain patterns for edge computing and offline-first systems — sync protocols, conflict resolution under partition, local-first architecture, constrained resources, intermittent connectivity, and failure modes. Use when designing or evaluating mobile apps, IoT systems, field-deployed software, or any system that must work without reliable network access.microsoft/amplifier-bundle-systems-design
- System Type Enterprise IntegrationDomain patterns for enterprise integration — legacy modernization, strangler fig, anti-corruption layers, API gateways, canonical data models, event-carried state transfer, and failure modes. Use when designing or evaluating integration between existing enterprise systems, legacy modernization, or multi-system orchestration.microsoft/amplifier-bundle-systems-design
- System Type Event DrivenDomain patterns for event-driven and message-based systems — pub/sub, event sourcing, CQRS, sagas, delivery guarantees, schema evolution, and failure modes. Use when designing or evaluating systems built around events, messages, or asynchronous workflows.microsoft/amplifier-bundle-systems-design
- System Type Ml ServingDomain patterns for ML/AI serving and training systems — model serving, feature stores, training pipelines, experiment tracking, A/B testing, GPU scheduling, and failure modes. Use when designing or evaluating machine learning infrastructure, model serving platforms, or AI-powered product features.microsoft/amplifier-bundle-systems-design
- System Type Multi Tenant SaasDomain patterns for multi-tenant SaaS platforms — tenant isolation models, data partitioning, noisy neighbor mitigation, per-tenant configuration, billing metering, and failure modes. Use when designing or evaluating SaaS products that serve multiple customers from shared infrastructure.microsoft/amplifier-bundle-systems-design
- System Type Peer To PeerDomain patterns for peer-to-peer system architecture — network topologies, NAT traversal, peer discovery, data distribution, consistency without central authority, identity and trust, and incentive mechanisms. Use when designing or evaluating a decentralized, peer-to-peer, or mesh-networked system.microsoft/amplifier-bundle-systems-design
- System Type Real TimeDomain patterns for real-time and collaborative systems — persistent connections, state synchronization, conflict resolution, presence, fan-out, and failure modes. Use when designing or evaluating chat systems, collaborative editors, live dashboards, gaming backends, or any system with bidirectional real-time communication.microsoft/amplifier-bundle-systems-design
- System Type SpaDomain patterns for single-page application architecture — client-side routing, state management, rendering strategies, authentication, performance, and offline support. Use when designing or evaluating a browser-based SPA, progressive web app, or rich client-side application.microsoft/amplifier-bundle-systems-design
- System Type Web ServiceDomain patterns for web service architecture — API design (REST/GraphQL/gRPC), scaling, data layer, observability, failure modes, and anti-patterns. Use when designing or evaluating a web service, API, or request/response system.microsoft/amplifier-bundle-systems-design
- System Type Workflow OrchestrationDomain patterns for workflow orchestration systems — long-running processes, state machines, saga coordination, human-in-the-loop gates, retry and timeout hierarchies, and failure modes. Use when designing or evaluating workflow engines, job orchestrators, or multi-step business process systems.microsoft/amplifier-bundle-systems-design
- Systems Design MethodologyUse when the /systems-design mode is active. 9-phase structured design methodology -- problem framing, system classification, constraints, candidate architectures, tradeoff analysis, risk review, refinement, migration planning, and documentation. Governs conversation flow, delegation patterns, and user validation checkpoints.microsoft/amplifier-bundle-systems-design
- Systems Design Review MethodologyUse when the /systems-design-review mode is active. 7-step design review methodology -- understand the design, classify the system, evaluate against codebase, adversarial analysis, tradeoff validation, synthesis, and action items. Governs conversation flow, delegation patterns, and user validation checkpoints.microsoft/amplifier-bundle-systems-design
- Template CreatorCreate or update a reusable Amplifier artifact template skill from a permitted reference document, deck, workbook, image, or message.microsoft/amplifier-bundle-work
- Test DisciplineUpdate tests when changing APIs — no exceptionsmicrosoft/frontier-ghcp-hackathon
- Test DisciplineUpdate tests when changing APIs — no exceptionsmicrosoft/fsi-banking-payments-dispute-resolution-accelerator
- Test DisciplineUpdate tests when changing APIs — no exceptionsmicrosoft/fsi-banking-payments-dispute-resolution-accelerator
- Test DisciplineUpdate tests when changing APIs — no exceptionsmicrosoft/frontier-ghcp-hackathon
- Tiered MemoryThree-tier agent memory model (hot/cold/wiki) for context reduction per spawnmicrosoft/fsi-banking-payments-dispute-resolution-accelerator
- Tradeoff AnalysisStructured tradeoff analysis methodology — the 8-dimension comparison frame, tradeoff matrix template, and common tradeoff patterns. Use when evaluating design alternatives, comparing technology choices, or when the answer is 'it depends.'microsoft/amplifier-bundle-systems-design
- UnslopCut AI tells from any writing. Must always apply.microsoft/frontier-ghcp-ttt-rvas
- Validate Post Migration DataValidate data and schema after migrating SQL Server to Azure SQL Database, Azure SQL Managed Instance, or SQL Server on Azure VM. Use after migration, restore, BACPAC import, LRS completion, cutover validation, row-count comparison, or source-target reconciliation.microsoft/sqlcon-eu-2026-demos
- VisualizeBuild interactive HTML explanations, charts, simulations, comparisons, and UI mockups. Use when a visual helps understanding; use artifact skills for Office deliverables.microsoft/amplifier-bundle-work
- VisualsUse when user wants to incorporate charts, graphs, data grid, or other visual representations of data into their project. Use VegaVisual and DataGrid components to create these visuals, utilizing the shared DataTable input, formatting, theme, and interactivity. Covers the onInteraction selection/click events host apps consume, named multi-table data input for layered overlays and reference lines, and Vega-Lite native selections.microsoft/aitour27-BRK390-building-ai-applications-with-microsoft-databases-and-fabric
- Windows CompatibilityCross-platform path handling and command patternsmicrosoft/frontier-ghcp-hackathon
- Windows CompatibilityCross-platform path handling and command patternsmicrosoft/frontier-ghcp-hackathon
- XlsxUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsmicrosoft/frontier-ghcp-ttt-rvas