[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEV9F1RPZDZSVZBXGJSFTR":3,"skill-same:01M7AEV9F1RPZDZSVZBXGJSFTR":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AEV9F1RPZDZSVZBXGJSFTR","0.4.1-understand-microservices_architecture",null,"sancovp\u002Fdark-factory-live","sancovp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F147458096?v=4","01M74F2EFE4Q0KF1Y5AY27HVNB","Isaac Wostrel-Rubin","01M7AC3EB8VZXS1SKHQW1EZ4N1",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Flibraries\u002Fsoftware_architecture_patterns_and_styles\u002Funderstand-software_architecture_patterns_and_styles\u002Funderstand-microservices_architecture\u002F.claude\u002Fskills\u002F0.4.1-understand-microservices_architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 0.4.1-understand-microservices_architecture\ndescription: [0.4.1] An architectural style that structures an application as a collection of small, autonomous, loosely-coupled se\n---\n\n# understand-microservices_architecture\n\n**CALL NUMBER:** `software_architecture_patterns_and_styles.microservices_architecture : deep_microservices_archit(16), deep_event_driven_archite(9)`\n**DEFINITION:** An architectural style that structures an application as a collection of small, autonomous, loosely-coupled services organized around business capabilities, each deployable independently and communicating via lightweight protocols.\n\nInvoke this skill to understand `microservices_architecture` down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP\u002FSWI-Prolog consistency gate): every reference below resolves.\n\n## THE RELATIVE ROOT (the import cone, by lib)\n\n### from `?`\n- **distributed_transaction** (d2): A transaction that spans multiple independent services or database_per_service instances, requiring coordination to maintain atomicity across nodes where each participant may reside in a different process or machine.\n\n### from `deep_event_driven_archite`\n- **pubsub_broker** (d5): The intermediary component that receives messages from publishers and forwards them to subscribers based on topic subscriptions; may also perform filtering.\n- **pubsub_topic** (d5): A named channel or subject through which messages are routed from publishers to interested subscribers; the publisher has no knowledge of subscriber identities or count.\n- **pubsub_message** (d5): The payload broadcast by a publisher on a topic; in pub\u002Fsub it is typically ephemeral and not persisted beyond active subscriber consumption.\n- **pubsub_dead_letter** (d6): A destination for messages that cannot be successfully delivered to any subscriber, capturing failures for later inspection or replay.\n- **pubsub_subscription** (d6): An active registration linking a subscriber to a topic; may be durable (surviving subscriber disconnection) or transient (active only while subscriber is connected).\n- **pubsub_topic_namespace** (d6): A hierarchical or scoped naming scheme for topics (e.g., orders.new, orders.cancelled) that enables subscribers to express interest at varying levels of granularity.\n- **pubsub_content_filter** (d6): A predicate or attribute-based rule applied at the broker or subscriber side to select a subset of messages on a topic for delivery.\n- **pubsub_message_schema** (d6): A structured format (JSON, Avro, Protobuf) defining the shape of messages on a topic, enabling subscribers to deserialize and interpret published events.\n- **pubsub_subscriber** (d7): An entity that expresses interest in one or more topics and receives messages published to those topics; receives only messages matching its subscriptions.\n\n### from `deep_microservices_archit`\n- **gateway_routing__integration** (d3): Integration with load_balancing to distribute requests across multiple instances of a backend service.\n- **gateway_routing_backend_service** (d3): A microservice or backend resource that receives forwarded requests from the gateway.\n- **gateway_routing_circuit_breaker_integration** (d3): Integration with circuit_breaker logic to prevent routing to failing backend services.\n- **gateway_routing_fallback_route** (d3): A predefined route or behavior triggered when primary routing fails or no route matches.\n- **gateway_routing_response_aggregation** (d3): The combination of responses from multiple backend services into a single client response.\n- **gateway_routing_reverse_proxy** (d3): The mechanism that forwards matched requests to backend services and returns responses to clients.\n- **gateway_routing_route** (d3): A defined mapping between incoming request criteria and a target backend service endpoint.\n- **gateway_routing_service_discovery_integration** (d3): Integration with service_discovery to dynamically resolve backend service network locations.\n- **gateway_routing_header_transformation** (d4): The addition, removal, or modification of HTTP headers during request forwarding.\n- **gateway_routing_path_rewrite** (d4): A transformation that modifies the request path before forwarding to the backend service.\n- **gateway_routing_route_definition** (d4): The declarative or imperative specification of a route including matching criteria and target service.\n- **gateway_routing_request_matcher** (d5): A component that evaluates incoming requests against route matching criteria.\n- **gateway_routing_route_priority** (d5): The ordering rule that determines which route takes precedence when multiple routes match.\n- **gateway_routing_header_condition** (d6): A matching rule based on request or response header values for routing decisions.\n- **gateway_routing_http_method_filter** (d6): A routing constraint based on HTTP method (GET, POST, PUT, DELETE) for route matching.\n- **gateway_routing_path_pattern** (d6): A URL path template or pattern used to match incoming request paths for routing decisions.\n\n### from `software_architecture_patterns_and_styles`\n- **api_gateway** (d1): A server entry point that routes requests to backend services, handling cross-cutting concerns like authentication, rate_limiting, and protocol_translation.\n- **database_per_service** (d1): A data management pattern in microservices where each service owns and manages its own database schema or instance, enforcing loose coupling.\n- **saga_pattern** (d1): A pattern for managing distributed transactions across microservices using a sequence of local transactions with compensating actions for rollback, replacing distributed transactions.\n- **service_discovery** (d1): The automatic detection of services and their network locations (IP address, port) in a dynamic infrastructure, typically via client_side_discovery or server_side_discovery.\n- **service_mesh** (d1): A dedicated infrastructure layer that handles service_to_service communication, providing observability, traffic_management, and security without embedding this logic in application code (e.g., Istio, Linkerd).\n- **shared_database** (d1): An anti_pattern in microservices where multiple services share the same database, creating tight coupling and hindering independent deployment.\n- **gateway_routing** (d2): A pattern where an API_gateway routes requests to appropriate backend services based on request characteristics (URL path, headers) without the client knowing service locations.\n- **rate_limiting** (d2): A traffic_management technique that controls how many requests a client can make in a given time period, protecting services from overload and abuse.\n- **choreography_pattern** (d2): A distributed coordination pattern where services exchange events without a central orchestrator; each service knows what to do based on received events.\n- **orchestration_pattern** (d2): A distributed coordination pattern where a central coordinator (orchestrator) directs the flow of operations across services, contrasting with choreography.\n- **load_balancing** (d2): A technique for distributing network traffic or workload across multiple servers to ensure no single resource is overwhelmed, improving responsiveness and availability.\n- **sidecar_pattern** (d2): A deployment pattern where a helper container (sidecar) is attached to a main application container to extend or add functionality without modifying the application.\n- **anti_pattern** (d2): A commonly used pattern that appears beneficial but is actually counterproductive; architectural anti_patterns include big_ball_of_mud, golden_hammer, and spaghetti_code.\n- **event_driven_architecture** (d3): A software design pattern where the flow of the program is determined by events (user actions, sensor outputs, messages) and the propagation of events through the system.\n- **service_oriented_architecture** (d3): An architectural pattern where application components provide services to other components via a communication protocol, typically over a network. SOA emphasizes interoperability and composition of services.\n- **horizontal_scaling** (d3): Scaling out by adding more machines to a system, as opposed to vertical_scaling which adds resources to existing machines.\n- **ambassador_service** (d3): A helper service that offloads client-side network responsibilities (retry, circuit_breaker, monitoring) from the application into a sidecar container.\n- **event_streaming** (d4): A data handling approach where events are captured in order as an immutable log (stream), allowing multiple consumers to read independently (e.g., Kafka, Pulsar).\n- **message_queue** (d4): A communication mechanism where messages are placed in a queue by producers and consumed asynchronously by consumers, decoupling sender and receiver in time and space.\n- **publish_subscribe_pattern** (d4): A messaging pattern where publishers send messages to a topic without knowing subscribers, and subscribers receive messages published to topics they are interested in.\n- **auto_scaling** (d4): Automatically adjusting the number of compute instances based on demand metrics (CPU, request_count, queue_depth), improving resource efficiency.\n\n## CONSUMERS (what needs this)\n`bounded_context`, `contract_testing`, `strangler_fig_pattern`\n\n---\n*Projected from the `software architecture patterns and styles` KB (211 concepts \u002F 192 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.*\n\n_(leaf — this is an actual skill.)_\n","# understand-microservices_architecture\n\n**CALL NUMBER:** `software_architecture_patterns_and_styles.microservices_architecture : deep_microservices_archit(16), deep_event_driven_archite(9)`\n**DEFINITION:** An architectural style that structures an application as a collection of small, autonomous, loosely-coupled services organized around business capabilities, each deployable independently and communicating via lightweight protocols.\n\nInvoke this skill to understand `microservices_architecture` down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP\u002FSWI-Prolog consistency gate): every reference below resolves.\n\n## THE RELATIVE ROOT (the import cone, by lib)\n\n### from `?`\n- **distributed_transaction** (d2): A transaction that spans multiple independent services or database_per_service instances, requiring coordination to maintain atomicity across nodes where each participant may reside in a different process or machine.\n\n### from `deep_event_driven_archite`\n- **pubsub_broker** (d5): The intermediary component that receives messages from publishers and forwards them to subscribers based on topic subscriptions; may also perform filtering.\n- **pubsub_topic** (d5): A named channel or subject through which messages are routed from publishers to interested subscribers; the publisher has no knowledge of subscriber identities or count.\n- **pubsub_message** (d5): The payload broadcast by a publisher on a topic; in pub\u002Fsub it is typically ephemeral and not persisted beyond active subscriber consumption.\n- **pubsub_dead_letter** (d6): A destination for messages that cannot be successfully delivered to any subscriber, capturing failures for later inspection or replay.\n- **pubsub_subscription** (d6): An active registration linking a subscriber to a topic; may be durable (surviving subscriber disconnection) or transient (active only while subscriber is connected).\n- **pubsub_topic_namespace** (d6): A hierarchical or scoped naming scheme for topics (e.g., orders.new, orders.cancelled) that enables subscribers to express interest at varying levels of granularity.\n- **pubsub_content_filter** (d6): A predicate or attribute-based rule applied at the broker or subscriber side to select a subset of messages on a topic for delivery.\n- **pubsub_message_schema** (d6): A structured format (JSON, Avro, Protobuf) defining the shape of messages on a topic, enabling subscribers to deserialize and interpret published events.\n- **pubsub_subscriber** (d7): An entity that expresses interest in one or more topics and receives messages published to those topics; receives only messages matching its subscriptions.\n\n### from `deep_microservices_archit`\n- **gateway_routing__integration** (d3): Integration with load_balancing to distribute requests across multiple instances of a backend service.\n- **gateway_routing_backend_service** (d3): A microservice or backend resource that receives forwarded requests from the gateway.\n- **gateway_routing_circuit_breaker_integration** (d3): Integration with circuit_breaker logic to prevent routing to failing backend services.\n- **gateway_routing_fallback_route** (d3): A predefined route or behavior triggered when primary routing fails or no route matches.\n- **gateway_routing_response_aggregation** (d3): The combination of responses from multiple backend services into a single client response.\n- **gateway_routing_reverse_proxy** (d3): The mechanism that forwards matched requests to backend services and returns responses to clients.\n- **gateway_routing_route** (d3): A defined mapping between incoming request criteria and a target backend service endpoint.\n- **gateway_routing_service_discovery_integration** (d3): Integration with service_discovery to dynamically resolve backend service network locations.\n- **gateway_routing_header_transformation** (d4): The addition, removal, or modification of HTTP headers during request forwarding.\n- **gateway_routing_path_rewrite** (d4): A transformation that modifies the request path before forwarding to the backend service.\n- **gateway_routing_route_definition** (d4): The declarative or imperative specification of a route including matching criteria and target service.\n- **gateway_routing_request_matcher** (d5): A component that evaluates incoming requests against route matching criteria.\n- **gateway_routing_route_priority** (d5): The ordering rule that determines which route takes precedence when multiple routes match.\n- **gateway_routing_header_condition** (d6): A matching rule based on request or response header values for routing decisions.\n- **gateway_routing_http_method_filter** (d6): A routing constraint based on HTTP method (GET, POST, PUT, DELETE) for route matching.\n- **gateway_routing_path_pattern** (d6): A URL path template or pattern used to match incoming request paths for routing decisions.\n\n### from `software_architecture_patterns_and_styles`\n- **api_gateway** (d1): A server entry point that routes requests to backend services, handling cross-cutting concerns like authentication, rate_limiting, and protocol_translation.\n- **database_per_service** (d1): A data management pattern in microservices where each service owns and manages its own database schema or instance, enforcing loose coupling.\n- **saga_pattern** (d1): A pattern for managing distributed transactions across microservices using a sequence of local transactions with compensating actions for rollback, replacing distributed transactions.\n- **service_discovery** (d1): The automatic detection of services and their network locations (IP address, port) in a dynamic infrastructure, typically via client_side_discovery or server_side_discovery.\n- **service_mesh** (d1): A dedicated infrastructure layer that handles service_to_service communication, providing observability, traffic_management, and security without embedding this logic in application code (e.g., Istio, Linkerd).\n- **shared_database** (d1): An anti_pattern in microservices where multiple services share the same database, creating tight coupling and hindering independent deployment.\n- **gateway_routing** (d2): A pattern where an API_gateway routes requests to appropriate backend services based on request characteristics (URL path, headers) without the client knowing service locations.\n- **rate_limiting** (d2): A traffic_management technique that controls how many requests a client can make in a given time period, protecting services from overload and abuse.\n- **choreography_pattern** (d2): A distributed coordination pattern where services exchange events without a central orchestrator; each service knows what to do based on received events.\n- **orchestration_pattern** (d2): A distributed coordination pattern where a central coordinator (orchestrator) directs the flow of operations across services, contrasting with choreography.\n- **load_balancing** (d2): A technique for distributing network traffic or workload across multiple servers to ensure no single resource is overwhelmed, improving responsiveness and availability.\n- **sidecar_pattern** (d2): A deployment pattern where a helper container (sidecar) is attached to a main application container to extend or add functionality without modifying the application.\n- **anti_pattern** (d2): A commonly used pattern that appears beneficial but is actually counterproductive; architectural anti_patterns include big_ball_of_mud, golden_hammer, and spaghetti_code.\n- **event_driven_architecture** (d3): A software design pattern where the flow of the program is determined by events (user actions, sensor outputs, messages) and the propagation of events through the system.\n- **service_oriented_architecture** (d3): An architectural pattern where application components provide services to other components via a communication protocol, typically over a network. SOA emphasizes interoperability and composition of services.\n- **horizontal_scaling** (d3): Scaling out by adding more machines to a system, as opposed to vertical_scaling which adds resources to existing machines.\n- **ambassador_service** (d3): A helper service that offloads client-side network responsibilities (retry, circuit_breaker, monitoring) from the application into a sidecar container.\n- **event_streaming** (d4): A data handling approach where events are captured in order as an immutable log (stream), allowing multiple consumers to read independently (e.g., Kafka, Pulsar).\n- **message_queue** (d4): A communication mechanism where messages are placed in a queue by producers and consumed asynchronously by consumers, decoupling sender and receiver in time and space.\n- **publish_subscribe_pattern** (d4): A messaging pattern where publishers send messages to a topic without knowing subscribers, and subscribers receive messages published to topics they are interested in.\n- **auto_scaling** (d4): Automatically adjusting the number of compute instances based on demand metrics (CPU, request_count, queue_depth), improving resource efficiency.\n\n## CONSUMERS (what needs this)\n`bounded_context`, `contract_testing`, `strangler_fig_pattern`\n\n---\n*Projected from the `software architecture patterns and styles` KB (211 concepts \u002F 192 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.*\n\n_(leaf — this is an actual skill.)_\n",{},"main","dfed66814f223a9f42bec375a3c59d74eefdcad5","kbworld\u002Fstate\u002Flibraries\u002Fsoftware_architecture_patterns_and_styles\u002Funderstand-software_architecture_patterns_and_styles\u002Funderstand-microservices_architecture\u002F.claude\u002Fskills\u002F0.4.1-understand-microservices_architecture","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live","https:\u002F\u002Fgithub.com\u002Fsancovp","https:\u002F\u002Fisaacwr.carrd.co\u002F","AKA Olivus Victory-Promise\r\n\r\nAI Agents, Tools, and Infrastructure","2026-10-09 02:22:46",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sancovp\u002Fdark-factory-live --skill 0.4.1-understand-microservices_architecture",{"tool":37,"command":38},"bunx","bunx skills add sancovp\u002Fdark-factory-live --skill 0.4.1-understand-microservices_architecture",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sancovp\u002Fdark-factory-live --skill 0.4.1-understand-microservices_architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Flibraries\u002Fsoftware_architecture_patterns_and_styles\u002Funderstand-software_architecture_patterns_and_styles\u002Funderstand-microservices_architecture\u002F.claude\u002Fskills\u002F0.4.1-understand-microservices_architecture\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AGYB2CPCQYJP631CH18A1A","quests","The quest board — accept quests, craft skills to fulfill them, earn gold rewards.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002Fquests\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AGXYVW23T3X4APFAV3H4ZY","metrics","Check your profitability and trading performance — gold earned, spent, net profit, trade history.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002Fmetrics\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AGXWC0C1W7PZK5YXQW0NQM","things","Flat search across the game — find quests, knowledge domains, agents, trade listings, memories.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AGXT9SX50REN4K7ZGE08JT","test-skill","Test a crafted skill by running it through a fresh Claude instance. Use before posting to trade or submitting for quests.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Ftest_skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AGXRA67MFHJJNDEVX6PFKR","remember","Your zettelkasten — persistent memory that survives across seasons. Record observations, strategies, and craft insights.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fremember\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AGXNND02SYFXB1JV9YRPAN","skill-types","The type system — Template, Lens, Prosthesis, Towering, Combiner, Persona, Recipe. Learn to type skills, chain them, and write Recipes.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fplaces\u002Fskill_types\u002FSKILL.md",[],[]]