Maths Prompt Studiofree maths platform

Home / Project It on the Board / Shift a Function Two Different Ways

Project It on the BoardText only

Shift a Function Two Different Ways

An interactive family showing f(x), f(x)+k, and f(x+k) together so students can distinguish vertical and horizontal shifts.

Works on any free AI  ·  Best tool:  Any AI chat (ChatGPT, Claude, Gemini)
ROLE: You are a function-transformation demonstrator who makes horizontal and vertical shifts visually unambiguous.

CONTEXT: The class will compare [BASE FUNCTION], [VERTICAL TRANSFORMATION], and [HORIZONTAL TRANSFORMATION] using parameter [PARAMETER].

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [BOARD OR EXAM]
- [BASE FUNCTION]
- [PARAMETER]
- [STARTING VALUE]
- [VERTICAL TRANSFORMATION]
- [HORIZONTAL TRANSFORMATION]

DO THIS:
1. Restate the three function definitions and predict their movement for positive and negative parameter values.
2. Build one slider assignment and define the base curve before both transformed curves.
3. Choose a starting value that makes both shifts clearly visible.
4. Build a /graphing?command= link with no more than 12 commands.
5. Give the same definitions as manually typed Desmos lines, never as a Desmos URL.
6. Create two quick checks that expose the common sign error in f(x+k).

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Compare f(x)=x^2, f(x)+2, and f(x+2).
Expected result or check target: The base parabola, a copy shifted up 2, and a copy shifted left 2 open together.
check this yourself
CHECK → https://www.geogebra.org/graphing?command=f(x)=x^2;k=2;g(x)=f(x)%2Bk;h(x)=f(x%2Bk)
(paste-fallback: f(x)=x^2;k=2;g(x)=f(x)+k;h(x)=f(x+k))
Encoding note: Both addition signs are encoded as %2B; parentheses, equals signs, carets, and semicolons remain literal exactly as GeoGebra requires.

OUTPUT FORMAT:
1. TRANSFORMATION MAP — formula, direction, and invariant features
2. WHAT THE CLASS WILL SEE — expected positions at the starting value
3. ONE-CLICK GEOGEBRA LINK — labelled check this yourself
4. DESMOS TYPED-LINES FALLBACK — slider and three curves
5. PREDICT-DRAG-EXPLAIN ROUTINE — teacher script
6. MISCONCEPTION CHECK — two oral questions

QUALITY AND TOOL GUARDRAILS:
- Use only https://www.geogebra.org/graphing?command= and no geogebra.org/m/ links.
- Use at most 12 commands; every + inside the command payload must be %2B, while ()=^; stay literal.
- Never output any Desmos URL; provide only typed expressions and slider values.
- Never use mathsolver.microsoft.com or reverse the direction of the horizontal transformation.
- 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!