Use when a user is designing or building a new API, endpoint, or service surface and needs a design decision made — not just a concept explained. Triggers on: "designing/planning/building a new endpoint (set), API, or service contract", picking a protocol/style (REST vs gRPC vs GraphQL vs SOAP, websockets, webhooks)…
Use when explaining or looking up a DevOps or CI/CD concept — Kubernetes, Docker, deployment strategies (blue-green/canary/rolling), Terraform, CI/CD pipelines, logging/tracing/metrics observability, DevOps vs SRE vs platform engineering. Recall, not strategy selection (use choose-deployment-strategy).
Use when explaining or looking up a dev tool, Git, or Linux concept — Git internals and merge-vs-rebase, Linux commands/permissions/filesystem, diagram-as-code tools, shipping code to production, causes of 100% CPU usage. Recall.
Use when looking up how to design a specific well-known system — Gmail, Google Docs, Google Maps, stock exchange, chat app, push notifications, live streaming, search engine, proximity service, quadtree, S3 upload, internationalization. Reference designs.
Use when a user is making a system resilient / fault-tolerant / highly available and needs a design — not just a concept explained. Triggers on: "this must survive downstream outages", "add retries / circuit breakers / failover", ensuring idempotency, timeouts, distributed locks, disaster recovery / RTO-RPO…
Use when explaining or looking up a payment or fintech concept — VISA/ACH/UPI/SWIFT flows, Apple/Google Pay, reconciliation, double-payment avoidance, hotspot accounts, digital wallets, foreign exchange. Recall, not payment-flow design (use design-a-payment-flow).
Use when looking up how a specific company architected its system — Netflix, Uber, Twitter, Discord, Airbnb, TikTok, Figma, Reddit, Slack, Stack Overflow, YouTube, Disney Hotstar. Reference for proven real-world architectures.
Use when a user is scaling a system or designing for high load / traffic growth and needs a plan — not just a concept explained. Triggers on: "how do we handle X requests", "our API falls over under load", "scale this to millions of users", and decisions about caching, CDN, load balancing, read replicas, sharding…
Use when a user is securing a system or designing authentication / authorization and needs a decision — not just a concept explained. Triggers on: "design login/auth for X", choosing session vs JWT vs OAuth2 vs SSO, HTTPS/TLS setup, encryption choice, permission/RBAC/ABAC model, secret management, or API security…
Use when explaining or looking up a security concept — authentication (cookie/session/JWT/SSO/OAuth2), HTTPS/TLS handshake, symmetric vs asymmetric encryption, digital signatures, permission systems, VPN, SSH, 2FA. Recall, not secure-design decisions (use secure-the-system).
Use when explaining or looking up a software-architecture concept — microservices best practices, domain-driven design, design patterns, MVC/MVP/MVVM/VIPER, orchestration vs choreography, architectural patterns, system-design tradeoffs, OOP concepts. Recall, not full design.
Use when explaining or looking up a software-development concept — garbage collection, load-balancing algorithms, OOP pillars, programming paradigms, concurrency vs parallelism, data structures, big vs little endian, server types, multithreading patterns. Recall.