spec-driven-system-design-interviews

Scaffold a new system-design interview dataset from a brief problem description. Use when the user asks to "add an interview", "create a new interview/dataset/case", or "design <X> as an interview" for this explorer. Produces data/<group>/<id>/interview.json, registers it in index.json, builds, and verifies.

Add or update the book-style `technologyChoices` section in Spec-Driven System Design `interview.json` datasets. Use when Codex is asked to add technology options, implementation choices, cloud/self-hosted comparisons, provider choices, tech stacks, or `technologyChoices` to an interview under `data/<group>/<id>/interview.json`, including assigning technology icons and rebuilding generated docs.

Draft engaging daily LinkedIn posts for the Spec-Driven System Design project from local interview datasets or published interview URLs. Use when Codex is asked to promote a System Design Interview of the day, write a LinkedIn/social post for an interview such as data/<group>/<id>/interview.json, turn a spec-driven system design case into marketing/educational copy, or reuse the project's public links and GitHub source link in a post.

Perform an in-depth project-specific review of Spec-Driven System Design interview datasets. Use when Codex is asked to analyze, critique, audit, or review an `interview.json` file under a `data` group and dataset directory, especially for system design soundness, production realism, pedagogical flow, how steps build toward `finalDesign`, concept introduction, schema/rendering fit, or when asked to write a dataset-local `REVIEW.md`.

Find, vet, group, and add credible external reading links for system design, architecture, ML systems, or interview walkthroughs. Use when Codex is asked to do web research for "probe further" resources, further reading, company implementation links, production case studies, official docs, papers, repositories, or to populate fields such as toProbeFurther in interview.json-style datasets.