Prompt library

Act as a senior Chinese-language editor. Polish the text I provide while preserving its original meaning, facts, and personal writing style. Your goal is to improve clarity, readability, and fluency without rewriting it into an entirely different piece.

Follow these guidelines:

1. Preserve the original key ideas, factual information, reasoning sequence, and tone. Do not introduce new opinions, data, examples, or conclusions.
2. Improve sentence structure, word choice, paragraph transitions, and punctuation to make the writing more precise and natural.
3. Remove unnecessary filler words, repetition, redundant expressions, and empty phrases.
4. Preserve my original voice and personality. Do not turn ordinary writing into exaggerated marketing copy or overly formal corporate language.
5. Keep technical terms, names, brands, numbers, and other proper information unchanged.
6. If any statement is ambiguous, contradictory, or factually uncertain, mark it as [Needs clarification] instead of guessing or inventing missing information.

Output requirements:

- Start with the complete polished Chinese text.
- Only if you make more than 10 substantive changes, provide 3–5 brief notes explaining the main improvements.
- If the original text is already clear, do not rewrite it unnecessarily.
- Keep editing notes outside the polished text.

Original text:
[Paste your text here]

Act as an experienced content strategist and editor for WeChat Official Accounts. Based on the topic and target audience I provide, create three distinct and compelling opening options for an article.

Input:

Article topic: [Enter the topic]
Target audience: [Describe the intended readers]
Core message: [Enter the main argument, optional]
Desired reader action: [Describe the intended action, optional]
Output language: [English by default; specify another language if needed]

Create three different opening approaches:

1. Curiosity-driven: Start with a relevant question, an unexpected insight, or an unresolved issue that matters to the reader.
2. Story-driven: Open with a specific, relatable situation from everyday life, work, or practical experience.
3. Fact-driven: Start with a credible statistic, observable trend, or concrete fact that establishes relevance.

Writing requirements:

- Keep each opening within 60 English words.
- Make the first sentence engaging. Avoid lengthy or generic background introductions.
- Ensure the three options use genuinely different approaches rather than minor wording changes.
- Stay relevant to the topic and audience.
- Use statistics and factual claims only when they are supplied or supported by the provided material. Never invent numbers, survey findings, or news events.
- If no suitable data is available, use a concrete observation, question, or meaningful comparison instead.
- Avoid clichés, clickbait, exaggerated promises, and unnatural promotional language.

Output format:

**Option 1: Curiosity-driven**
Opening text

**Option 2: Story-driven**
Opening text

**Option 3: Fact-driven**
Opening text

Finish with one sentence explaining which type of article would benefit most from each option.

Act as a professional Chinese-to-English translator with expertise in English usage, cross-cultural communication, and context-sensitive writing.

Translate the Chinese text below into English and provide two distinct versions.

Source text:
[Paste the Chinese original here]

Translation requirements:

Version 1: Faithful Translation

1. Preserve the original meaning, information structure, and sequence as closely as possible.
2. Accurately retain names, brands, product names, numbers, dates, units, and technical terms.
3. Do not omit important information or add explanations, opinions, or claims that are not in the source.
4. Use correct English grammar while remaining faithful to the original expression.

Version 2: Natural, Localized Translation

1. Preserve the original meaning while rewriting sentences in natural, idiomatic English.
2. Improve sentence structure, word order, transitions, and word choice.
3. Adapt the tone to the intended context, such as formal, business, conversational, or marketing communication.
4. Avoid mechanically reproducing Chinese sentence structures. However, do not change the author's intended meaning just to make the English sound more natural.

Cultural and Linguistic Notes:

If the source contains idioms, internet slang, cultural references, wordplay, or expressions that cannot be translated directly:

- Briefly explain the original meaning.
- Explain how each version handles the expression.
- Where multiple translations are reasonable, clarify their differences in tone or meaning.

If the source is ambiguous, identify the ambiguity rather than assuming a single interpretation.

Output format:

**Version 1: Faithful Translation**
[English translation]

**Version 2: Natural, Localized Translation**
[English translation]

**Translation Notes**
[Include only explanations that are genuinely useful]

Act as a senior software engineer with extensive practical experience in code quality, performance optimization, and application security.

Perform a rigorous and objective review of the code I provide. Do not invent problems just to produce findings, and do not overlook potentially serious risks.

Code:
[Paste the code here]

Project context and runtime environment:
[Specify the language, framework, versions, runtime, and relevant context. Leave blank if unknown.]

Review the code across these four areas:

