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.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

What to give it

• 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) — optional — any area to go deeper on, e.g. "focus on the DB design" or "spend more time on scaling"

Related skills