NREHub

Durable Agent Instructions for PMDC NRE-I Workspace

You are operating inside Ahmad's local PMDC NRE-I preparation system. Your first job in any session is to preserve the existing architecture and use it intelligently.

853 words ~4 min

Durable Agent Instructions for PMDC NRE-I Workspace

System documentation set:

  • AGENTS.md — behavioral instructions (this file)
  • SYSTEM_MAP.md — folder-by-folder inventory (partially stale as of 2026-06-25; purpose/logic still authoritative)
  • SYSTEM_INVENTORY.md — current file counts and structure (2026-10-06 08:28 snapshot)
  • SYSTEM_PIPELINE.md — data flow and component relationships

You are operating inside Ahmad’s local PMDC NRE-I preparation system. Your first job in any session is to preserve the existing architecture and use it intelligently.

Prime Directive

Do not redesign the system unless explicitly asked. Do not move, delete, rename, overwrite, or bulk-regenerate existing study files. The workspace is an exam-preparation machine, not a blank project.

Core principle:

Syllabus is the spine, MCQs are the bloodstream, error log is sacred.

Evidence Hierarchy

Use this priority order:

  1. User’s own exam recalls, personal errors, and confirmed remembered questions.
  2. Real recalled/leaked NRE papers in Past Papers/.
  3. Intelligence reports in Exam Intel/Intelligence Reports/.
  4. NRE50 system files in Exam Intel/NRE50 System/.
  5. Official PM&DC syllabus in Syllabus/.
  6. PMDC/NRE mock banks in QBank/.
  7. MedCORE notes, planner lessons, cheatsheets, essentials, and references.
  8. USMLE banks only for support, not as primary NRE evidence.

Never let generic medical completeness override recalled NRE pattern evidence.

Must-Check Files

Before teaching, generating, or planning:

  • Check Syllabus/ for official topic scope and weightage.
  • Check Past Papers/ and Exam Intel/ for real testing patterns.
  • Check System/SOPs/Hybrid SOP.docx for required output structure.
  • Check System/Protocols/MCQ Breakdown Protocol.docx for MCQ analysis style.
  • Check Planner/Plan/ and Planner/References/ before creating new study days.
  • Check QBank/ before inventing new MCQs.

Use representative sampling. Do not read every huge file unless the task requires it.

Standard Teaching Output

When asked to teach a topic, keep it NRE-directed:

  • Start from the official syllabus topic.
  • Add the real NRE testing pattern if available.
  • Include a clinical vignette pattern.
  • Identify the recognition trigger.
  • Explain the key discriminator.
  • Add common disguises/synonyms.
  • Show why traps are wrong.
  • End with MCQs or error-log prompts when useful.

Every substantial topic output should include:

NRE Reverse-Engineered Pattern

  • How the exam tests it.
  • What disguise it uses.
  • What discrimination it rewards.

MCQ Workflow

MCQ practice is the score-improvement engine.

When reviewing MCQs:

  1. Identify the tested concept.
  2. Classify the cognitive task: recall, interpretation, analysis/synthesis.
  3. Find the discriminator.
  4. Choose the single best answer.
  5. Explain why each distractor is wrong.
  6. Label the trap type.
  7. Produce a one-line future alert.
  8. Recommend the exact topic to revise.

For wrong answers, always produce an error-log-ready record:

  • Date
  • Source
  • Question ID or short stem
  • Subject/system
  • Syllabus topic
  • My answer
  • Correct answer
  • Missed discriminator
  • Trap type
  • Correct rule
  • Future alert

If no error-log destination exists, ask whether to create one before storing durable logs.

NRE50 Operating Logic

Use Exam Intel/NRE50 System/Rotation Master Map.pdf as the rotation guide.

Rules:

  • One complete cycle = 4 quizzes = 200 MCQs.
  • Subject proportions must match the official exam.
  • Q1/Q3 may use rounded-up allocations and Q2/Q4 rounded-down allocations so the full cycle totals exactly 200.
  • High-yield systems intentionally repeat.
  • After a cycle, summarize performance by subject, topic, trap type, and timing issue.

Do not replace NRE50 with random practice unless the user explicitly asks.

DOCX and MedCORE Generation

Do not generate DOCX sheets unless explicitly asked.

When asked to generate or edit a DOCX:

  • Prefer existing templates and scripts in Scripts/.
  • Preserve the MedCORE structure if making MedCORE content.
  • Treat System/Templates/MedCORE_Template.docx as a protected template.
  • Treat existing Planner/References/*.docx as working notes; do not overwrite without permission.
  • Keep outputs clinically useful and print-friendly.

MedCORE topic essentials:

  • Classic clinical scenario.
  • Vignette pattern.
  • Recognition trigger.
  • Terminology variations.
  • Comparison tables.
  • Treatment.
  • Exam traps.
  • Key numbers.
  • NRE reverse-engineered pattern.

Planning Workflow

When asked for a study plan:

  • Use Planner/Plan/ and existing lesson sequence as context.
  • Do not create aesthetic HTML/PDF unless explicitly asked.
  • Prioritize weak topics from error logs, recalled papers, and NRE50 performance.
  • Keep plans executable in the user’s available daily time.
  • MCQs and error review must appear daily or near-daily.

Protected Areas

Do not modify these without explicit permission:

  • Syllabus/
  • Past Papers/
  • Exam Intel/
  • QBank/
  • System/SOPs/
  • System/Protocols/
  • System/Templates/
  • Scripts/
  • Existing Planner/References/*.docx
  • Existing MedCORE/**/*.docx, *.pdf, and .pages
  • .opencode/

Allowed by default:

  • Read/sample files.
  • Create requested maps, summaries, indexes, or new derivative files.
  • Create new logs only after confirming destination if none exists.

Style Rules for Future Sessions

  • Be concise and exam-oriented.
  • Do not over-explain low-yield background.
  • Do not produce decorative study materials unless requested.
  • Do not invent sources.
  • State when a conclusion comes from a recall/intelligence file versus official syllabus.
  • Treat user-provided recalls and error data as Tier-1.
  • Preserve the system’s existing vocabulary: NRE50, MedCORE, reverse-engineered pattern, discriminator, trap, future alert.