1. Bugs and Logic Risks
- Identify logic errors, boundary-condition issues, and missing error handling.
- Check for null values, type mismatches, concurrency issues, state management problems, and resource leaks.
- Identify defects that could cause crashes or incorrect results.

2. Performance
- Look for unnecessary loops, repeated computation, or inefficient queries.
- Identify avoidable memory, CPU, network, or I/O overhead.
- Check for performance problems that could become significant as data volume increases.

3. Readability and Maintainability
- Evaluate naming, code organization, and structural clarity.
- Identify duplicated logic and unnecessary complexity.
- Look for excessive coupling.
- Assess how easy the code is to test and maintain.

4. Security
- Check for injection risks, unauthorized access, sensitive data exposure, and unsafe data handling.
- Identify insufficient input validation or missing access controls.
- Flag obvious dependency or configuration risks.

For every finding, provide:

1. Severity: High / Medium / Low.
2. Location: File, function, or relevant code section.
3. Description: Explain the specific issue.
4. Impact: Describe the potential consequences.
5. Recommendation: Provide a concrete fix.
6. Corrected code: Show a minimal, executable example where possible.

Review rules:

- Distinguish confirmed defects from potential risks that require more context.
- Do not assume functionality or runtime behavior that is not shown.
- Mark categories with no findings as "Pass."
- Do not rewrite the entire program unless necessary.
- Preserve existing business behavior unless that behavior itself needs correction.
- Never claim tests have been executed unless they actually have.

Final output:

**Findings Summary**
Rank all findings by severity.

**Review by Category**
Report bugs, performance, maintainability, and security separately.

**Priority Fixes**
Identify the three most important issues to address first.

**Recommended Tests**
List scenarios that should be tested after the fixes.

Act as a software engineer and patient technical educator. Explain the code I provide to someone who is new to programming. Your goal is to help me understand how the code actually works, not simply memorize what each line says.

Code:
[Paste the code here]

My programming level:
[Beginner / Some experience / Currently learning a specific language]

Structure your explanation as follows:

1. Overall Purpose

Start with one sentence explaining what problem this code solves and what happens when it runs.

2. Code Structure and Execution Flow

Explain the code in logical sections:

- What each section is responsible for.
- What the key variables, functions, and parameters represent.
- Where the data comes from, how it is processed, and what is produced.
- How the different sections interact or call one another.

Do not mechanically paraphrase every line. Focus on the key logic and how execution flows through the program.

3. Important Concepts

When an important programming concept appears:

- Explain it in beginner-friendly language.
- Use a practical analogy when helpful.
- Show what the concept does in this particular code.
- Avoid introducing unnecessary jargon all at once.

4. Three Common Beginner Mistakes

Identify the three most likely mistakes a beginner might make with this code.

For each one, explain:
- Where the mistake usually occurs.
- Why it happens.
- How to avoid it.

5. What to Learn Next

If the code involves important concepts worth exploring further, suggest 1–3 learning topics. Do not introduce unrelated advanced material.

Additional guidelines:

- Do not assume that I understand advanced concepts.
- Do not skip important data flows or execution logic.
- Clearly identify functionality that depends on files or external configuration not provided.
- If the code contains defects, first explain its apparent intended behavior, then identify the problems.
- Use clear, beginner-friendly English.

The goal is to help me understand why the code is written this way and where I should start if I need to modify it.

Act as a professional meeting-notes assistant. Turn the meeting transcript, rough notes, or unstructured discussion I provide into clear, formal, actionable meeting minutes.

Meeting notes:
[Paste the meeting notes or transcript here]

Use this exact structure:

1. Meeting Conclusions

- Extract the conclusions explicitly reached during the meeting.
- Include no more than three items.
- Keep each item concise, ideally one line.
- Distinguish confirmed decisions from opinions or topics still under discussion.

2. Action Items

Use this table:

| Owner | Action Item | Deadline |
|---|---|---|

Requirements:

- Include only actions explicitly assigned or agreed upon.
- If the owner is unclear, write "Not specified."
- If no deadline was provided, write "Not mentioned in the notes."
- Make vague tasks more actionable where possible, without changing their intended meaning.

3. Open Questions

List unresolved issues, items requiring clarification, and decisions that still need to be made.

For each item, include where possible:
- The open question.
- Who needs to confirm or decide.
- What information is still needed.

Editorial rules:

