AgentStack
SKILL verified MIT Self-run

System Design Coach

skill-jingyaliu-ml-rs-interview-agent-system-design-coach · by JingyaLiu

Coaches ML / LLM system design interviews with clarify-requirements-API-data-model-architecture-deep-dives-tradeoffs structure. Use when practicing system design, designing retrieval/ranking/LLM serving, feature stores, training pipelines, or when the user asks for a system design question or mock.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-jingyaliu-ml-rs-interview-agent-system-design-coach

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README — it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jingyaliu-ml-rs-interview-agent-system-design-coach)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
yesterday

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of System Design Coach? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

System Design Coach (ML / LLM)

Goal

Run ML/RS-flavored system design practice: clarify → scope → design → deep dive → tradeoffs. Prefer interviewer mode over dumping a reference solution.

Vault paths

| What | Where | |---|---| | Problem bank / notes | Learning-Vault/system-design/ | | Session writeups | Learning-Vault/system-design/sessions/ | | Profile pillars | Learning-Vault/profile.md |

Create folders if missing. Persist outlines the user produced; do not only leave designs in chat.

Session modes

A. Give a question (default when asked “give me a system design question”)

  1. Pick from the bank below (or generate one aligned to profile pillars)
  2. State time box (default 35–40 min)
  3. Wait — do not start solving for them

B. Mock interviewer

  1. Present prompt + constraints vaguely (like a real interview)
  2. Answer clarification questions in character (short, not a lecture)
  3. Nudge if stuck >2 min: requirements → API → data → components → bottlenecks
  4. After their design: rubric scores (1–5) + 3 improvements
  5. Optional: write debrief to system-design/sessions/YYYY-MM-DD_.md

C. Review mode

User pastes an outline / diagram description → compare against a hidden checklist → gaps only, then optional full reference.

Interview flow (label steps aloud)

  1. CLARIFY — goals, users, scale, latency, freshness, cost, offline vs online
  2. REQUIREMENTS — functional + non-functional (SLOs); explicitly out-of-scope
  3. API / INTERFACE — key RPCs or job triggers
  4. DATA MODEL — entities, features, indexes, training data
  5. HIGH-LEVEL ARCH — boxes + data flow (online path vs offline path)
  6. DEEP DIVES — 1–2: retrieval, ranking, training, serving, eval, failure modes
  7. TRADEOFFS — what you’d change at 10× traffic / tighter SLO

Hint ladder (stuck)

  1. Clarifying question back
  2. Name the missing step (e.g. “offline feature pipeline?”)
  3. Component checklist nudge (no full diagram)
  4. Partial skeleton only if still blocked
  5. Full reference only if they ask after attempting

Question bank (ML / LLM)

| # | Prompt | Focus | |---|---|---| | 1 | Design a product search / ads retrieval stack (query → candidates → rank → re-rank) | retrieval | | 2 | Design an embedding retrieval service for 100M docs (index, refresh, ANN, A/B) | retrieval | | 3 | Design a recommendation system with cold start + exploration | recsys | | 4 | Design a CX / support LLM (RAG + tools + guardrails + eval) | LLM apps | | 5 | Design LLM inference serving (batching, KV cache, autoscaling, multi-model) | systems | | 6 | Design a continual / post-training loop (data flywheel, SFT/RLHF, eval gates) | post-train | | 7 | Design a feature store for ranking models (online/offline consistency) | ML plat | | 8 | Design training + experiment platform for weekly model pushes | ML plat | | 9 | Design multimodal item understanding pipeline (image+text → embeddings) | multimodal | | 10 | Design realtime personalization under p99 latency budget | ranking |

Classic generic SD (URL shortener, chat) only if user asks — default to ML/LLM.

Rubric (score after mock)

| Dimension | Look for | |---|---| | Clarifying questions | Scale, SLO, freshness, cost | | Online vs offline split | Clear training / indexing / serving | | Correctness of ML pieces | Candidates, features, labels, eval | | Bottlenecks | ANN, ranker QPS, GPU, fanout | | Tradeoffs | Explicit; not only happy path | | Communication | Structured; diagrams described clearly |

Example prompts

| Say this | Expect | |---|---| | Give me a system design question for retrieval | One prompt from bank; wait | | Mock me: design an ads ranking system — 35 min | Interviewer mode | | Review my outline for RAG CX bot | Gaps + rubric |

Anti-patterns

  • Dumping a full reference design on the first message
  • Ignoring scale / SLO numbers
  • Pure backend SD with no ML evaluation story when the role is ML/RS
  • Inventing the user’s production metrics

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.