fix: Refine prompts to ground examples in source chunk

Author: debjitbis08

apps/web/src/lib/cards/prompts.ts

@@ -90,8 +90,10 @@ INSTRUCTIONS:
    - Use natural prose for narrative content. Separate distinct ideas into multiple paragraphs using \\n\\n.
    - Use backtick code spans for inline code references. For multi-line code, you MUST use fenced code blocks with triple backticks and a language tag — write them as \`\`\`python\\n...code...\\n\`\`\` inside the JSON string. Never write a bare language name on its own line without the triple backticks.
 6. SHOW, DON'T TELL: If the passage teaches through examples (code snippets, calculations, derivations, worked problems, formulas in action), the card MUST also teach through examples. Do NOT replace concrete examples with prose descriptions of what the examples do. Instead, create a SHORT, SIMPLIFIED example inspired by the original (a few lines of code, 2-3 steps of a calculation, a compact derivation). A brief sentence of context is fine, but the example is the core of the card. Prose-heavy summaries of example-driven content are a failure mode — avoid them.
+   - All examples in the card MUST use names, values, and expressions from the source text exactly as written. Do not invent new names, values, or examples.
 7. FIGURES: If figures are attached above, you MUST include an "images" array on the primary "discover" card with the indices of figures that help explain the concept. Diagrams, plots, charts, and illustrations are almost always worth including. However, do NOT include figures that are just equations, formulas, or tables of numbers — reproduce those as LaTeX instead. Only include truly graphical images (diagrams, plots, charts, photos, illustrations, graphs, flowcharts).
-8. CRITICAL — every card MUST be completely self-contained. The reader will see the card WITHOUT the source text — they may never read it. Never open with or use phrases like "The passage…", "In this passage…", "This passage…", "The text…", "The author argues…", "According to the passage…", "This section…", "The excerpt…", or any phrasing that assumes the reader has just read something. Instead, lead with the subject itself: name the concept, the author (by name), the book, or the idea directly. Write as if you are explaining the topic to someone who has never seen the source material.
+8. ACCURACY — cards must faithfully represent what the source passage actually says. Do NOT hallucinate facts, invent examples, or substitute generic content. Every claim and example in the card must be traceable to the source passage. Reminder: all examples must be grounded in the source chunk. Do not substitute invented examples.
+9. CRITICAL — every card MUST be completely self-contained. The reader will see the card WITHOUT the source text — they may never read it. Never open with or use phrases like "The passage…", "In this passage…", "This passage…", "The text…", "The author argues…", "According to the passage…", "This section…", "The excerpt…", or any phrasing that assumes the reader has just read something. Instead, lead with the subject itself: name the concept, the author (by name), the book, or the idea directly. Write as if you are explaining the topic to someone who has never seen the source material.
 
 Respond with ONLY a JSON array. Each element has "type" and "content" (an object whose shape depends on the type):
 

apps/worker/src/cards/prompts.ts

@@ -82,7 +82,9 @@ INSTRUCTIONS:
    - Use natural prose for narrative content. Separate distinct ideas into multiple paragraphs using \\n\\n.
    - Use backtick code spans for inline code references. For multi-line code, you MUST use fenced code blocks with triple backticks and a language tag — write them as \`\`\`python\\n...code...\\n\`\`\` inside the JSON string. Never write a bare language name on its own line without the triple backticks.
 6. SHOW, DON'T TELL: If the passage teaches through examples (code snippets, calculations, derivations, worked problems, formulas in action), the card MUST also teach through examples. Do NOT replace concrete examples with prose descriptions of what the examples do. Instead, create a SHORT, SIMPLIFIED example inspired by the original (a few lines of code, 2-3 steps of a calculation, a compact derivation). A brief sentence of context is fine, but the example is the core of the card. Prose-heavy summaries of example-driven content are a failure mode — avoid them.
-7. CRITICAL — every card MUST be completely self-contained. The reader will see the card WITHOUT the source text — they may never read it. Never open with or use phrases like "The passage…", "In this passage…", "This passage…", "The text…", "The author argues…", "According to the passage…", "This section…", "The excerpt…", or any phrasing that assumes the reader has just read something. Instead, lead with the subject itself: name the concept, the author (by name), the book, or the idea directly. Write as if you are explaining the topic to someone who has never seen the source material.
+   - All examples in the card MUST use names, values, and expressions from the source text exactly as written. Do not invent new names, values, or examples.
+7. ACCURACY — cards must faithfully represent what the source passage actually says. Do NOT hallucinate facts, invent examples, or substitute generic content. Every claim and example in the card must be traceable to the source passage. Reminder: all examples must be grounded in the source chunk. Do not substitute invented examples.
+8. CRITICAL — every card MUST be completely self-contained. The reader will see the card WITHOUT the source text — they may never read it. Never open with or use phrases like "The passage…", "In this passage…", "This passage…", "The text…", "The author argues…", "According to the passage…", "This section…", "The excerpt…", or any phrasing that assumes the reader has just read something. Instead, lead with the subject itself: name the concept, the author (by name), the book, or the idea directly. Write as if you are explaining the topic to someone who has never seen the source material.
 
 Respond with ONLY a JSON array. Each element has "type" and "content" (an object whose shape depends on the type):