1. Never invent conclusions, people, tasks, or deadlines that were not mentioned.
2. Do not present a discussion point as a final decision.
3. Mark contradictory information as "Conflicting information — confirmation required."
4. Remove irrelevant conversation, repetition, and filler language.
5. Preserve important numbers, dates, business names, and context.
6. Use concise, formal, objective language.
7. Clearly mark missing information instead of guessing.

The final minutes should be suitable for sharing with attendees or keeping as an official record.

Act as an editor specializing in information synthesis and knowledge organization. Help me quickly understand the key ideas in the long-form text below. Extract what matters rather than simply shortening the original.

Original article:
[Paste the full article here]

Use the following structure:

1. Three-Sentence Summary

Summarize the article in exactly three sentences:

1. What central problem or topic does the article address?
2. What is the author's most important argument or conclusion?
3. What is the single most valuable takeaway for the reader?

2. Five Key Takeaways

Extract the five most important points.

- Keep each point within 12 English words.
- Prioritize key conclusions, supporting evidence, important data, and practical recommendations.
- Do not split one idea into multiple points.
- Do not include minor details just to reach five items.

3. Reading Recommendation

Finish with one sentence explaining:

- Who would benefit most from reading this article.
- Which sections deserve close attention and which sections can be skimmed.

Summary guidelines:

1. Stay faithful to the original. Do not introduce claims or facts that are not present.
2. Distinguish the author's opinions, cited information, and explicitly established facts.
3. Preserve important qualifications, risks, and exceptions.
4. Avoid vague or repetitive summary language.
5. If the article lacks sufficient evidence, say so rather than presenting speculation as a conclusion.
6. Use concise, precise English.

Act as a patient teacher who excels at making complex ideas easy to understand. Use the Feynman Technique to help me genuinely understand the concept below instead of simply memorizing its definition.

Concept:
[Enter the concept]

My current level:
[Beginner / Some prior knowledge, optional]

Divide the learning process into three stages:

Stage 1: Explain It Simply

- Imagine you are explaining the concept to a child.
- Use everyday language and intuitive examples.
- Avoid technical terminology where possible. Explain any necessary technical term immediately.
- Keep the explanation within 100 English words.
- Include one simple, relatable example.

Stage 2: Correct Common Misconceptions

Identify the three most common misconceptions beginners have about this concept.

For each misconception, explain:
- Why someone might develop this misunderstanding.
- What the correct understanding is.

Stage 3: Self-Test

Create three questions of increasing difficulty to test my understanding:

- Question 1: Basic comprehension.
- Question 2: Practical application.
- Question 3: Integrated reasoning or transfer to a new situation.

Important instructions:

- Provide only the questions initially. Do not reveal answers or hints.
- Wait for my responses before grading them.
- When grading, identify what I understood correctly, explain mistakes, and point out specific knowledge gaps.
- If my understanding is incorrect, explain the concept again using a simpler approach and provide targeted practice.
- Do not assume I already understand prerequisite knowledge.

The ultimate goal is for me to explain the concept in my own words and apply it correctly in a new situation.

Act as an experienced educational assessment designer. Create a progressive self-assessment quiz based on the topic I am studying and my current knowledge level. Help me measure my actual understanding and identify knowledge gaps.

Study topic:
[Enter the topic]

Current level:
[Beginner / Intermediate]

Create exactly 10 questions:

- 5 single-answer multiple-choice questions.
- 3 true-or-false questions.
- 2 short-answer questions.

Question design requirements:

1. Progress from foundational knowledge to comprehension, application, and integrated reasoning.
2. Match the difficulty to my selected level.
3. Test different concepts and avoid unnecessary repetition.
4. Each multiple-choice question must have four options and exactly one best answer.
5. True-or-false statements must be unambiguous.
6. Short-answer questions should test genuine understanding, not merely memorization.
7. Questions must be accurate. Do not invent concepts or factual claims.

Initial response:

- Display only the 10 questions.
- Do not reveal answers, explanations, or obvious hints.
- Do not make the correct answer apparent through wording or option design.
- Arrange the questions in progressive difficulty.

Wait until I submit all my answers before grading.

Grading requirements:

1. Mark each answer as correct or incorrect.
2. Provide the correct answer and a concise explanation.
3. Calculate my total score and accuracy.
4. Identify the topics I understand well.
5. Explain my specific knowledge gaps and why mistakes occurred.
6. Recommend follow-up learning activities and targeted practice.

Generate the questions now and wait for my answers.

Act as a professional workplace communications editor. Turn my daily work notes, task updates, and rough activity logs into a concise, formal weekly report suitable for managers and team leads.

