Re-explain Clearly
Restate the target content so the user can understand it without weakening its meaning. This is a language and clarity preference, not a new research or tool capability.
Establish the Target
- Identify the exact explanation, passage, term, or supplied content the user wants clarified.
- If the target is missing or ambiguous, ask one concise question to obtain it. Do not invent a source or intended meaning.
- Use an output language the user explicitly requests. Otherwise continue in the language the user is currently using. Preserve exact code, API names, quoted text, and other identifiers when needed.
- Do not require or silently infer an age, profession, or knowledge level. Use an audience or persona the user supplies when it helps; otherwise use neutral, respectful language.
Re-explain
- State the central meaning directly.
- Use short sentences with one main idea each and concrete verbs.
- Keep necessary technical terms, and explain each one immediately in plain language.
- Add only the context needed to understand the target.
- Use an example or analogy only when it materially helps. State its limit when the limit matters.
- Match the depth and length to the source and the user's request. Be concise by default, then add layers when the topic requires them.
Preserve the Source Contract
Keep every material fact, number, uncertainty, condition, exception, causal direction, and distinction from the source. Do not turn a possibility into a certainty, an estimate into an exact value, or a conditional rule into a universal one.
Never trade correctness for simplicity. If the source itself is unclear or incomplete, identify that uncertainty instead of filling the gap.
Avoid
- patronizing language or claims that the user should already understand;
- fixed age-based or job-based stereotypes;
- forced analogies, decorative examples, or unnecessary background;
- English-only simplified-language rules when the user is speaking another language; and
- silently changing the task into drafting, translation, summarization, research, or implementation.
1---2name: re-explain-clearly3description: Re-explains an existing explanation, passage, term, or other supplied content in clearer language when the user says they do not understand, asks what it means, or requests a simpler explanation. Use for equivalent requests in any language; do not use for drafting or revising substantive documents, translation-only or summary-only requests, or original tutorials.4---56# Re-explain Clearly78Restate the target content so the user can understand it without weakening its meaning. This is a language and clarity preference, not a new research or tool capability.910## Establish the Target1112- Identify the exact explanation, passage, term, or supplied content the user wants clarified.13- If the target is missing or ambiguous, ask one concise question to obtain it. Do not invent a source or intended meaning.14- Use an output language the user explicitly requests. Otherwise continue in the language the user is currently using. Preserve exact code, API names, quoted text, and other identifiers when needed.15- Do not require or silently infer an age, profession, or knowledge level. Use an audience or persona the user supplies when it helps; otherwise use neutral, respectful language.1617## Re-explain18191. State the central meaning directly.202. Use short sentences with one main idea each and concrete verbs.213. Keep necessary technical terms, and explain each one immediately in plain language.224. Add only the context needed to understand the target.235. Use an example or analogy only when it materially helps. State its limit when the limit matters.246. Match the depth and length to the source and the user's request. Be concise by default, then add layers when the topic requires them.2526## Preserve the Source Contract2728Keep every material fact, number, uncertainty, condition, exception, causal direction, and distinction from the source. Do not turn a possibility into a certainty, an estimate into an exact value, or a conditional rule into a universal one.2930Never trade correctness for simplicity. If the source itself is unclear or incomplete, identify that uncertainty instead of filling the gap.3132## Avoid3334- patronizing language or claims that the user should already understand;35- fixed age-based or job-based stereotypes;36- forced analogies, decorative examples, or unnecessary background;37- English-only simplified-language rules when the user is speaking another language; and38- silently changing the task into drafting, translation, summarization, research, or implementation.
ether-moon