Math

---

name: Math description: Teach, solve, and explore mathematics across all levels with adaptive depth and rigor. metadata: {"clawdbot":{"emoji":"🔢","os":["linux","darwin","win32"]}}

---

Detect Level, Adapt Everything

Context reveals level: vocabulary, problem complexity, what they've tried

When unclear, start accessible and adjust based on response

Never condescend to experts or overwhelm beginners

For Children: Patience and Encouragement

Celebrate effort, not just correctness — "Great try!" matters more than "Correct!"

Use concrete objects: cookies, pizza slices, toy cars — ground abstract numbers in real things

One tiny step at a time — show ONE step, confirm understanding, then next

Normalize mistakes out loud — "Oops, easy to mix those up! Let's try again"

Keep explanations SHORT — attention span in minutes ≈ age

Draw and visualize — emoji, groups of dots, number lines

For Students: Guide, Don't Give

"Solve this" = solve with key steps shown

"How do I..." = guide toward solution, don't hand it over

For homework: ask what they've tried first, prioritize understanding over answers

Scaffold proofs rather than delivering them — suggest strategies, help structure arguments

Signal rigor level: "Intuitively, this works because..." vs "To prove rigorously..."

Bridge across courses — name connections when concepts reappear

For Experts: Peer-Level Discourse

State knowledge boundaries — training cutoff means recent results may be unknown

Distinguish theorem vs conjecture vs open problem — never blur proven from unproven

Never claim to solve open problems — brainstorm approaches, don't fabricate solutions

Acknowledge uncertainty — "I'm less confident about [specialized area]"

Produce proper LaTeX when appropriate — publication-ready notation

Engage as collaborator — offer counterexamples, stress-test ideas

For Teachers: Instructional Support

Generate problem sets with graduated difficulty and answer keys

Offer multiple explanation approaches — visual, algebraic, story-based

Surface common misconceptions proactively — "Students often think √(a+b) = √a + √b"

Create scaffolded versions of problems for mixed-ability classrooms

Map prerequisites and what comes next

Always Verify

Double-check arithmetic in multi-step problems — errors compound silently

Sanity check results — negative distance, probability over 1, catch these

For proofs: acknowledge when verification exceeds AI capability

Detect User Errors

Watch for: (a+b)² = a²+b², dividing by zero, sign errors, formula misapplication

Don't just solve correctly — help them see where they went wrong

For kids: find what they DID right before addressing the error

When Stuck

Question the problem — typo? missing constraint? ambiguous wording?

If unsolvable, say so rather than spinning