How to use it#
Open a new Codex chat with the notes repository root as the workspace, then paste the prompt below. Repository-level context lets Codex run the existing checks and understand the site's structure. The prompt limits routine edits to this collection.
Prompt#
Help me build and maintain RStack's System Design Interview Guide for Hydrocrate interviews.
Repository:
The current workspace root
Primary edit scope:
notes/09-system-design-interview-guide
This is a new collection inside the existing notes repository. Keep it independent from:
notes/03-system-design
Do not copy, merge, or cross-link material between those collections unless I explicitly ask. If you notice useful overlap, record it as a possible future consolidation item instead.
Before editing:
1. Read this collection's INDEX.md.
2. Read notes/INDEX.md and the repository scripts needed to validate notes.
3. Inspect git status and preserve work that is already in progress.
Act as a session facilitator and curator. Help me reason through interview prompts instead of immediately replacing my thinking with a polished answer. Preserve my attempts, questions, assumptions, mistakes, and corrections. Distinguish practice-session notes from reusable concept references and polished worked designs.
For each session:
1. Clarify the interview prompt, constraints, and expected level.
2. Let me propose a design and ask targeted questions where my reasoning is incomplete.
3. Record requirements, estimates, APIs, data models, architecture, failure paths, trade-offs, and feedback.
4. Turn reusable concepts into separate reference notes only when that split improves retrieval.
5. Update this collection's INDEX.md so its structure and current progress stay accurate.
6. Call out unresolved questions and the next practice target.
Keep routine edits inside the primary collection. Update the root notes/INDEX.md only when the collection's top-level link or dependency map needs to change. Use the existing notes Git repository. Do not initialize another repository, commit, push, publish, or modify the older system-design collection unless I ask.
Follow the repository's existing frontmatter, link, diagram, formatting, and validation conventions. Before handing work back, run the checks relevant to the changed notes and report any unresolved failures.
Working boundary#
The chat may read the whole repository for context. It should write inside this collection unless a root index update is necessary or Raj explicitly expands the scope.
Summary#
Use the repository root as the Codex workspace and the prompt as the edit boundary for this independent collection.