feat: improve lang styling

src/tools/finalizer.ts

@@ -16,12 +16,12 @@ function getPrompt(mdContent: string, allKnowledge: KnowledgeItem[], schema: Sch
 Your task is to revise the provided markdown content (written by your junior intern) while preserving its original vibe, delivering a polished and professional version.
 
 <structure>
-- Begin with a blunt, fact-driven, and unapologetically statement of the main question or issue you'll address
+- Begin with fact-driven statement of the main question or issue you'll address
 - Develop your argument using a logical progression of ideas while allowing for occasional contemplative digressions that enrich the reader's understanding
 - Organize paragraphs with clear topic sentences but vary paragraph length to create rhythm and emphasis, do not use bullet points or numbered lists.
 - Write section headers as single phrases without colons (##, ###) to organize long content. Strictly avoid headers with colons like 'The Digital Revolution: Transforming Modern Business'. Instead use 'Digital Transformation in Business'.
 - Present facts, quotes and data points with minimal hedging
-- Conclude with both a definitive statement of your position and a thought-provoking reflection that leaves readers pondering deeper implications and insane hot-takes.
+- Conclude with both a definitive statement of your position and a thought-provoking reflection that leaves readers pondering deeper implications.
 - Remove all disclaimer and copyright notices at the end of the content.
 </structure>
 
@@ -32,6 +32,26 @@ Your task is to revise the provided markdown content (written by your junior int
 - Use accessible language that combines clarity with elegant expressiveness
 - Include relevant cultural references from both Eastern and Western traditions while maintaining analytical rigor
 - Brutal intellectual honesty that doesn't pander to feelings
+- Use simple language: Write plainly with short sentences.
+  Example: "I need help with this issue."
+- Avoid AI-giveaway phrases: Don't use clichés like "dive into," "unleash your potential," etc.
+  Avoid: "Let's dive into this game-changing solution."
+  Use instead: "Here's how it works."
+- Be direct and concise: Get to the point; remove unnecessary words.
+  Example: "We should meet tomorrow."
+- Maintain a natural tone: Write as you normally speak; it's okay to start sentences with "and" or "but."
+  Example: "And that's why it matters."
+- Avoid marketing language: Don't use hype or promotional words.
+  Avoid: "This revolutionary product will transform your life."
+  Use instead: "This product can help you."
+- Keep it real: Be honest; don't force friendliness.
+  Example: "I don't think that's the best idea."
+- Simplify grammar: Don't stress about perfect grammar; it's fine not to capitalize "i" if that's your style.
+  Example: "i guess we can try that."
+- Stay away from fluff: Avoid unnecessary adjectives and adverbs.
+  Example: "We finished the task."
+- Focus on clarity: Make your message easy to understand.
+  Example: "Please send the file by Monday."
 </language-style>
 
 <content-approach>
@@ -49,7 +69,8 @@ Your task is to revise the provided markdown content (written by your junior int
 3. Fix any broken tables, lists, code blocks, footnotes, or formatting issues.
 4. Tables are good! But they must always in basic HTML table syntax with proper <table> <thead> <tr> <th> <td> without any CSS styling. STRICTLY AVOID any markdown table syntax. HTML Table should NEVER BE fenced with (\`\`\`html) triple backticks.
 5. Replace any obvious placeholders or Lorem Ipsum values such as "example.com" with the actual content derived from the knowledge.
-6. Your output language must be the same as user input language.
+6. When describing formulas, equations, or mathematical concepts, you are encouraged to use LaTeX or MathJax syntax.
+7. Your output language must be the same as user input language.
 </rules>