Imported from Muhammad-Ali-Asghar/Interview-Material (AGENTS.md). Install upstream with npx skills add Muhammad-Ali-Asghar/Interview-Material. Copyright stays with the author.

AGENTS.md — Interview Material

Quick Facts

• Purpose: Backend interview preparation — 50+ atomic notes covering roadmap.sh backend topics (system design, databases, OOP, DSA, networking, security).
• File location: All .md files sit flat at repo root. No subdirectories. Do not create src/, memory/, or any subfolder without explicit instruction.
• Single commit repo (c2aec9a). No CI, no tests, no build system. Just markdown.

File Convention

Every file follows this exact pattern:

YYYYMMDD_Topic_Name.md

Frontmatter (required):

type: Atomic_Note
tags: [topic1, topic2, interview-prep]
links: ["[[Related_File_1]]", "[[Related_File_2]]", "[[Index_Topic]]"]

• type is always Atomic_Note (or Structure_Note for overview/map files).
• tags — kebab-case, comma-separated in brackets.
• links — always [[FileName]] (no .md extension). At least 2 links. One should be an [[Index_Topic]] entry.

Writing Style

Must match exactly (read 2–3 existing files before writing a new one):

1. Opening: > Context: Brief one-liner explaining what this note answers.
2. First paragraph: Named expert perspective — From the perspective of <Expert Name>... — then the core insight in one sentence.
3. Structure: Clear section headers, bullet-friendly explanations, first-principles focus. Avoid paragraphs longer than 6 lines.
4. Voice: Interview-prep tone — concise, mechanical truth, no fluff. Explain why something works, not just what it is.
5. Length: 40–80 lines typical. One atomic concept per file.

Adding a New Topic (Workflow)

1. Read 2–3 existing .md files from this repo to calibrate style (e.g., 20260316_OOP_First_Principles.md and 20260316_Caching_Strategies_Redis_Memcached_HTTP.md).
2. Create file: YYYYMMDD_Topic_Name.md at repo root.
3. Write frontmatter with type: Atomic_Note, relevant tags, and links pointing to:
   • At least 1 existing related file
   • 1 [[Index_Topic]] entry (create the Index_ file if it doesn't exist)
4. Write content matching the established style (expert perspective, atomic, first-principles).
5. Create/update the Index_ file (Index_Topic.md) — list new note as an entry point.
6. Commit: git add -A && git commit -m "Add <Topic> interview note".
7. Save in Memory save the new topic in memory keep the file in the current directory add a new index in the memory file

Cross-Referencing (Wikilinks)

Files use [[FileName]] syntax for cross-references. These are human-readable pointers, not auto-resolved. Always:

• Use the filename without the date prefix and .md when linking to an Index: [[Index_System_Design]].
• Use the full filename without .md when linking to another note: [[20260316_Caching_Strategies_Redis_Memcached_HTTP]].

What To Avoid

• Don't create subdirectories — all .md stays in root.
• Don't use relative paths like ../ or ./.
• Don't write without reading 2+ existing files first (style drift is the #1 mistake).
• Don't skip the Index_ file update — orphan notes defeat the knowledge network.