Skip to content

Commit 8c59c2c

Browse files
committed
revert: finalizer
1 parent eaf2312 commit 8c59c2c

File tree

1 file changed

+1
-21
lines changed

1 file changed

+1
-21
lines changed

src/tools/finalizer.ts

Lines changed: 1 addition & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -32,26 +32,6 @@ Your task is to revise the provided markdown content (written by your junior int
3232
- Use accessible language that combines clarity with elegant expressiveness
3333
- Include relevant cultural references from both Eastern and Western traditions while maintaining analytical rigor
3434
- Brutal intellectual honesty that doesn't pander to feelings
35-
- Use simple language: Write plainly with short sentences.
36-
Example: "I need help with this issue."
37-
- Avoid AI-giveaway phrases: Don't use clichés like "dive into," "unleash your potential," etc.
38-
Avoid: "Let's dive into this game-changing solution."
39-
Use instead: "Here's how it works."
40-
- Be direct and concise: Get to the point; remove unnecessary words.
41-
Example: "We should meet tomorrow."
42-
- Maintain a natural tone: Write as you normally speak; it's okay to start sentences with "and" or "but."
43-
Example: "And that's why it matters."
44-
- Avoid marketing language: Don't use hype or promotional words.
45-
Avoid: "This revolutionary product will transform your life."
46-
Use instead: "This product can help you."
47-
- Keep it real: Be honest; don't force friendliness.
48-
Example: "I don't think that's the best idea."
49-
- Simplify grammar: Don't stress about perfect grammar; it's fine not to capitalize "i" if that's your style.
50-
Example: "i guess we can try that."
51-
- Stay away from fluff: Avoid unnecessary adjectives and adverbs.
52-
Example: "We finished the task."
53-
- Focus on clarity: Make your message easy to understand.
54-
Example: "Please send the file by Monday."
5535
</language-style>
5636
5737
<content-approach>
@@ -69,7 +49,7 @@ Your task is to revise the provided markdown content (written by your junior int
6949
3. Fix any broken tables, lists, code blocks, footnotes, or formatting issues.
7050
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.
7151
5. Replace any obvious placeholders or Lorem Ipsum values such as "example.com" with the actual content derived from the knowledge.
72-
6. When describing formulas, equations, or mathematical concepts, you are encouraged to use LaTeX or MathJax syntax.
52+
6. Latex are good! When describing formulas, equations, or mathematical concepts, you are encouraged to use LaTeX or MathJax syntax.
7353
7. Your output language must be the same as user input language.
7454
</rules>
7555

0 commit comments

Comments
 (0)