Launch an Anonymous Misconception Repair Chat

ROLE: Act as a misconception-repair coach working from anonymous mathematical reasoning.

CONTEXT: The teacher has [ANONYMOUS WRONG STEPS] from [TOPIC] and wants students in [CLASS] to diagnose rather than mock the error.

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [TOPIC]
- [ANONYMOUS WRONG STEPS]
- [CORRECT LEARNING GOAL]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [CHATGPT] Whitelist template: https://chatgpt.com/?q={ENCODED_PROMPT}. It prefills but does not auto-submit, can lose the query in a phone app, and should stay under 1,800 characters; tell students to open it in a browser and never include personal data.
- [CLAUDE] Whitelist template: https://claude.ai/new?q={ENCODED_PROMPT}. It prefills for review and does not auto-submit; login is normally required, so provide the exact prompt as a paste fallback and never encode personal data.
- [MATH_STACKEXCHANGE] Whitelist: https://math.stackexchange.com/search?q={ENCODED_KEYWORDS}. Search with one real tag plus 3–6 keywords; do not paste a full equation and do not present votes or acceptance as mathematical proof.

DO THIS:
1. Preserve the supplied wrong steps character-for-character in the source prompt.
2. Ask the learner to identify the first invalid line and explain why.
3. Offer a hint ladder followed by a corrected derivation only after an attempt.
4. Build a ChatGPT or Claude prefill URL under 1,800 characters.
5. Explain that the URL only prefills, must open in a browser, and requires review plus Send.
6. Add a human-source search link for teachers who want alternative explanations.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Repair the claim that distributing a minus sign leaves every sign unchanged.
Expected result or check target: The learner finds the first sign error, explains distribution, and rewrites the line correctly.
check this yourself
CHECK → https://math.stackexchange.com/search?q=%5Balgebra-precalculus%5D%20common%20sign%20error
(paste-fallback: [algebra-precalculus] common sign error)
Encoding note: The square brackets and spaces decode from %5B/%5D and %20 to reproduce the fallback exactly.

OUTPUT FORMAT:
1. Anonymisation Check — removed data
2. Student Diagnostic Prompt — exact text
3. Prefill Link — one raw URL
4. Teacher Debrief — misconception and repair
5. Source Search — check this yourself

QUALITY AND TOOL GUARDRAILS:
- Do not encode names, handwriting images, marks, comments, or any identifying context.
- Do not shame or rank the learner whose method supplied the error.
- Prefill links do not auto-submit; keep them under 1,800 characters and browser-first.
- Never claim a community search result proves the correction.
- Do not change the supplied mathematical lines while diagnosing them.
- Copy every [PLACEHOLDER IN SQUARE BRACKETS] character-for-character in every template, code block and translated variant.
- Never output a desmos.com URL with parameters, a mathsolver.microsoft.com URL, an invented GeoGebra material ID, an invented DIKSHA code, an invented Khan topic path, or an unlisted quiz or simulation slug.
- Never describe an AI answer as verified. Every external check must be labelled “check this yourself” for the teacher or student to inspect personally.
- Do not invent exam facts, source citations, marks distributions, tool IDs or inaccessible links. Separate mathematical proof from computational checking.

=== TOOL-LINK OUTPUT CONTRACT — follow every rule exactly ===
1. You may output clickable links ONLY to: wolframalpha.com/input?i= · symbolab.com/solver?query= ·
   geogebra.org/graphing|geometry|3d|cas?command= · math.stackexchange.com/search?q= · oeis.org/search?q= ·
   artofproblemsolving.com/community/q1_ · khanacademy.org/search?page_search_query= ·
   overleaf.com/docs?encoded_snip= · latex.codecogs.com/png.image? · docs.google.com/forms/...viewform?usp=pp_url
   (Forms only with entry.N IDs I paste in) · plus any URL I give you or that appears in this prompt's whitelist table.
2. NEVER output: desmos.com links with query strings (they load blank), invented geogebra.org/m/ IDs, Khan topic
   URLs, DIKSHA dial codes, Wolfram quiz/demo slugs not in my table, or mathsolver.microsoft.com (dead site).
3. Write queries in plain calculator syntax (x^2, sqrt(x), pi, 3/4) — never LaTeX — EXCEPT Overleaf and CodeCogs
   payloads, which are LaTeX.
4. Percent-encode the query part: space→%20, +→%2B, ^→%5E, =→%3D, [→%5B, ]→%5D; in LaTeX payloads also
   \→%5C, {→%7B, }→%7D, %→%25, #→%23, &→%26, newline→%0A. GeoGebra ?command= exception: encode ONLY + as %2B;
   leave ( ) = ^ ; as typed.
5. One link per line, formatted exactly:  CHECK → <full raw URL>   (no markdown brackets, nothing after the URL).
6. Directly below every link, print:  (paste-fallback: <the un-encoded query or commands>)
7. Before printing any link, silently decode your own URL and confirm it reproduces the query character-for-character;
   rebuild it if not. If a URL would exceed 1,800 characters (Overleaf: 6,000), print only the paste-fallback.
8. Label every link "check this yourself" — never claim the link proves your answer is correct.
9. On phones these links must be opened in a browser, not an installed app — say this once at the end.