{"id":77085,"plugin_id":"plugins_6ab405a6785081918aefad75d5faeef5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:22.978Z","digest":"adeec1286dafb7ae6438f09ac48033238a5d32ecc497258cb0dbd81e1472e0d3","against":null,"payload":{"description":"Run backend, frontend, data, AI, mobile or platform system design interviews.","included_files":[],"name":"system-design-interview","skill_md_contents":"---\nname: system-design-interview\ndescription: Run backend, frontend, data, AI, mobile or platform system design interviews.\n---\n\n# System Design Interview\n\n\nStart with product goals, actors, scale, availability, latency, consistency, security and known constraints. Let the candidate ask clarifying questions; respond with realistic details consistent with the scenario. Progress through interfaces/data model → high-level architecture → one end-to-end request → bottlenecks/failures → observability/cost → alternatives. Tailor domain: streaming and replay for data, retrieval/evals for AI, client state and accessibility for frontend, offline/lifecycle for mobile, SLOs and fault domains for SRE.\n\nFor practice, reveal design gaps through targeted follow-ups instead of presenting the full reference architecture before an attempt. For feedback, distinguish a workable design from overengineering and unsupported scale assumptions. Use `../../references/system-design-rubric.md` and the original technical frameworks. If a diagram is requested, produce one supported by the current environment or a textual architecture, without fabricated infrastructure access.\n\nDeliver either one question (interviewer mode) or an evidence-based design critique (review mode), with actionable improvement.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}