<h1 align="center">
<a href="https://prompts.chat">
Expand the knowledge base **beyond the course boundary** with precisely sourced external knowledge. The result should make the student's understanding deeper and broader than the course alone provides.
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
Expand the knowledge base beyond the course boundary with precisely sourced external knowledge. The result should make the student's understanding deeper and broader than the course alone provides.
This phase operates in one of two modes, determined in Phase 0:
Mode A — Web-enabled (WebSearch + WebFetch available) Run the full three-layer search strategy below.
Mode B — Curriculum-grounded (no web access)
Do NOT search the web. Instead, expand using stable, well-established knowledge from standard CS/engineering curricula. Every claim must be marked [Standard curriculum knowledge]. Do not invent URLs, paper titles, author names, or implementation details. If you are uncertain about a claim, omit it or flag it as [Uncertain — verify before exam]. The goal is to avoid hallucination causing review distortion, not to produce maximum volume.
If Mode B was chosen but the user now wants to enable web access, stop and ask them to grant WebSearch permission before continuing.
Process expansion targets in this priority order. Hard cap: maximum 15 targets per course. If there are more, present a ranked list and ask the user to confirm which to include.
For each target, use up to three layers. Stop when you have sufficient quality material.
Search for specific, deep content:
Query tips: Use formal concept name + "implementation" / "in practice" / "architecture". Avoid generic "what is X" queries.
Search for:
For each paper: title, authors, arXiv ID or DOI, year, and 1-3 sentences on its relevance.
When multiple sources are found, note where they agree (builds confidence) and where they disagree (flags nuance). If the course material contradicts an authoritative external source, flag this explicitly.
For each target concept:
All content marked [Standard curriculum knowledge]. No fictional sources.
Organize by concept, not by search layer:
# Course Expansion: [Course Name]
## [Concept Name]
**Source in course:** [Lecture X, pp. Y-Z | Section X.Y] — [brief note on course treatment]
**Why expand:** [EXPAND marker / gap from synthesis / core concept]
### What the course doesn't cover
[The specific gap this expansion addresses.]
### Expanded understanding
[Mode A: what industry or research adds. Mode B: standard curriculum context.]
**Sources:**
- [Mode A] [Page Title](URL) — one-line note
- [Mode B] [Standard curriculum knowledge — topic area]
### Key insight
[2-4 sentences: what the student gains here that the slides don't provide.]
### Cross-verification note *(Mode A only)*
[Agreement/disagreement across sources, if applicable.]
---
Mode A: Every factual claim needs a traceable source. Acceptable forms:
[Title](full URL)Author et al., "Title" (Year). arXiv:ID or DOI:xxx[Doc Section](URL) with version[Standard curriculum knowledge — topic area] — use sparinglyNever cite a source you haven't actually retrieved. If search fails, write: "No high-quality external source found for [concept]; expansion based on course material and general domain knowledge."
Mode B: All claims [Standard curriculum knowledge]. No citations to sources not in hand.
| Concept | Mode A depth | Mode B depth |
|---|---|---|
| Core + [EXPAND] marked | All 3 layers, 300-500 words | 200-300 words, curriculum context |
| Core, well-covered | Layer 1 only, 100-200 words | 100 words, brief context |
| Gap from Phase 2 | Layers 1-2, 200-300 words | 150 words, what standard treatment adds |
| Minor/tangential | Skip or 1-2 sentences | Skip |