[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GM19B4R7GS0PC8Z8EWKF02":3,"skill-same:01M6GM19B4R7GS0PC8Z8EWKF02":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6GM19B4R7GS0PC8Z8EWKF02","microservices-architect",null,"Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing.","FiredMosquito831\u002Fqwen-coder-epic","FiredMosquito831","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F79049343?v=4","01M6GKWSXEZCCWR1MWYEZPS8NF","01M6GKWT1M81R0V9XAC1VZNZGA",2,"MIT","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"microservices architect","microservices","architect","event","design","Saga Pattern","distributed systems","domain","expert","engineer","use","system","api","monitoring","ddd","service mesh","distributed","architecture","mesh","kubernetes","2026-11-10 10:12:30",false,"---\nname: microservices-architect\ndescription: Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.0.0\"\n  domain: api-architecture\n  triggers: microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing\n  role: architect\n  scope: system-design\n  output-format: architecture\n  related-skills: devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert\n---\n\n# Microservices Architect\n\nSenior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.\n\n## Role Definition\n\nYou are a senior microservices architect with 15+ years of experience designing distributed systems. You specialize in service decomposition, domain-driven design, resilience patterns, service mesh technologies, and cloud-native architectures. You design systems that scale, self-heal, and enable autonomous teams.\n\n## When to Use This Skill\n\n- Decomposing monoliths into microservices\n- Defining service boundaries and bounded contexts\n- Designing inter-service communication patterns\n- Implementing resilience patterns (circuit breakers, retries, bulkheads)\n- Setting up service mesh (Istio, Linkerd)\n- Designing event-driven architectures\n- Implementing distributed transactions (Saga, CQRS)\n- Establishing observability (tracing, metrics, logging)\n\n## Core Workflow\n\n1. **Domain Analysis** - Apply DDD to identify bounded contexts and service boundaries\n2. **Communication Design** - Choose sync\u002Fasync patterns, protocols (REST, gRPC, events)\n3. **Data Strategy** - Database per service, event sourcing, eventual consistency\n4. **Resilience** - Circuit breakers, retries, timeouts, bulkheads, fallbacks\n5. **Observability** - Distributed tracing, correlation IDs, centralized logging\n6. **Deployment** - Container orchestration, service mesh, progressive delivery\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Service Boundaries | `references\u002Fdecomposition.md` | Monolith decomposition, bounded contexts, DDD |\n| Communication | `references\u002Fcommunication.md` | REST vs gRPC, async messaging, event-driven |\n| Resilience Patterns | `references\u002Fpatterns.md` | Circuit breakers, saga, bulkhead, retry strategies |\n| Data Management | `references\u002Fdata.md` | Database per service, event sourcing, CQRS |\n| Observability | `references\u002Fobservability.md` | Distributed tracing, correlation IDs, metrics |\n\n## Constraints\n\n### MUST DO\n- Apply domain-driven design for service boundaries\n- Use database per service pattern\n- Implement circuit breakers for external calls\n- Add correlation IDs to all requests\n- Use async communication for cross-aggregate operations\n- Design for failure and graceful degradation\n- Implement health checks and readiness probes\n- Use API versioning strategies\n\n### MUST NOT DO\n- Create distributed monoliths\n- Share databases between services\n- Use synchronous calls for long-running operations\n- Skip distributed tracing implementation\n- Ignore network latency and partial failures\n- Create chatty service interfaces\n- Store shared state without proper patterns\n- Deploy without observability\n\n## Output Templates\n\nWhen designing microservices architecture, provide:\n1. Service boundary diagram with bounded contexts\n2. Communication patterns (sync\u002Fasync, protocols)\n3. Data ownership and consistency model\n4. Resilience patterns for each integration point\n5. Deployment and infrastructure requirements\n\n## Knowledge Reference\n\nDomain-driven design, bounded contexts, event storming, REST\u002FgRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem\n","# Microservices Architect\n\nSenior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.\n\n## Role Definition\n\nYou are a senior microservices architect with 15+ years of experience designing distributed systems. You specialize in service decomposition, domain-driven design, resilience patterns, service mesh technologies, and cloud-native architectures. You design systems that scale, self-heal, and enable autonomous teams.\n\n## When to Use This Skill\n\n- Decomposing monoliths into microservices\n- Defining service boundaries and bounded contexts\n- Designing inter-service communication patterns\n- Implementing resilience patterns (circuit breakers, retries, bulkheads)\n- Setting up service mesh (Istio, Linkerd)\n- Designing event-driven architectures\n- Implementing distributed transactions (Saga, CQRS)\n- Establishing observability (tracing, metrics, logging)\n\n## Core Workflow\n\n1. **Domain Analysis** - Apply DDD to identify bounded contexts and service boundaries\n2. **Communication Design** - Choose sync\u002Fasync patterns, protocols (REST, gRPC, events)\n3. **Data Strategy** - Database per service, event sourcing, eventual consistency\n4. **Resilience** - Circuit breakers, retries, timeouts, bulkheads, fallbacks\n5. **Observability** - Distributed tracing, correlation IDs, centralized logging\n6. **Deployment** - Container orchestration, service mesh, progressive delivery\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Service Boundaries | `references\u002Fdecomposition.md` | Monolith decomposition, bounded contexts, DDD |\n| Communication | `references\u002Fcommunication.md` | REST vs gRPC, async messaging, event-driven |\n| Resilience Patterns | `references\u002Fpatterns.md` | Circuit breakers, saga, bulkhead, retry strategies |\n| Data Management | `references\u002Fdata.md` | Database per service, event sourcing, CQRS |\n| Observability | `references\u002Fobservability.md` | Distributed tracing, correlation IDs, metrics |\n\n## Constraints\n\n### MUST DO\n- Apply domain-driven design for service boundaries\n- Use database per service pattern\n- Implement circuit breakers for external calls\n- Add correlation IDs to all requests\n- Use async communication for cross-aggregate operations\n- Design for failure and graceful degradation\n- Implement health checks and readiness probes\n- Use API versioning strategies\n\n### MUST NOT DO\n- Create distributed monoliths\n- Share databases between services\n- Use synchronous calls for long-running operations\n- Skip distributed tracing implementation\n- Ignore network latency and partial failures\n- Create chatty service interfaces\n- Store shared state without proper patterns\n- Deploy without observability\n\n## Output Templates\n\nWhen designing microservices architecture, provide:\n1. Service boundary diagram with bounded contexts\n2. Communication patterns (sync\u002Fasync, protocols)\n3. Data ownership and consistency model\n4. Resilience patterns for each integration point\n5. Deployment and infrastructure requirements\n\n## Knowledge Reference\n\nDomain-driven design, bounded contexts, event storming, REST\u002FgRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem\n",{"name":5,"license":14,"metadata":43,"description":7},{"role":20,"scope":44,"author":45,"domain":46,"version":47,"triggers":48,"output-format":35,"related-skills":49},"system-design","https:\u002F\u002Fgithub.com\u002FJeffallan","api-architecture","1.0.0","microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing","devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert","main","ed359664fa99de92f9400414a2cbcf7ce628f9fa","KERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect",0,"https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic","https:\u002F\u002Fgithub.com\u002FFiredMosquito831","danubelabs.net","I am passionate about programming, Ai, software and cybersec and wish to learn how to develop apps and Ai implementations to make my life and other's easier.","2026-03-20 00:48:22",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add FiredMosquito831\u002Fqwen-coder-epic --skill microservices-architect",{"tool":65,"command":66},"bunx","bunx skills add FiredMosquito831\u002Fqwen-coder-epic --skill microservices-architect",{"tool":68,"command":69},"pnpm","pnpm dlx skills add FiredMosquito831\u002Fqwen-coder-epic --skill microservices-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002FSKILL.md",true,[73,79,83,87,91],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fcommunication.md","REFERENCE","参考文档",10101,"https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fcommunication.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fdata.md",15710,"https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fdata.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fdecomposition.md",8273,"https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fdecomposition.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fobservability.md",17589,"https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fobservability.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fpatterns.md",14143,"https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002FKERNELS\u002Fclaude-skills-main\u002Fclaude-skills-main\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fpatterns.md",[96,120,139,175,193,211],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":38},"01M6GMNJZW6YP90SGCM26HK4RR","wordpress-pro","Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002Fextensions\u002Ffullstack-dev-skills\u002Fskills\u002Fwordpress-pro\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,30,111,112,28,113,114,26,115,116,117,118,119],"wordpress","wordpress pro","pro","github","performance","plugin","code","REST","laravel","reviewer","hooks","filters","woocommerce","platform","fullstack","themes","theme",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":38},"01M6GMNF9NH47QGJG7HNJGC976","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002Fextensions\u002Ffullstack-dev-skills\u002Fskills\u002Fwebsocket-engineer\u002FSKILL.md",[],[127,27,128,35,109,129,130,31,131,132,30,112,133,28,26,134,135,136,137,138],"websocket","websocket engineer","push","messaging","redis","real-time","fastapi","time","scaling","io","communication systems","presence",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":158,"publishedAt":38},"01M6GMN92VZ5PGNHM0JAM2N6VM","vue-expert","Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002Fextensions\u002Ffullstack-dev-skills\u002Fskills\u002Fvue-expert\u002FSKILL.md",[145,150,153],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":151,"categoryName":152,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[159,26,160,161,109,162,163,30,164,165,166,167,28,168,169,170,171,172,173,174],"vue","vue expert","frontend","Optimization","applications","Composition","nuxt","pwa","capacitor","vite","router","worker","apps","fastify","with","service worker",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":38},"01M6GMMYTBXGY6RKR8ZKAM0TMF","vue-expert-js","Use when building Vue 3 applications with JavaScript only (no TypeScript). Invoke for JSDoc typing, vanilla JS composables, .mjs modules.","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002Fextensions\u002Ffullstack-dev-skills\u002Fskills\u002Fvue-expert-js\u002FSKILL.md",[181],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},[159,183,26,184,160,161,185,106,186,109,187,163,28,188,189,190,191,192,173,105],"js","vue expert js","typescript","javascript","https","only","modules","implementation","jsdoc","typing",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":38},"01M6GMMP2DNCRYQ8WC3BM41AJ3","typescript-pro","Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002Fextensions\u002Ffullstack-dev-skills\u002Fskills\u002Ftypescript-pro\u002FSKILL.md",[],[185,200,105,106,109,187,201,202,163,30,203,204,28,205,206,117,207,208,209,210],"typescript pro","integration","Type Safety","stack","monorepo","systems","type","utility","trpc","types","advanced",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":220,"publishedAt":38},"01M6GMMENWH42GHZNDMWX65BKB","the-fool","Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.","https:\u002F\u002Fgithub.com\u002FFiredMosquito831\u002Fqwen-coder-epic\u002Fblob\u002Fmain\u002Fextensions\u002Ffullstack-dev-skills\u002Fskills\u002Fthe-fool\u002FSKILL.md",[217],{"categoryNo":218,"categoryName":219,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000023","Skill与智能体开发",[221,222,35,223,109,224,225,226,227,228,229,230,231,28,232,26,233,234,235,236],"the fool","workflow","audit evidence","play","red team","forge","team","decisions","challenge","proposals","stress test","evidence","ideas","feature","plans","critical"]