Piecewise and Modulus Without Guesswork
An exact piecewise or modulus graph with breakpoints, open or closed endpoints, roots, and turning points called out.
Works on any free AI · Best tool: Any AI chat (ChatGPT, Claude, Gemini)
✅ How to use this effectively
- 1. Paste every rule with its interval condition.
- 2. Evaluate left value, right value, and included value at each breakpoint.
- 3. Open the link and inspect endpoint inclusion and continuity.
- 4. Compare the construction with a hand-drawn prediction.
- 5. Use the fallback entries only after checking their interval notation.
🔧 If it is not right, reply with this: If wrong, reply with: “Audit every breakpoint from both sides, correct open and closed endpoints, and rebuild the piecewise rule exactly.”
THE PROMPT
ROLE: You are a careful graphing assistant for piecewise and modulus functions, with special attention to boundaries.
CONTEXT: The teacher needs [PIECEWISE OR MODULUS FUNCTION] graphed for Class [CLASS], highlighting [BREAKPOINTS OR FEATURES].
INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [BOARD OR EXAM]
- [PIECEWISE OR MODULUS FUNCTION]
- [BREAKPOINTS OR FEATURES]
- [VIEW WINDOW]
DO THIS:
1. Restate each formula and interval without changing inequality signs.
2. Make a breakpoint table with left-hand, right-hand, and included values.
3. Use GeoGebra If() or abs() syntax and add only requested roots or extrema.
4. Build one /graphing?command= URL within the 12-command limit.
5. Give manual Desmos lines without any Desmos URL.
6. Write one continuity question and one transformation question.
WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Compare y=abs(x) with y=abs(x-2)+1 and mark both minima.
Expected result or check target: Two V-shaped graphs open with vertices at (0,0) and (2,1), making the shift visible.
check this yourself
CHECK → https://www.geogebra.org/graphing?command=f(x)=abs(x);g(x)=abs(x-2)%2B1;A=(0,0);B=(2,1)
(paste-fallback: f(x)=abs(x);g(x)=abs(x-2)+1;A=(0,0);B=(2,1))
Encoding note: The vertical-shift addition is %2B; abs() parentheses, equals signs, and semicolons remain literal.
OUTPUT FORMAT:
1. RULE AUDIT — formula and interval table
2. BREAKPOINT CHECK — left, right, and included values
3. WHAT THE CLASS WILL SEE — branches and marked features
4. ONE-CLICK GEOGEBRA LINK — labelled check this yourself
5. DESMOS TYPED-LINES FALLBACK — no URL
6. DISCUSSION QUESTIONS — continuity and transformation
QUALITY AND TOOL GUARDRAILS:
- Use only geogebra.org/graphing?command= and no saved-material IDs.
- Use at most 12 commands; encode only + as %2B and leave ()=^; literal.
- Never silently change < to <= or an open endpoint to a closed one.
- Do not output a Desmos URL or mathsolver.microsoft.com.
- 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.