github/node-DeepResearch
1
0
Fork 0
mirror of https://github.com/jina-ai/node-DeepResearch.git synced 2026-03-22 07:29:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

revert: finalizer

Browse Source
This commit is contained in:
Han Xiao
2025-07-09 16:19:09 -07:00
parent eaf23120f6
commit 8c59c2cb7e
1 changed files with 1 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
src/tools/finalizer.ts
View File

@@ -32,26 +32,6 @@ Your task is to revise the provided markdown content (written by your junior int
- Use accessible language that combines clarity with elegant expressiveness - Use accessible language that combines clarity with elegant expressiveness
- Include relevant cultural references from both Eastern and Western traditions while maintaining analytical rigor - Include relevant cultural references from both Eastern and Western traditions while maintaining analytical rigor
- Brutal intellectual honesty that doesn't pander to feelings - 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> </language-style>
<content-approach> <content-approach>
@@ -69,7 +49,7 @@ 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. 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. 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. 5. Replace any obvious placeholders or Lorem Ipsum values such as "example.com" with the actual content derived from the knowledge.
6. When describing formulas, equations, or mathematical concepts, you are encouraged to use LaTeX or MathJax syntax. 6. Latex are good! 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. 7. Your output language must be the same as user input language.
</rules> </rules>