Command
Capture a debrief after a real system-design interview — the problem, your approach by stage, tradeoffs probed, curveballs, where you got stuck, and your gut outcome. Writes a structured session file under the company directory. Text-only.
Command
Capture a debrief from a real interview. Main session interviews you about what was asked, what stories you told, what surprised you, and your gut sense. Writes a session file and updates the question index for that company/JD.
Command
Run a mock behavioral interview tailored to a target company and JD. Spawns the behavioral-interviewer subagent with mapped stories as context; main session scores the transcript and writes a session file afterward.
Command
Graded 40-min coding mock: you write code in a seeded solution file while a neutral interviewer probes your approach and throws one follow-up; afterward it runs your solution against the test cases and scores a 6-axis rubric.
Command
Graded 45-minute system-design mock interview. You draw your architecture on the local Excalidraw canvas while a realistic interviewer probes what you draw, calls time, and throws one curveball; afterward it scores a 6-axis rubric, writes coach notes, and annotates your diagram with critique. Falls back to prose when…
Command
Untimed guided coding practice: you write code in a seeded solution file in your own editor; a warm interviewer hints via a ladder, runs your code, and teaches inline. Summarized, not scored.
Command
Guided, untimed system-design practice. The interviewer is a scribe — sketches your described architecture live on the local Excalidraw canvas while you talk, gives hints freely, throws no curveballs. Ends with a coverage summary (not a score). Falls back to prose-only when the canvas can't start.
Command
Add a new canonical STAR story to the behavioral story bank. Two modes — cold (you describe an experience from scratch) and CV-grounded (you point at a PDF resume; Claude reads it, suggests candidates, probes the one you pick).
Command
Migrate a legacy STAR-stories markdown file into one or more canonical story files in behavioral/stories/. Use once per legacy file; not part of the regular prep loop.
Command
Map your canonical story bank to a specific company (and optionally a JD). Caches company values, optionally fetches a JD, and writes tailored mapped stories under /behavioral/mapped-stories/ /.
Command
Drill a single story variant for delivery quality. Two modes — canonical (drill the underlying story) and mapped (drill the company-tailored variant). Critiques filler, ramble, metrics, pronoun discipline, time-to-deliver. Saves a session file but does NOT modify canonical files.
Command
Manually start (or restart) the local Excalidraw canvas server and open it in your browser. Rarely needed — the coaching commands boot it automatically. Use this to reopen a closed tab or recover a stopped server.
Command
Canonical senior-engineer walkthrough of a system design. Pulls the library entry and walks through it step-by-step — requirements, estimation, architecture, API, storage, deep dives, curveballs — rendering the architecture progressively on the local Excalidraw canvas (browser tab); falls back to structured markdown…
Skill Claude CodeCodex
Reference frameworks (STAR, SBI, CARL), anti-patterns, and standard interviewer follow-ups for behavioral interview prep. Use when extracting STAR stories from user's experience, mapping stories to a specific company or JD, running mock behavioral interviews, rehearsing behavioral story delivery, or debriefing a real…
Skill Claude CodeCodex
Reference frameworks for coding interviews — the UMPIRE method, a pattern taxonomy (two-pointers, sliding-window, BFS/DFS, backtracking, dynamic-programming, graphs, and more), a Big-O cheatsheet, Python idioms, communication guidance, and anti-patterns. Used by the coding commands (/coding-explain, /practice-coding…
Skill Claude CodeCodex
Reference frameworks (RESHADED, the 4S shorthand), capacity estimation cheatsheet, core building blocks (load balancing, caching, queues, sharding, replication, CAP), common tradeoffs, and anti-patterns for system design interview prep. Use when running /mock-sysdesign, /practice-sysdesign, /sysdesign-explain, or…