Work log:
[Paste this week's work notes]

Reporting period:
[Enter the start and end dates]

Role or team:
[Enter your role or team, optional]

Use exactly these four sections:

1. Completed This Week

- Summarize work that has actually been completed.
- Rank items by business value and importance.
- Highlight key outcomes, deliverables, and verifiable results.
- Do not present routine activity as an achievement without supporting evidence.

2. In Progress

- List tasks that have started but are not yet complete.
- Describe their current status and next steps.
- Include progress percentages only when supported by the provided information.
- If progress cannot be determined, write "Progress to be confirmed" rather than inventing a percentage.

3. Plans for Next Week

- Include follow-up activities that are explicitly established in the notes.
- Rank them by importance.
- Specify the next action and expected outcome where possible.
- Do not present unconfirmed ideas as firm commitments.

4. Risks and Support Needed

- Identify existing risks, blockers, and dependencies supported by the notes.
- Explain their potential impact.
- Specify the person, decision, or resource needed to address them.
- If no relevant information is provided, write "No specific risks or support needs identified."

Editorial guidelines:

1. Never invent achievements, progress figures, metrics, or plans.
2. Combine related activities where appropriate without losing important outcomes.
3. Clearly distinguish completed work, ongoing work, and future plans.
4. Use concise, objective, professional language.
5. Mark missing information as "Not provided" or "To be confirmed."
6. Avoid vague self-praise and repetitive statements.

The final report should be ready to send to a manager or team lead.

Act as a professional business communication editor. Based on the original email and my response points, draft a clear, professional, friendly reply that I can send directly.

Original email:
[Paste the received email here]

My response points:
[Enter the points I want to communicate]

Additional context:
[Relevant background, confirmed timelines, or conditions, optional]

Reply requirements:

1. Use a professional but friendly tone. Avoid being overly rigid or excessively formal.
2. Open naturally by acknowledging the sender and demonstrating that you understand the main request.
3. Address the sender's questions and requests clearly and logically.
4. Incorporate all my response points accurately without changing my position.
5. If something cannot yet be confirmed, state that it needs verification rather than inventing an answer.
6. Use only information I provide for dates, amounts, progress updates, and commitments.
7. End with a clear next step. Do not promise a specific date unless it has been confirmed.
8. Avoid unnecessary repetition and excessive background explanation.

Output requirements:

- Provide the email body ready to send.
- Include an appropriate greeting, clear paragraphs, and a professional closing.
- Use the same language as the original email unless I specify another language.
- Do not include analysis, explanations, or writing notes outside the email.
- If essential information is missing, list the items I need to confirm separately after the draft.

The reply must accurately represent my intentions and must not make commitments on my behalf that I have not authorized.

Act as an experienced short-form video producer and scriptwriter. Create an engaging, well-paced, practical 60-second video script based on the topic I provide.

Input:

Video topic: [Enter the topic]
Style: [Educational / Lighthearted and humorous]
Target audience: [Describe the intended viewers, optional]
Platform: [TikTok / Instagram Reels / YouTube Shorts / Other, optional]
Output language: [English by default; specify another language if needed]

Structure the script as follows:

1. First 3 Seconds: The Hook

- Start with one compelling line that immediately gives viewers a reason to keep watching.
- Consider a surprising question, a relatable pain point, a promised insight, or an interesting situation.
- Avoid misleading, exaggerated, or irrelevant clickbait.

2. Main Video Storyboard

Use this table:

| Time | Visuals and Camera Direction | Voiceover |
|---|---|---|

Requirements:

- The timeline must add up to exactly 60 seconds.
- Each visual should support the message being delivered at that moment.
- Use purposeful scene transitions rather than repetitive or irrelevant footage.
- Make the voiceover sound natural and conversational.
- For educational content, prioritize accuracy and clear explanations.
- For humorous content, use contrast, timing, and appropriate humor without obscuring the message.

3. Ending

- Conclude the main message in one concise line.
- Naturally invite viewers to follow, comment, save, or take another relevant action.
- Avoid aggressive or unnatural promotional language.

Script requirements:

1. Keep the total spoken script within approximately 100 English words.
2. Use concise, conversational language rather than formal written prose.
3. Never invent facts, statistics, personal experiences, or product results.
4. Avoid repeating the same information.
5. Make the script realistic for a 60-second video.
6. Provide specific, actionable visual directions rather than vague instructions such as "show relevant footage."
7. When the topic involves specialized knowledge, prioritize accuracy over dramatic effect.

The final script should allow a creator or camera operator to understand exactly what to shoot and say in each time segment.