WTF
Use this skill when the immediately previous response from an LLM was unclear, too dense, or difficult to follow.
Procedure
- Read the immediately previous LLM response.
- If the response uses domain terms, first inspect repository guidance for its declared glossary authority and bounded-context scope. If none is declared, check common locations such as
CONTEXT.md, GLOSSARY.md, UBIQUITOUS_LANGUAGE.md, and *.glossary.yml without creating a new convention.
- Use only the glossary that owns the relevant context to select canonical terms and meanings.
- Re-explain the previous response with a clearer structure and simpler wording.
- Preserve its meaning and all relevant technical details.
- Keep the explanation about the previous response.
- Do not perform a new task.
- Do not introduce information from the terminology files that the previous response did not contain.
Writing Rules
Write in a style inspired by ASD-STE100 Simplified Technical English.
- Use active voice.
- Use plain UK English.
- Write for a reading level between Key Stage 4 and Further Education.
- Use the same term for the same concept throughout the explanation.
- Use precise and technically accurate wording.
- Use short sentences where possible.
- Use the imperative form for direct instructions.
- Put one main action in each sentence.
- Define an uncommon abbreviation or specialist term when it first appears.
- Preserve technical details, including constraints, exceptions, conditions, dependencies, examples, values, units, and warnings.
- Prioritise technical accuracy and unambiguous meaning when clarity and brevity conflict.
Clarity Controls
- Put each prerequisite, condition, warning, or limitation before the action to which it applies.
- Use the exact nouns from the previous response for files, commands, components, and values.
- Replace vague pronouns with the specific subject.
- Remove idioms, unnecessary synonyms, ambiguous references, and complex noun clusters.
- Do not add information that is not present in the previous response.
- State uncertainty when the previous response was uncertain.
Completion Criterion
The new explanation is complete when it re-explains the immediately previous LLM response, preserves its meaning and relevant technical details, and uses clearer plain language without starting new work.
Attribution
Adapted from Adam Bulmer's MIT-licensed Mintuz wtf skill at pinned revision
e436942ef328e692567300dba51424c68850ab12. See
references/source-notes.md and LICENSE.
1---2name: wtf3description: Re-explain the immediately previous LLM response when it did not land, using plain, precise UK English.4---56# WTF78Use this skill when the immediately previous response from an LLM was unclear, too dense, or difficult to follow.910## Procedure11121. Read the immediately previous LLM response.132. If the response uses domain terms, first inspect repository guidance for its declared glossary authority and bounded-context scope. If none is declared, check common locations such as `CONTEXT.md`, `GLOSSARY.md`, `UBIQUITOUS_LANGUAGE.md`, and `*.glossary.yml` without creating a new convention.143. Use only the glossary that owns the relevant context to select canonical terms and meanings.154. Re-explain the previous response with a clearer structure and simpler wording.165. Preserve its meaning and all relevant technical details.176. Keep the explanation about the previous response.187. Do not perform a new task.198. Do not introduce information from the terminology files that the previous response did not contain.2021## Writing Rules2223Write in a style inspired by ASD-STE100 Simplified Technical English.2425- Use active voice.26- Use plain UK English.27- Write for a reading level between Key Stage 4 and Further Education.28- Use the same term for the same concept throughout the explanation.29- Use precise and technically accurate wording.30- Use short sentences where possible.31- Use the imperative form for direct instructions.32- Put one main action in each sentence.33- Define an uncommon abbreviation or specialist term when it first appears.34- Preserve technical details, including constraints, exceptions, conditions, dependencies, examples, values, units, and warnings.35- Prioritise technical accuracy and unambiguous meaning when clarity and brevity conflict.3637## Clarity Controls3839- Put each prerequisite, condition, warning, or limitation before the action to which it applies.40- Use the exact nouns from the previous response for files, commands, components, and values.41- Replace vague pronouns with the specific subject.42- Remove idioms, unnecessary synonyms, ambiguous references, and complex noun clusters.43- Do not add information that is not present in the previous response.44- State uncertainty when the previous response was uncertain.4546## Completion Criterion4748The new explanation is complete when it re-explains the immediately previous LLM response, preserves its meaning and relevant technical details, and uses clearer plain language without starting new work.4950## Attribution5152Adapted from Adam Bulmer's MIT-licensed Mintuz `wtf` skill at pinned revision53`e436942ef328e692567300dba51424c68850ab12`. See54`references/source-notes.md` and `LICENSE`.