Homework Link Pack With Worksheet
A concise worksheet paired with browser-ready GeoGebra explorations, expected observations, and a printable no-device alternative.
Works on any free AI · Best tool: Any AI chat (ChatGPT, Claude, Gemini)
✅ How to use this effectively
- 1. State the topic, class, question count, and expected phone or computer access.
- 2. Review the worksheet questions before sharing anything.
- 3. Open each link in a browser and compare it with the expected view.
- 4. Share the link pack with the instruction to record observations, not screenshots alone.
- 5. Offer the printable fallback to students without reliable internet.
🔧 If it is not right, reply with this: If wrong, reply with: “Make every worksheet question require an observation from its matching link, and add an equivalent no-device question.”
THE PROMPT
ROLE: You are a homework designer who pairs purposeful interactive links with written mathematical evidence and equal-access alternatives.
CONTEXT: The homework covers [TOPIC] for Class [CLASS], with [QUESTION COUNT] questions and [DEVICE ACCESS LEVEL] access.
INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [BOARD OR EXAM]
- [TOPIC]
- [QUESTION COUNT]
- [DEVICE ACCESS LEVEL]
- [DIFFICULTY MIX]
DO THIS:
1. Create questions that require prediction, manipulation, recorded values, and explanation rather than passive viewing.
2. Attach only the minimum number of GeoGebra links needed and state the expected starting view for each.
3. Keep each GeoGebra construction within 12 commands and include raw-command fallbacks.
4. Give exact browser-opening instructions and state that installed apps may drop query parameters.
5. Provide a parallel printable question for every link-dependent task.
6. End with a short answer key containing expected observations and reasoning.
WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Create a four-question homework exploration comparing y=x^2 with y=(x-2)^2+1.
Expected result or check target: Students predict the shift, open the two labelled parabolas, record vertices, explain the transformation, and can complete an equivalent coordinate-table task offline.
check this yourself
CHECK → https://www.geogebra.org/graphing?command=f(x)=x^2;g(x)=f(x-2)%2B1;Extremum(f);Extremum(g)
(paste-fallback: f(x)=x^2;g(x)=f(x-2)+1;Extremum(f);Extremum(g))
Encoding note: The vertical-shift plus sign is %2B; the rest of the GeoGebra command punctuation remains literal.
OUTPUT FORMAT:
1. STUDENT INSTRUCTIONS — browser and recording expectations
2. WORKSHEET — numbered prediction, exploration, and explanation items
3. LINK PACK — expected view, check link, and paste fallback
4. PRINTABLE ALTERNATIVE — equivalent no-device tasks
5. ANSWER KEY — expected values and observations
6. TEACHER CHECKLIST — links tested and access plan
QUALITY AND TOOL GUARDRAILS:
- Use only GeoGebra /graphing, /geometry, /3d, or /cas ?command= URLs and no invented /m/ IDs.
- Use at most 12 commands per link; encode only + as %2B and leave ()=^; literal.
- Never output a Desmos URL; manual typed lines may be offered as an optional fallback.
- Never link mathsolver.microsoft.com, and never make completion depend on a paid account.
- 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.