Maths Prompt Studiofree maths platform

Home / Every Language, Every Learner / Build a Multilingual Maths Vocabulary Bridge

Every Language, Every LearnerText only

Build a Multilingual Maths Vocabulary Bridge

A classroom glossary linking one concept across languages, notation, a precise definition, one non-example, and a pronunciation-support note.

Works on any free AI  ·  Best tool:  Any AI chat (ChatGPT, Claude, Gemini)
ROLE: Act as a multilingual mathematics terminology editor.

CONTEXT: Create a vocabulary bridge for [TOPIC] across [LANGUAGE LIST] for [CLASS].

INPUTS — FILL EVERY PLACEHOLDER:
- [TOPIC]
- [LANGUAGE LIST]
- [CLASS]
- [APPROVED TERMS]
- [KEY NOTATION]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [KHAN_ACADEMY] Whitelist: https://www.khanacademy.org/search?page_search_query={ENCODED_KEYWORDS}. Use search only; never invent opaque Khan topic or exercise paths.
- [CODECOGS] Whitelist: https://latex.codecogs.com/png.image?{PERCENT_ENCODED_LATEX}. CodeCogs renders one equation image, not a document. Start permanent classroom PNGs with the encoded form of \dpi{150}, keep the URL short, and tell the teacher to download rather than hotlink it.

DO THIS:
1. Extract the smallest set of load-bearing concepts for the topic.
2. Lock [KEY NOTATION], placeholders, numbering, marks, and examples before translating terms.
3. Give one concise definition, one example, and one non-example for each concept.
4. List regional or textbook variants without inventing consensus.
5. Create an optional equation-only CodeCogs link when a symbol needs visual preservation.
6. Add a Khan search for teacher-selected supplementary explanations.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Build a vocabulary bridge for numerator and denominator around 3/4.
Expected result or check target: Each language term points to the same unchanged fraction and a consistent positional definition.
check this yourself
CHECK → https://latex.codecogs.com/png.image?%5Cfrac%7B3%7D%7B4%7D
(paste-fallback: \frac{3}{4})
Encoding note: The encoded backslash and braces decode to the exact fraction fallback.

OUTPUT FORMAT:
1. Term Inventory — concepts to include
2. Vocabulary Bridge — language columns and approved term
3. Meaning Check — definition, example, and non-example
4. Notation Lock — unchanged symbols
5. Review Queue — variants needing fluent-speaker approval

QUALITY AND TOOL GUARDRAILS:
- Preserve placeholders, notation, numbers, marks, and numbering exactly.
- Do not treat transliteration, translation, and definition as interchangeable.
- CodeCogs is equation-only and cannot render or validate a multilingual glossary.
- Khan links must be search URLs, not invented content slugs.
- For multilingual Overleaf use free login, XeLaTeX, fontspec, and a fallback font without availability claims.
- 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.

◀ Browse all 961 free prompts

Copied!