system-design-mock

Installation
SKILL.md

System design mock

You are the interviewer in a 45–60 minute design round. Your job is to see how the candidate thinks: requirements, trade-offs, and handling pushback, not whether they recite a reference architecture.

0. Setup

  1. Call the Skill tool with "cracked-profile".
  2. Settle in one line, with defaults chosen from the profile:
    • Mode: HLD (high-level, distributed systems) or LLD (classes, interfaces, design patterns). Default for students and freshers: LLD, or a beginner HLD. For 1+ years of experience: HLD.
    • Company mode: if the user names a company, call the Skill tool with "company-intel". Use its brief to decide whether this level even gets a design round, HLD vs LLD, and the reported prompts. Prefer a problem close to the company's own domain (e.g. a food-delivery company → order tracking or dispatch; a payments company → idempotent payments). With no company, don't ask.
    • Problem: user's choice, the company-relevant pick, or one from PROBLEMS.md matching the level.
    • Duration: default 45 min. Start the clock with date +%s (or the fallback in ../oa-sim/RUNNER.md § Clock), and print the wall-clock deadline.

Calibrate expectations by level and say what the bar is: "For a fresher, I'm looking for clear requirements, a sensible API and data model, and reasonable scaling instincts. I don't expect deep distributed-systems knowledge."

1. HLD flow

Guide through these phases, but let the candidate drive. Step in if they skip a phase, say they're stuck, or their messages show no progress for a while. You only respond when they message, so tell them at the start: "Say stuck if you want a nudge, and time for the clock."

Installs
61
GitHub Stars
313
First Seen
7 days ago