system-design-interview
Structure a complete system design answer for interview questions or real architecture sessions. Use when asked to design a system, answer a system design interview question, or architect a solution at scale. Produces a structured answer covering requirements, capacity estimates, high-level design, component deep-dives, trade-offs, and follow-up considerations.
npx skills add mohitagw15856/pm-claude-skills --skill system-design-interview --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# System Design Interview Skill Structures a complete, interview-grade system design response — covering clarifying questions, requirements, capacity estimates, architecture, component design, and trade-offs. Works equally well for real architecture sessions. ## Required Inputs Ask for these if not provided: - **The system to design** (e.g. "design a URL shortener", "design a notification service", "design Twitter's feed") - **Scope** (interview prep / real architecture decision / practice run) - **Scale target** (rough numbers: DAU, requests/sec, data volume — or "assume typical web scale") - **Constraints or priorities** (e.g. prioritise availability over consistency, minimise cost, low-latency reads) - **Time available** (interview context only: 30 / 45 / 60 minutes — skip for real architecture sessions) - **Emphasis** (optional — any area to go deeper on, e.g. "focus on the DB design" or "spend more time on scaling") ## Output Format ### 1. Clarifying Questions Before designing, list 4–6 questions that would change the design. Examples: - Read-heavy or write-heavy? (affects caching and DB choice) - Global or single-region? (affects latency requirements) - Strong or eventual con
- Required Inputs
- Output Format
- 1. Clarifying Questions
- 2. Functional Requirements
- 3. Non-Functional Requirements
- 4. Capacity Estimation
- 5. High-Level Architecture
- 6. Component Deep-Dive
- 7. Data Flow
- 8. Scaling Bottlenecks and Mitigations
- 9. Trade-offs and Alternatives
- 10. Follow-up Considerations
- Quality Checks
- Anti-Patterns
What does the system-design-interview skill do?
Structure a complete system design answer for interview questions or real architecture sessions. Use when asked to design a system, answer a system design interview question, or architect a solution at scale. Produces a structured answer covering requirements, capacity estimates, high-level design, component deep-dives, trade-offs, and follow-up considerations.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill system-design-interview --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.