Güvenlik uyarılı skill
Bu skill destructive command içerebilir. Skill detaylarını ve kaynak içeriği incelemeden kurulum yapmayın, kopyalamayın, indirmeyin veya çalıştırmayın. Bilinçli ve kontrollü şekilde kullanın.
Tarayıcı bulguları
highcredential_theft
System Type Multi Tenant Saas
microsoft/amplifier-bundle-systems-design/skills/system-type-multi-tenant-saas
ai-mlResmi
Resmi Sağlayıcı Skill'iView repo
Domain 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.
Dosyalar1 dosya
SKILL.md485 satır
Loading editor…
Kurulum
ÖnerilenTek komut — ajanınız otomatik olarak devreye alır.
Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.
veya
Manuel Kurulum
Daha fazla adımDosyayı indirin ve ajanınızın sistem istemine yapıştırın.
Skill detayları
Versiyonv1.0.0
YazarMicrosoft
Kategoriai-ml
Skill IDmicrosoft/amplifier-bundle-systems-design/skills/system-type-multi-tenant-saas
İlgili skill'ler
Adversarial ReviewAdversarial review of a system design from 6 critical perspectives -- SRE, security, staff engineer, finance, operator, and developer advocate. Produces a unified risk assessment. Use for INTERACTIVE on-demand reviews during a design conversation (/adversarial-review). For RECIPE-DRIVEN reviews (where prior step context is needed), use the systems-design-critic agent instead.Architecture PrimitivesCatalog of reusable architectural primitives — boundaries, contracts, state machines, queues, caches, consistency models, and more. For each: what it is, when it's right, when it's WRONG. Use when selecting patterns for a design or evaluating whether a pattern fits.Design Philosophy Domain DrivenDomain-Driven Design as a lens for system architecture — bounded contexts, aggregates, ubiquitous language, context mapping, domain events, and strategic vs tactical patterns. Use when modeling complex business domains, defining service boundaries, or evaluating whether a system's structure reflects its domain.Design Philosophy LinuxThe Unix/Linux design philosophy as a lens for system design — mechanism vs policy, composability, small tools, text streams, convention over configuration, and the principle of least surprise. Use when evaluating designs for composability, simplicity, or separation of concerns.Design Philosophy Object OrientedObject-oriented design principles as a lens for system architecture — SOLID, composition over inheritance, the actor model, design patterns (and when they're wrong), encapsulation, polymorphism, and responsibility-driven design. Use when evaluating code organization, module boundaries, or object/component relationships.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.