feat: adopt Clean Professional (Turbo AI) style for notes

src/components/UploadDialog.tsx

@@ -50,10 +50,9 @@ export default function UploadDialog({ open, onOpenChange }: { open: boolean; on
     try {
       // EXPERT OVERRIDE
       const EXPERT_PREFIX = `[EXPERT ADVISORY: ACT AS AN EXPERT ACADEMIC DATA EXTRACTION AGENT. 
-DIRECTIVE: LOSSLESS EXTRACTION. NO GROUPING POLICY.
-MANDATORY: EVERY ITEM IN A LIST (e.g. SHAPES, Underlying Skills) MUST HAVE ITS OWN ### HEADING.
-NEVER USE BULLET POINTS FOR DEFINED TERMS. EXTRACT FULL TEXT WORD-FOR-WORD.
-ALWAYS EXPAND LISTS INTO FULL SECTIONS.]\n\n`;
+STYLE: PROFESSIONAL, CLEAN MARKDOWN. NO EMOJIS ALLOWED.
+DIRECTIVE: LOSSLESS EXTRACTION. ZERO OMISSION.
+TEMPLATE: Overview -> Key Points -> Tables for Frameworks -> Sub-headings for Detailed Terms.]\n\n`;
       
       const finalContent = EXPERT_PREFIX + textContent;
 
@@ -133,10 +132,9 @@ ALWAYS EXPAND LISTS INTO FULL SECTIONS.]\n\n`;
 
         // EXPERT OVERRIDE: Prepend instructions to ensure lossless extraction even if backend is old
         const EXPERT_PREFIX = `[EXPERT ADVISORY: ACT AS AN EXPERT ACADEMIC DATA EXTRACTION AGENT. 
-DIRECTIVE: LOSSLESS EXTRACTION. NO GROUPING POLICY.
-MANDATORY: EVERY ITEM IN A LIST (e.g. SHAPES, Underlying Skills) MUST HAVE ITS OWN ### HEADING.
-NEVER USE BULLET POINTS FOR DEFINED TERMS. EXTRACT FULL TEXT WORD-FOR-WORD.
-ALWAYS EXPAND LISTS INTO FULL SECTIONS.]\n\n`;
+STYLE: PROFESSIONAL, CLEAN MARKDOWN. NO EMOJIS ALLOWED.
+DIRECTIVE: LOSSLESS EXTRACTION. ZERO OMISSION.
+TEMPLATE: Overview -> Key Points -> Tables for Frameworks -> Sub-headings for Detailed Terms.]\n\n`;
         
         const finalRawText = EXPERT_PREFIX + extractedText;
 

supabase/functions/generate_notes/index.ts

@@ -8,38 +8,48 @@ const corsHeaders = {
     "authorization, x-client-info, apikey, content-type, x-supabase-client-platform, x-supabase-client-platform-version, x-supabase-client-runtime, x-supabase-client-runtime-version",
 };
 
-const SYSTEM_PROMPT = `You are an Expert Academic Data Extraction Agent. Your singular directive is to perform a **lossless, exhaustive extraction** of the provided educational document into a highly structured format.
+const SYSTEM_PROMPT = `You are an Expert Academic Data Extraction Agent. Your directive is to perform a **lossless, exhaustive extraction** of the provided educational document into a professional, clean Markdown format.
 
-**CRITICAL MANDATE: HEADING-FIRST EXPANSION**
-1. **NO GROUPING:** If a document introduces a list (e.g., "SHAPES", "Underlying Skills", "Ancillary Skills"), you are FORBIDDEN from listing them as simple bullet points. 
-2. **MANDATORY H3 HEADINGS:** You MUST create a dedicated H3 (###) heading for EVERY individual item in a framework or list that has a definition or example in the text.
-3. **WORD-FOR-WORD DEFINITIONS:** You must extract the full, detailed definition for each item exactly as provided. Do not summarize or simplify.
-4. **ZERO OMISSION:** If a slide provides a "Scenario" and "Solution" for a specific sub-item (like "Observation"), that Scenario/Solution MUST appear directly under that item's H3 heading.
+**STYLE CONSTRAINTS:**
+- **NO EMOJIS:** You are strictly forbidden from using any emojis in the output.
+- **PROFESSIONAL TONE:** Use clear, academic language.
+- **EXHAUSTIVE DETAIL:** Do not summarize. Capture every definition, example, and scenario in full.
 
-**STRICT OUTPUT SCHEMA:**
-# [Document Title / Main Topic]
+**REQUIRED OUTPUT STRUCTURE:**
 
-**Overview:** [A brief 2-3 sentence overview of the entire document]
+# [Document Title]
 
-## [Major Section Heading]
-[Introduction to the section]
+**Overview:** This note covering [Topic] was created from a [Page Count] page document. It provides a structured walk-through of [Primary Goal of Document].
 
-### [Framework Item/Sub-topic 1]
-* **Full Definition:** [Extract exhaustive definition word-for-word]
-* **Context/Importance:** [Detailed context from text]
-* **Scenario:** [Specific scenario for this item]
-* **Solution/Result:** [Solution for this scenario]
+## Key Points
+- [High-level topic 1]
+- [High-level topic 2]
+- [High-level topic 3]
+- [High-level topic 4]
 
-### [Framework Item/Sub-topic 2]
-*(Repeat this H3 structure for EVERY item. NEVER group them into a single list)*
+## [Section Heading]
+[Detailed introduction to the section]
+
+### [Sub-topic or Framework Item]
+**Full Definition:** [Extract exhaustive definition word-for-word]
+**Detailed Example/Context:** [Extract full context and examples]
+
+**Question:** [If a scenario is presented, format the question here]
+**Answer:** [Format the solution/result here]
+
+*(Use Tables for Frameworks like SHAPES or Ancillary Skills lists)*
+| Item | Meaning/Why Important | Example |
+|------|----------------------|---------|
+| [X]  | [Y]                  | [Z]     |
 
 ## Key Scenarios & Practical Applications
-*(Capture any general scenarios that weren't specific to a sub-topic)*
+**Scenario:** [Extract general scenarios]
+**Solution/Takeaway:** [Extract solution]
 
 ## Final Summary & Synthesis
-[Comprehensive wrap-up]
+[A comprehensive wrap-up of the document's value]
 
-**FINAL INSTRUCTION:** If you are unsure whether to group or expand, ALWAYS EXPAND. Your goal is a 100% lossless recovery of the lecture's detail.`;
+**FINAL DIRECTIVE:** Maintain 100% fidelity to the source text. Every sub-topic from the document must have its own detailed heading. Never group distinct items into a single paragraph.`;
 
 Deno.serve(async (req) => {
   if (req.method === "OPTIONS") return new Response("ok", { headers: corsHeaders });