azure-service-fabric
Expert knowledge for Azure Service Fabric development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when designing Service Fabric clusters, Reliable Services/Actors, CRP/CRM placement, reverse proxy, or sfctl automation, and other Azure Service Fabric related development tasks. Not for Azure App Service (use azure-app-service), Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure Container Apps (use azure-container-apps), Azure Cloud Services (use azure-cloud-services).
What this skill does
# Azure Service Fabric Skill This skill provides expert guidance for Azure Service Fabric. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities. ## How to Use This Skill > **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file > **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md) This skill requires **network access** to fetch documentation content: - **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown. - **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns Markdown. ## Category Index | Category | Lines | Description | |----------|-------|-------------| | Troubleshooting | L37-L59 | Diagnosing and fixing Service Fabric issues: connectivity, upgrades, health, logging/monitoring, container and Java logs, reverse proxy, Reliable Services/Actors, and local cluster setup. | | Best Practices | L60-L93 | Best practices for designing, migrating, testing, operating, and troubleshooting Azure Service Fabric apps and clusters, including Reliable Actors/Collections, backup/restore, health, capacity, and networking. | | Decision Making | L94-L105 | Guidance on planning Service Fabric clusters: OS/disk choices, stateless node types, capacity/durability sizing, migration targets, and supported cluster versions. | | Architecture & Design Patterns | L106-L119 | Designing Service Fabric cluster architecture: cross-AZ replica rings, CRP/CRM internals, service affinity, movement cost, defragmentation, metrics balancing, networking, and API gateway patterns. | | Limits & Quotas | L120-L124 | Configuring Service Fabric app upgrade settings: health policies, rolling upgrade behavior, monitoring, and timeout parameters to control safe, reliable deployments. | | Security | L125-L181 | Securing Service Fabric clusters/apps: cert and Entra auth, managed identities and secrets, disk encryption, network/DDoS/IP policies, remoting/endpoint security, and security best practices. | | Configuration | L182-L301 | Configuring and operating Service Fabric clusters and apps: networking, scaling, backups, manifests, actors, monitoring/logging, reverse proxy, containers, and Cluster Resource Manager settings. | | Integrations & Coding Patterns | L302-L338 | Patterns and tools for integrating Service Fabric apps with Azure services, APIs, containers, remoting stacks, and managing clusters/apps via sfctl, PowerShell, and EventStore APIs | | Deployment | L339-L402 | Deploying and upgrading Service Fabric clusters and apps (managed, classic, standalone), scaling and AZ/region migration, CI/CD pipelines, security, images, and maintenance/upgrade control. | ### Troubleshooting | Topic | URL | |-------|-----| | Connect to Service Fabric managed clusters and handle SFX cert errors | https://learn.microsoft.com/en-us/azure/service-fabric/how-to-managed-cluster-connect | | Troubleshoot SNAT port exhaustion in Service Fabric managed clusters | https://learn.microsoft.com/en-us/azure/service-fabric/how-to-managed-cluster-troubleshoot-snat-port-exhaustion-issues | | Troubleshoot Azure Service Fabric application upgrade issues | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-application-upgrade-troubleshooting | | View and use Service Fabric container logs for diagnosis | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-containers-view-logs | | Troubleshoot common Service Fabric code package errors | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-code-package-errors | | Diagnose common monitoring and diagnostics scenarios in Service Fabric | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-common-scenarios | | Analyze Service Fabric events with Azure Monitor logs queries | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-event-analysis-oms | | Monitor and diagnose Service Fabric apps locally on Windows | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-how-to-monitor-and-diagnose-services-locally | | Monitor and diagnose Service Fabric apps locally on Linux | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-how-to-monitor-and-diagnose-services-locally-linux | | Report and inspect Service Fabric health from code | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-how-to-report-and-check-service-health | | Resolve common FabricClient exceptions in Service Fabric | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-errors-and-exceptions | | Monitor Service Fabric Reliable Actors runtime diagnostics | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-actors-diagnostics | | Monitor Service Fabric ServiceRemoting with performance counters | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-serviceremoting-diagnostics | | Diagnose Stateful Reliable Services using Service Fabric diagnostics | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-diagnostics | | Diagnose Service Fabric reverse proxy request failures | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-reverse-proxy-diagnostics | | Fix common local Service Fabric cluster setup issues | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-troubleshoot-local-cluster-setup | | Debug and collect logs for Java apps on local Service Fabric clusters | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-tutorial-debug-log-local-cluster | | Use Service Fabric system health reports to troubleshoot | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-understand-and-troubleshoot-with-system-health-reports | | Query and evaluate aggregated health in Service Fabric | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-view-entities-aggregated-health | ### Best Practices | Topic | URL | |-------|-----| | Best practices to migrate Cloud Services to Service Fabric | https://learn.microsoft.com/en-us/azure/service-fabric/cloud-services-to-service-fabric-migration-guide | | Patch Windows OS on Azure Service Fabric clusters | https://learn.microsoft.com/en-us/azure/service-fabric/how-to-patch-cluster-nodes-windows | | Apply data serialization best practices for Service Fabric upgrades | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-application-upgrade-data-serialization | | Avoid invalid Service Fabric ARM cluster configurations | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-azure-resource-manager-guardrails | | Design Azure Service Fabric applications effectively | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-best-practices-applications | | Plan and scale Azure Service Fabric cluster capacity | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-best-practices-capacity-scaling | | Manage Service Fabric as code with ARM templates | https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-best-practices-infrastructure-as-code | | Monitor Azure Service Fabric clusters and applications | https://learn.microsof
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.