[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AW3K1FYRKBA86MDY2ZBFBN":3,"skill-same:01M7AW3K1FYRKBA86MDY2ZBFBN":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AW3K1FYRKBA86MDY2ZBFBN","system-design-architect",null,"Design, evaluate, and scale production distributed systems using the 5-step senior engineering framework, capacity estimation calculus, and 5-dimension interview scorecards. Do not use for low-level algorithm coding, single-process scripts, or generic prompt drafting.","SpectreDeath\u002FBrain-Harness","SpectreDeath","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F207463416?v=4","01M7AVGR1D4X8ADT47APKGVH2Z","JL","01M7AVGR2HSGD23BA5DBTJJTVN",0,"MIT","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystem-design-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: system-design-architect\ndescription: Design, evaluate, and scale production distributed systems using the 5-step senior engineering framework, capacity estimation calculus, and 5-dimension interview scorecards. Do not use for low-level algorithm coding, single-process scripts, or generic prompt drafting.\n---\n\n# Senior Software System Design Architect\n\n`system-design-architect` is the definitive system design and architectural engineering skill for designing, evaluating, and scaling production distributed systems. Synthesized directly from the curriculum and masterclass *Design Software Systems Like a Senior Engineer* by Hike Simon and Beau Carnes (freeCodeCamp.org), it enforces the **5-Step System Design Progression** and evaluates architectures across the **5 Senior Engineering Dimensions**.\n\nSystem design evaluates **how you think and communicate** across ambiguous requirements, not merely whether you memorize static diagrams. This skill operationalizes structured problem decomposition, quantitative capacity calculations, and proactive production failure mode analysis.\n\nSee [CARD.md](CARD.md) for the companion summary card, 5-stage progression matrix, and mandatory invariants checklist.\nConsult `config.default.yaml` for default capacity thresholds and latency SLO budgets.\n\n---\n\n## The 5-Stage System Design Progression\n\n```\n[1. Requirements & Scope Lock] ──► [2. Data & API Modeling] ──► [3. High-Level Architecture]\n                                                                        │\n                                                                        ▼\n[5. Trade-offs & Extension] ◄── [4. Scale & Failure Modes Deep Dive] ◄──┘\n```\n\n---\n\n## 1. Requirements Clarification & Scope Lock (5–10 min)\n\nTransform ambiguous, vague problem prompts into locked functional and non-functional specifications before designing:\n\n1. **Clarify Functional Requirements (Core Flows)**:\n   - Identify the 3 to 5 non-negotiable user capabilities: *\"What functionalities, if removed, mean this system ceases to be itself?\"* (e.g. Booking.com must search rooms and reserve inventory; WhatsApp must deliver messages and maintain connections).\n   - Isolate edge flows to explicitly mark as out-of-scope for the initial design.\n2. **Lock Non-Functional Requirements (SLAs\u002FSLOs)**:\n   - **Availability vs Consistency**: State CAP theorem priority (e.g. Booking.com demands strong consistency for room reservations; Spotify prioritizes high availability for streaming).\n   - **Latency Bounds**: Read latency SLA (e.g. \u003C 100ms p99) and write latency SLA (e.g. \u003C 200ms p99).\n   - **Durability & Security**: Data loss tolerance and encryption requirements (e.g. WhatsApp end-to-end encryption).\n3. **Capacity & Scale Estimation (Top-Down vs Bottom-Up)**:\n   - Calculate Daily Active Users (DAU), Read:Write Ratio, Average QPS, and Peak QPS ($2\\times \\text{ to } 5\\times \\text{ average}$).\n   - Estimate Network Ingress and Egress Bandwidth ($\\text{QPS} \\times \\text{payload size}$).\n   - Project Storage Growth over 1 to 5 years ($\\text{writes\u002Fday} \\times \\text{record size} \\times 365 \\times 5$).\n4. **Establish Bounded Scope**:\n   - Explicitly enumerate **In-Scope** versus **Out-of-Scope** components to prevent unbudgeted scope creep.\n\n> **Completion criterion**: Functional requirements cataloged, non-functional SLAs locked, capacity estimates calculated, and scope boundaries agreed upon.\n\n---\n\n## 2. Data & API Modeling (15–20 min)\n\nFormalize data contracts, storage paradigms, and network protocols prior to component topology:\n\n1. **Entity-Relationship Data Modeling**:\n   - Identify primary entities, attributes, and relationships (1:1, 1:N, N:M).\n   - Establish primary keys, foreign keys, partition keys, and query indexes.\n2. **Database Paradigm Selection & Technical Justification**:\n   - **Relational SQL (PostgreSQL\u002FMySQL)**: Structured relational entities, ACID transactional consistency, complex joins (e.g. Booking.com reservations, Spotify artist\u002Falbum catalog).\n   - **NoSQL Document \u002F Wide-Column (Cassandra\u002FDynamoDB\u002FScyllaDB)**: Massive write throughput, time-series data, high horizontal scale (e.g. WhatsApp message mailboxes, Spotify track playback analytics).\n   - **In-Memory Key-Value (Redis\u002FMemcached)**: Ephemeral routing tables, session state, distributed locks (Redlock), and caching layers.\n   - **Object \u002F Blob Storage (S3\u002FGCS)**: Static media assets, raw audio segments (Spotify), and user attachments.\n3. **API Contract & Protocol Specification**:\n   - Define exact API endpoints, HTTP methods, payload schemas, and response codes.\n   - Select protocol based on access pattern: REST for stateless CRUD, gRPC for inter-service RPC, WebSocket\u002FTCP for persistent bi-directional streams (WhatsApp).\n\n> **Completion criterion**: Entity schemas defined, database paradigms technically justified, API contracts drafted, and protocol selections aligned with SLAs.\n\n---\n\n## 3. High-Level Architecture Design (15–20 min)\n\nConstruct the end-to-end component topology and trace primary read and write data flows:\n\n1. **Ingress & Edge Routing Layer**:\n   - DNS routing, Anycast IP, and Global CDN edge caching for static assets and media chunks (e.g. Cloudflare, Fastly).\n   - API Gateway \u002F Reverse Proxy (Envoy, Nginx) handling TLS termination, rate limiting, authentication, and request routing.\n2. **Core Domain Microservices Tier**:\n   - Decompose monolithic domains into single-responsibility stateless services (e.g. Search Service, Booking Service, Audio Ingestion Service, Connection Manager).\n   - Ensure services scale horizontally behind load balancers.\n3. **Data & Storage Tiering**:\n   - Connect domain services to primary databases, read replicas, and caching clusters.\n   - Integrate asynchronous message brokers (Kafka, RabbitMQ, SQS) to decouple write-heavy ingestion from downstream analytics and notifications.\n4. **End-to-End Data Flow Trace**:\n   - Walk through the step-by-step **Read Flow** from client request through CDN, Cache, and Read Replica.\n   - Walk through the step-by-step **Write Flow** from client submission through Gateway, Service, Lock Manager, Primary Database, and Message Queue.\n\n> **Completion criterion**: Comprehensive architecture topology mapped with clear ingress, microservices, caches, and end-to-end read\u002Fwrite data flows.\n\n---\n\n## 4. Scalability, Failure Modes & Reliability Deep Dive (10–15 min)\n\nStress-test the architecture against production scale, concurrency bottlenecks, and single points of failure:\n\n1. **Single Point of Failure (SPOF) Identification & Elimination**:\n   - Audit every component: *\"What happens if this database, gateway, or cache fails?\"*\n   - Implement multi-AZ and multi-region active-passive or active-active redundancy with automated failover.\n2. **Horizontal Scaling & Data Partitioning (Sharding)**:\n   - Formulate sharding strategy: Range-based, Hash-based, or Consistent Hashing (Virtual Nodes).\n   - Resolve rebalancing costs, cross-shard joins, and hot-shard \u002F celebrity keys (e.g. Spotify viral song, WhatsApp popular group).\n3. **Concurrency Control & Race Condition Prevention**:\n   - **Optimistic Locking**: Version column checks (`WHERE version = :expected`) for low-contention environments.\n   - **Pessimistic Locking \u002F Distributed Leases**: Redis Redlock or ZooKeeper mutexes with short TTLs (10–15 min) to prevent double bookings in reservation systems.\n4. **Caching Strategy & Stampede Protection**:\n   - Strategy: Cache-Aside (Lazy Loading), Write-Through, or Write-Behind.\n   - Invalidation & Eviction: TTL expiration, LRU\u002FLFU policy, and distributed mutexes\u002Fprobabilistic early expiration (XFetch) to prevent cache stampedes.\n5. **Resilience & Fault Tolerance**:\n   - Circuit breakers, exponential backoff with jitter, dead-letter queues (DLQ), and graceful degradation.\n\n> **Completion criterion**: Single points of failure eliminated, sharding keys selected, concurrency locks verified, and caching stampede defenses established.\n\n---\n\n## 5. Trade-off Reflection & Extensions (5 min)\n\nConduct an objective architectural post-mortem and propose production refinements:\n\n1. **Explicit Architectural Trade-offs**:\n   - Articulate compromises made: *\"We chose Cassandra over PostgreSQL for message history to optimize write throughput at the expense of complex cross-entity transactional joins.\"*\n   - Evaluate CAP theorem trade-offs: Consistency vs Availability during network partitions.\n2. **Alternative Approaches Evaluated**:\n   - Compare rejected alternatives: Explain why WebSockets were selected over HTTP long-polling, or why Redis Redlock was chosen over pure SQL row locks.\n3. **Production Extensions & Day-2 Operations**:\n   - Observability: Distributed tracing (OpenTelemetry), metrics (Prometheus), structured logging.\n   - Multi-region deployment, disaster recovery RTO\u002FRPO targets, and cost optimization.\n\n> **Completion criterion**: Architectural trade-offs explicitly documented, alternative designs contrasted, and operational scaling roadmap finalized.\n\n---\n\n## The 5 Senior Engineering Evaluation Dimensions\n\nIn production audits and senior\u002Fstaff interviews, candidates and systems are graded across five dimensions:\n\n| Dimension | Weight | Senior \u002F Staff Evaluation Criteria |\n|---|---|---|\n| **1. Communication & Collaboration** | 20% | Treats the reviewer\u002Finterviewer as a peer colleague; asks clarifying questions upfront; validates assumptions incrementally; balances speaking with listening. |\n| **2. Structured Decomposition** | 20% | Outlines the 5-step roadmap; deconstructs ambiguous problem spaces into crisp functional blocks; maintains structured progression without erratic jumps. |\n| **3. Technical Judgment** | 25% | Selects databases, protocols, and architectural tiers strictly based on requirements and access patterns; justifies trade-offs; rejects buzzwords without merit. |\n| **4. Practical Depth** | 25% | Proactively anticipates production failure modes, concurrency race conditions, network partitions, cache stampedes, and failover scenarios. |\n| **5. Time Management & Pacing** | 10% | Actively manages pacing across the 45–60 minute session; aligns early on deep-dive focus areas; drives the discussion to a conclusive wrap-up. |\n\n---\n\n## Canonical Production Case Studies\n\n### 1. Spotify (Audio Streaming Platform)\n- **Audio Delivery:** S3 \u002F Blob Storage + Global CDN with HTTP Range Requests (`Range: bytes=0-1048575`) and pre-buffering.\n- **Metadata Management:** PostgreSQL for artist\u002Falbum\u002Ftrack catalog + Redis cluster for user playlists and recommendations.\n- **Audio Transcoding:** Asynchronous message queue (Kafka) triggering worker nodes for multi-bitrate AAC\u002FOGG encoding.\n- **Scale:** 500M+ users, > 95% CDN cache hit ratio, read:write ratio 50:1.\n\n### 2. Booking.com (Hotel Reservation & Inventory System)\n- **Zero-Double-Booking Guarantee:** 2-phase reservation state machine (`Pending` $\\rightarrow$ `Reserved` $\\rightarrow$ `Confirmed` $\\rightarrow$ `Expired`\u002F`Cancelled`).\n- **Concurrency Control:** Short-lived distributed lease (Redis Redlock with 10–15 min TTL) + Optimistic locking on room inventory (`version` column).\n- **Search & Filtering:** CQRS architecture with Elasticsearch\u002FOpenSearch read cluster decoupled from transactional booking database.\n- **Scale:** 1.1B annual reservations, 500M monthly web visits, read:write ratio 100:1.\n\n### 3. WhatsApp (Global Real-Time Messaging)\n- **Connection Management:** Stateful WebSocket \u002F TCP gateways managing millions of persistent connections per cluster.\n- **Session Registry:** Ephemeral Redis distributed routing table mapping User IDs to active Gateway instances with heartbeat monitoring.\n- **Message Storage:** Transient mailbox queues (Cassandra \u002F ScyllaDB) with automatic message purge upon client delivery ACK.\n- **E2EE Security:** Signal Protocol double ratchet algorithm; public identity keys hosted on key server; private keys never leave local client devices.\n\n---\n\n## The Three Foundational Pillars\n\n### 1. The Visual Brief\nEvery system design engagement renders a self-contained HTML visual brief at `%TEMP%\\system-design-brief-\u003Ctimestamp>.html` featuring Mermaid sequence and topology diagrams, capacity calculations, and 5-dimension scorecard evaluations.\n\n### 2. Mandatory Checkpoint Gate\nWhen designing complex multi-tier platforms or auditing enterprise architectures, the architect presents an `implementation_plan.md` artifact with `RequestFeedback: true`. STOP and await explicit user approval before generating infrastructure code or deep-module models.\n\n### 3. Explicit Anti-Patterns\nRigid boundaries prevent superficial whiteboard drawing, buzzword inflation, and ungrounded architecture sprawl.\n\n---\n\n## Anti-Patterns\n\n- **Premature Architecture Drawing** — Jumping directly into drawing boxes and database schemas before clarifying requirements and agreeing on scope boundaries.\n- **Buzzword-Driven Tool Selection** — Defaulting to trendy technologies (Kafka, GraphQL, Cassandra, Microservices) without concrete requirement or throughput justification.\n- **Monologue or Deafening Silence** — Talking non-stop without inviting feedback, or staying completely silent while diagramming without explaining thought processes.\n- **Ignoring Production Failure Modes** — Assuming 100% happy-path uptime; failing to analyze what happens when Redis nodes crash, databases hit IOPS caps, or network partitions occur.\n- **Unbudgeted Scope Blowout** — Attempting to design the entire universe of features in a single session rather than locking in 3 to 5 core functional flows.\n- **Untracked Time Allocation** — Spending 35 minutes on high-level box drawing, leaving zero time for scaling bottlenecks, concurrency locks, or trade-off analysis.\n","# Senior Software System Design Architect\n\n`system-design-architect` is the definitive system design and architectural engineering skill for designing, evaluating, and scaling production distributed systems. Synthesized directly from the curriculum and masterclass *Design Software Systems Like a Senior Engineer* by Hike Simon and Beau Carnes (freeCodeCamp.org), it enforces the **5-Step System Design Progression** and evaluates architectures across the **5 Senior Engineering Dimensions**.\n\nSystem design evaluates **how you think and communicate** across ambiguous requirements, not merely whether you memorize static diagrams. This skill operationalizes structured problem decomposition, quantitative capacity calculations, and proactive production failure mode analysis.\n\nSee [CARD.md](CARD.md) for the companion summary card, 5-stage progression matrix, and mandatory invariants checklist.\nConsult `config.default.yaml` for default capacity thresholds and latency SLO budgets.\n\n---\n\n## The 5-Stage System Design Progression\n\n```\n[1. Requirements & Scope Lock] ──► [2. Data & API Modeling] ──► [3. High-Level Architecture]\n                                                                        │\n                                                                        ▼\n[5. Trade-offs & Extension] ◄── [4. Scale & Failure Modes Deep Dive] ◄──┘\n```\n\n---\n\n## 1. Requirements Clarification & Scope Lock (5–10 min)\n\nTransform ambiguous, vague problem prompts into locked functional and non-functional specifications before designing:\n\n1. **Clarify Functional Requirements (Core Flows)**:\n   - Identify the 3 to 5 non-negotiable user capabilities: *\"What functionalities, if removed, mean this system ceases to be itself?\"* (e.g. Booking.com must search rooms and reserve inventory; WhatsApp must deliver messages and maintain connections).\n   - Isolate edge flows to explicitly mark as out-of-scope for the initial design.\n2. **Lock Non-Functional Requirements (SLAs\u002FSLOs)**:\n   - **Availability vs Consistency**: State CAP theorem priority (e.g. Booking.com demands strong consistency for room reservations; Spotify prioritizes high availability for streaming).\n   - **Latency Bounds**: Read latency SLA (e.g. \u003C 100ms p99) and write latency SLA (e.g. \u003C 200ms p99).\n   - **Durability & Security**: Data loss tolerance and encryption requirements (e.g. WhatsApp end-to-end encryption).\n3. **Capacity & Scale Estimation (Top-Down vs Bottom-Up)**:\n   - Calculate Daily Active Users (DAU), Read:Write Ratio, Average QPS, and Peak QPS ($2\\times \\text{ to } 5\\times \\text{ average}$).\n   - Estimate Network Ingress and Egress Bandwidth ($\\text{QPS} \\times \\text{payload size}$).\n   - Project Storage Growth over 1 to 5 years ($\\text{writes\u002Fday} \\times \\text{record size} \\times 365 \\times 5$).\n4. **Establish Bounded Scope**:\n   - Explicitly enumerate **In-Scope** versus **Out-of-Scope** components to prevent unbudgeted scope creep.\n\n> **Completion criterion**: Functional requirements cataloged, non-functional SLAs locked, capacity estimates calculated, and scope boundaries agreed upon.\n\n---\n\n## 2. Data & API Modeling (15–20 min)\n\nFormalize data contracts, storage paradigms, and network protocols prior to component topology:\n\n1. **Entity-Relationship Data Modeling**:\n   - Identify primary entities, attributes, and relationships (1:1, 1:N, N:M).\n   - Establish primary keys, foreign keys, partition keys, and query indexes.\n2. **Database Paradigm Selection & Technical Justification**:\n   - **Relational SQL (PostgreSQL\u002FMySQL)**: Structured relational entities, ACID transactional consistency, complex joins (e.g. Booking.com reservations, Spotify artist\u002Falbum catalog).\n   - **NoSQL Document \u002F Wide-Column (Cassandra\u002FDynamoDB\u002FScyllaDB)**: Massive write throughput, time-series data, high horizontal scale (e.g. WhatsApp message mailboxes, Spotify track playback analytics).\n   - **In-Memory Key-Value (Redis\u002FMemcached)**: Ephemeral routing tables, session state, distributed locks (Redlock), and caching layers.\n   - **Object \u002F Blob Storage (S3\u002FGCS)**: Static media assets, raw audio segments (Spotify), and user attachments.\n3. **API Contract & Protocol Specification**:\n   - Define exact API endpoints, HTTP methods, payload schemas, and response codes.\n   - Select protocol based on access pattern: REST for stateless CRUD, gRPC for inter-service RPC, WebSocket\u002FTCP for persistent bi-directional streams (WhatsApp).\n\n> **Completion criterion**: Entity schemas defined, database paradigms technically justified, API contracts drafted, and protocol selections aligned with SLAs.\n\n---\n\n## 3. High-Level Architecture Design (15–20 min)\n\nConstruct the end-to-end component topology and trace primary read and write data flows:\n\n1. **Ingress & Edge Routing Layer**:\n   - DNS routing, Anycast IP, and Global CDN edge caching for static assets and media chunks (e.g. Cloudflare, Fastly).\n   - API Gateway \u002F Reverse Proxy (Envoy, Nginx) handling TLS termination, rate limiting, authentication, and request routing.\n2. **Core Domain Microservices Tier**:\n   - Decompose monolithic domains into single-responsibility stateless services (e.g. Search Service, Booking Service, Audio Ingestion Service, Connection Manager).\n   - Ensure services scale horizontally behind load balancers.\n3. **Data & Storage Tiering**:\n   - Connect domain services to primary databases, read replicas, and caching clusters.\n   - Integrate asynchronous message brokers (Kafka, RabbitMQ, SQS) to decouple write-heavy ingestion from downstream analytics and notifications.\n4. **End-to-End Data Flow Trace**:\n   - Walk through the step-by-step **Read Flow** from client request through CDN, Cache, and Read Replica.\n   - Walk through the step-by-step **Write Flow** from client submission through Gateway, Service, Lock Manager, Primary Database, and Message Queue.\n\n> **Completion criterion**: Comprehensive architecture topology mapped with clear ingress, microservices, caches, and end-to-end read\u002Fwrite data flows.\n\n---\n\n## 4. Scalability, Failure Modes & Reliability Deep Dive (10–15 min)\n\nStress-test the architecture against production scale, concurrency bottlenecks, and single points of failure:\n\n1. **Single Point of Failure (SPOF) Identification & Elimination**:\n   - Audit every component: *\"What happens if this database, gateway, or cache fails?\"*\n   - Implement multi-AZ and multi-region active-passive or active-active redundancy with automated failover.\n2. **Horizontal Scaling & Data Partitioning (Sharding)**:\n   - Formulate sharding strategy: Range-based, Hash-based, or Consistent Hashing (Virtual Nodes).\n   - Resolve rebalancing costs, cross-shard joins, and hot-shard \u002F celebrity keys (e.g. Spotify viral song, WhatsApp popular group).\n3. **Concurrency Control & Race Condition Prevention**:\n   - **Optimistic Locking**: Version column checks (`WHERE version = :expected`) for low-contention environments.\n   - **Pessimistic Locking \u002F Distributed Leases**: Redis Redlock or ZooKeeper mutexes with short TTLs (10–15 min) to prevent double bookings in reservation systems.\n4. **Caching Strategy & Stampede Protection**:\n   - Strategy: Cache-Aside (Lazy Loading), Write-Through, or Write-Behind.\n   - Invalidation & Eviction: TTL expiration, LRU\u002FLFU policy, and distributed mutexes\u002Fprobabilistic early expiration (XFetch) to prevent cache stampedes.\n5. **Resilience & Fault Tolerance**:\n   - Circuit breakers, exponential backoff with jitter, dead-letter queues (DLQ), and graceful degradation.\n\n> **Completion criterion**: Single points of failure eliminated, sharding keys selected, concurrency locks verified, and caching stampede defenses established.\n\n---\n\n## 5. Trade-off Reflection & Extensions (5 min)\n\nConduct an objective architectural post-mortem and propose production refinements:\n\n1. **Explicit Architectural Trade-offs**:\n   - Articulate compromises made: *\"We chose Cassandra over PostgreSQL for message history to optimize write throughput at the expense of complex cross-entity transactional joins.\"*\n   - Evaluate CAP theorem trade-offs: Consistency vs Availability during network partitions.\n2. **Alternative Approaches Evaluated**:\n   - Compare rejected alternatives: Explain why WebSockets were selected over HTTP long-polling, or why Redis Redlock was chosen over pure SQL row locks.\n3. **Production Extensions & Day-2 Operations**:\n   - Observability: Distributed tracing (OpenTelemetry), metrics (Prometheus), structured logging.\n   - Multi-region deployment, disaster recovery RTO\u002FRPO targets, and cost optimization.\n\n> **Completion criterion**: Architectural trade-offs explicitly documented, alternative designs contrasted, and operational scaling roadmap finalized.\n\n---\n\n## The 5 Senior Engineering Evaluation Dimensions\n\nIn production audits and senior\u002Fstaff interviews, candidates and systems are graded across five dimensions:\n\n| Dimension | Weight | Senior \u002F Staff Evaluation Criteria |\n|---|---|---|\n| **1. Communication & Collaboration** | 20% | Treats the reviewer\u002Finterviewer as a peer colleague; asks clarifying questions upfront; validates assumptions incrementally; balances speaking with listening. |\n| **2. Structured Decomposition** | 20% | Outlines the 5-step roadmap; deconstructs ambiguous problem spaces into crisp functional blocks; maintains structured progression without erratic jumps. |\n| **3. Technical Judgment** | 25% | Selects databases, protocols, and architectural tiers strictly based on requirements and access patterns; justifies trade-offs; rejects buzzwords without merit. |\n| **4. Practical Depth** | 25% | Proactively anticipates production failure modes, concurrency race conditions, network partitions, cache stampedes, and failover scenarios. |\n| **5. Time Management & Pacing** | 10% | Actively manages pacing across the 45–60 minute session; aligns early on deep-dive focus areas; drives the discussion to a conclusive wrap-up. |\n\n---\n\n## Canonical Production Case Studies\n\n### 1. Spotify (Audio Streaming Platform)\n- **Audio Delivery:** S3 \u002F Blob Storage + Global CDN with HTTP Range Requests (`Range: bytes=0-1048575`) and pre-buffering.\n- **Metadata Management:** PostgreSQL for artist\u002Falbum\u002Ftrack catalog + Redis cluster for user playlists and recommendations.\n- **Audio Transcoding:** Asynchronous message queue (Kafka) triggering worker nodes for multi-bitrate AAC\u002FOGG encoding.\n- **Scale:** 500M+ users, > 95% CDN cache hit ratio, read:write ratio 50:1.\n\n### 2. Booking.com (Hotel Reservation & Inventory System)\n- **Zero-Double-Booking Guarantee:** 2-phase reservation state machine (`Pending` $\\rightarrow$ `Reserved` $\\rightarrow$ `Confirmed` $\\rightarrow$ `Expired`\u002F`Cancelled`).\n- **Concurrency Control:** Short-lived distributed lease (Redis Redlock with 10–15 min TTL) + Optimistic locking on room inventory (`version` column).\n- **Search & Filtering:** CQRS architecture with Elasticsearch\u002FOpenSearch read cluster decoupled from transactional booking database.\n- **Scale:** 1.1B annual reservations, 500M monthly web visits, read:write ratio 100:1.\n\n### 3. WhatsApp (Global Real-Time Messaging)\n- **Connection Management:** Stateful WebSocket \u002F TCP gateways managing millions of persistent connections per cluster.\n- **Session Registry:** Ephemeral Redis distributed routing table mapping User IDs to active Gateway instances with heartbeat monitoring.\n- **Message Storage:** Transient mailbox queues (Cassandra \u002F ScyllaDB) with automatic message purge upon client delivery ACK.\n- **E2EE Security:** Signal Protocol double ratchet algorithm; public identity keys hosted on key server; private keys never leave local client devices.\n\n---\n\n## The Three Foundational Pillars\n\n### 1. The Visual Brief\nEvery system design engagement renders a self-contained HTML visual brief at `%TEMP%\\system-design-brief-\u003Ctimestamp>.html` featuring Mermaid sequence and topology diagrams, capacity calculations, and 5-dimension scorecard evaluations.\n\n### 2. Mandatory Checkpoint Gate\nWhen designing complex multi-tier platforms or auditing enterprise architectures, the architect presents an `implementation_plan.md` artifact with `RequestFeedback: true`. STOP and await explicit user approval before generating infrastructure code or deep-module models.\n\n### 3. Explicit Anti-Patterns\nRigid boundaries prevent superficial whiteboard drawing, buzzword inflation, and ungrounded architecture sprawl.\n\n---\n\n## Anti-Patterns\n\n- **Premature Architecture Drawing** — Jumping directly into drawing boxes and database schemas before clarifying requirements and agreeing on scope boundaries.\n- **Buzzword-Driven Tool Selection** — Defaulting to trendy technologies (Kafka, GraphQL, Cassandra, Microservices) without concrete requirement or throughput justification.\n- **Monologue or Deafening Silence** — Talking non-stop without inviting feedback, or staying completely silent while diagramming without explaining thought processes.\n- **Ignoring Production Failure Modes** — Assuming 100% happy-path uptime; failing to analyze what happens when Redis nodes crash, databases hit IOPS caps, or network partitions occur.\n- **Unbudgeted Scope Blowout** — Attempting to design the entire universe of features in a single session rather than locking in 3 to 5 core functional flows.\n- **Untracked Time Allocation** — Spending 35 minutes on high-level box drawing, leaving zero time for scaling bottlenecks, concurrency locks, or trade-off analysis.\n",{"name":5,"description":7},"main","eff3b00e36d1d233ad4a4389605c82fbfa0326d3",".agents\u002Fskills\u002Fsystem-design-architect","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness","https:\u002F\u002Fgithub.com\u002FSpectreDeath","I'm here to manage stress so I wouldn't expect earth shattering break throughs I'm just an enthusiast that likes making stuff. ","2026-11-15 05:32:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add SpectreDeath\u002FBrain-Harness --skill system-design-architect",{"tool":37,"command":38},"bunx","bunx skills add SpectreDeath\u002FBrain-Harness --skill system-design-architect",{"tool":40,"command":41},"pnpm","pnpm dlx skills add SpectreDeath\u002FBrain-Harness --skill system-design-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystem-design-architect\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"CARD.md","REFERENCE","参考文档",4863,"https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystem-design-architect\u002FCARD.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"config.default.yaml",1682,"https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystem-design-architect\u002Fconfig.default.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Fsystem_design_engine.py","SCRIPT","脚本",16732,"https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystem-design-architect\u002Fscripts\u002Fsystem_design_engine.py",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7E0W6FR68J2N9CXCZTAQJFX","ui-behavior-primitive-architect","Architect, audit, and verify zero-dependency headless UI behavior primitives, WebMCP agent bridges, WAI-ARIA\u002FSSR\u002FRTL tri-modal checks, and framework expert routing. Do not use for static CSS theme styling or backend database migrations.","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-behavior-primitive-architect\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7E0VZ7JQNW34G271DENFGYP","trustgraph-ontology-governor","Govern knowledge graphs, SHACL-AF triple policies, OntologyRAG subclass validation, PROV-O dual named graphs, and Laya entropy decision scoring. Do not use for relational SQL queries or generic web scraping.","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftrustgraph-ontology-governor\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7E0VQ6Z7R45Q8QAZ4MT39EK","shim-harness-governor","Govern universal CLI agent loops, 4-tier tool permissions, ancestor-symlink workspace sandboxes, deterministic-first command routing, collision-safe MCP namespacing, and layered skill loading. Do not use for static UI styling or external SQL analytics.","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshim-harness-governor\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7E0VC18NMP1QBSRJ3TPQ7MB","graphiti-zep-memory-governor","Govern bi-temporal knowledge graphs with Graphiti future-edge clamping, MinHash\u002FLSH entity dedup, RRF\u002FMMR reranking, and Zep typed ontologies. Do not use for static SQL joins or generic web crawling.","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgraphiti-zep-memory-governor\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7E0V12ABE1RW3ZRCST8VH5Z","agora-mcp-workbench-architect","Architect, audit, and orchestrate Agora Workbench MCP servers, loopback sidecars, unified state graphs, gateway\u002Fdispatcher connectors, and policy-enforced data lakes. Do not use for static frontend CSS styling or non-MCP desktop GUI automation.","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagora-mcp-workbench-architect\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7BFYG6QT3484VC57TZ19V7P","skill-eval-assurance-runner","Evaluate and assure agent skills using small-N Wilson confidence intervals, unbiased pass^k reliability, deterministic trajectory graders, preflight boundary honesty, and sealed digest verification. Do not use for subjective prose review or unconstrained production deployment.","https:\u002F\u002Fgithub.com\u002FSpectreDeath\u002FBrain-Harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-eval-assurance-runner\u002FSKILL.md",[],[]]