<h1 align="center">
<a href="https://prompts.chat">
This file defines how to find and evaluate standard curriculum coverage for **any academic subject**. It replaces hardcoded topic lists — which only covered 8 CS/engineering subjects — with a live search approach that works for any course a student might take.
Loading actions...
<a href="https://prompts.chat">
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend linting, type safety, or ESLint configuration.
risks
This file defines how to find and evaluate standard curriculum coverage for any academic subject. It replaces hardcoded topic lists — which only covered 8 CS/engineering subjects — with a live search approach that works for any course a student might take.
From the user's input, determine:
Run 2-3 targeted searches. Prefer queries that surface syllabi, textbook tables of contents, and university course pages over generic explainers.
Recommended query patterns:
"[subject] university course syllabus topics"
"[subject] undergraduate curriculum [key textbook author OR university name]"
"[subject] course outline week by week"
"[subject] exam topics [university level]"
Examples:
"organic chemistry undergraduate syllabus topics""econometrics course outline core topics""Byzantine history university course curriculum""linear algebra textbook Strang table of contents"Target sources (in priority order):
From the search results, identify:
Discard topics that are:
If a textbook is clearly associated with this subject, check its table of contents as a sanity check. A topic in every major textbook is definitively "core." A topic in no major textbook is either niche or misidentified.
If web search is unavailable, use world knowledge. Apply this reasoning:
State explicitly: "No web search available — outline based on standard curriculum knowledge. Please verify against your actual course syllabus."
For well-established STEM subjects (mathematics, physics, chemistry, biology, standard engineering disciplines, core CS courses), world knowledge is reliable enough to generate a solid outline.
For humanities, social sciences, or niche technical subjects, add a stronger caveat and encourage the user to provide a reference syllabus or textbook.
After identifying the standard coverage for the subject, compare against Phase 1 extractions:
| Gap type | Action |
|---|---|
| Core topic entirely missing | High-priority Phase 3 target; flag prominently in synthesis |
| Core topic covered superficially | Medium-priority; note the gap and depth needed |
| Common topic missing | Low-priority; mention as "this course does not cover X, which standard curricula often include" |
| Specialized topic missing | Note only if student's Phase 0 emphasis indicated interest in this area |
Always be specific about the gap: don't just say "thermodynamics is missing" — say "the course covers reaction enthalpy (Lecture 3) but does not treat entropy or Gibbs free energy, which are core to understanding reaction spontaneity in standard physical chemistry curricula."
For the 8 most common CS/engineering courses (OS, Networks, DSA, Databases, Computer Architecture, ML/DL, Distributed Systems, Compilers), web search is still the preferred approach. World knowledge fallback is reliable for these subjects given their stable, well-documented curricula.