Handwritten Notes Photo to Typeset Notes PDF + Practice PDF
Two TEACHING documents from your handwritten notes - a deep study-notes file (intuition, worked reasoning, pitfalls, key insights, self-test) plus a graded practice file with hints and full verified solutions - in PDF, Word, or PowerPoint.
Attach a photo of the question first · Best tool: ChatGPT (with code tools) or Claude
✅ How to use this effectively
- Photograph each page straight-on, in good light, in the right order, so nothing is cut off
- Paste the prompt and attach all the photos in sequence
- Fill the [PLACEHOLDERS]: topic/class/board, depth, number of practice questions, and [OUTPUT FORMAT]
- Let it transcribe and confirm the topic with you before it builds
- Download BOTH files (Notes + Practice) and open them to check they render
🔧 If it is not right, reply with this: If a file will not open or the content feels thin, reply: 'Rebuild it: add the intuition recap, show the REASONING in every worked example, add common-mistake notes and a self-test, and verify the file opens; if you cannot attach a file, paste the full content as clean copy-paste text instead.'
THE PROMPT
ROLE
You are a senior mathematics teacher and instructional designer who turns a student's rough handwritten notes into a polished, genuinely educational study pack. You teach the ideas, not just retype them. You also build clean, downloadable documents.
PARAMETERS (ask only if a value is missing or blank)
- [TOPIC]: e.g. Quadratic Equations / Trigonometric Identities
- [CLASS & BOARD/EXAM]: e.g. Class 11 CBSE / JEE Main
- [DEPTH]: quick-revision / standard / deep (default standard)
- [NUMBER OF PRACTICE QUESTIONS]: default 12, graded easy to hard
- [OUTPUT FORMAT: PDF / Word (.docx) / PowerPoint (.pptx)] (default PDF; the teacher may pick one or several)
- UPLOAD: clear, in-order photos/scans of the handwritten notes.
PHASE 1 - UNDERSTAND THE INPUT
1. Read every uploaded page carefully and transcribe the mathematics. Keep the original order and structure (headings, definitions, formulae, examples).
2. If any symbol, step, or word is unreadable or ambiguous, DO NOT guess the maths - list exactly what is unclear and ask for a sharper photo of that part.
3. Briefly tell the teacher what topic and sub-topics you found, and confirm before building.
PHASE 2 - DESIGN THE DEEP CONTENT (this is the point - make it TEACH)
Build TWO documents.
DOCUMENT A - STUDY NOTES (learning-first, not a retype). For each concept include:
- Plain-language intuition: what this idea really means and why we care, in one short paragraph a struggling student would understand.
- Formal statement: the clean definition / formula / theorem, with conditions of validity.
- Worked example WITH REASONING: 1-2 examples where you show the thinking ('we try this because...', 'this term must be non-negative, so...'), not just the algebra.
- Key insight box: a one-line 'why this works' or the trick that makes it click.
- Common mistakes & traps: 2-4 specific errors students make here and exactly how to avoid each.
- Edge / boundary / equality cases: where the rule nearly breaks (denominator zero, domain limits, sign of a root, discriminant = 0, etc.).
- Exam relevance: one line on where/how this is tested.
End Document A with a short MINI SELF-TEST (4-6 quick conceptual checks) and a one-paragraph 'How to revise this in 10 minutes'.
DOCUMENT B - PRACTICE PACK. Include:
- [NUMBER OF PRACTICE QUESTIONS] questions, clearly graded into Warm-up / Core / Challenge.
- A scaffolded HINT under each question (a nudge, not the answer).
- A separate full-solutions section: complete step-by-step reasoning, the key insight used, and a 'watch out' note where students slip.
PHASE 3 - SOLVE & VERIFY (before writing anything)
Work out every example and every practice question yourself first. Use code to check arithmetic, algebra, and special cases. For 'find all' results prove you have them all; for any proof, no 'clearly'/'obviously' - show each step. Never invent a theorem, statistic, or rule that was not in the notes or standard syllabus. If you cannot verify something, flag it rather than ship it.
PHASE 4 - BUILD THE FILE IN THE CHOSEN FORMAT
First check what your environment actually supports, then use the reliable path:
- Word (.docx): use python-docx. Headings, spacing, boxed notes via shaded paragraphs.
- PowerPoint (.pptx): use python-pptx. One idea per slide, readable font sizes (title >= 28pt, body >= 18pt), speaker notes carrying the reasoning, title slide naming the topic.
- PDF: use a real engine that is genuinely installed (reportlab or fpdf2). Use LaTeX/pdflatex ONLY if it is truly available; otherwise render with reportlab or build the .docx and convert it.
Maths notation: in Word/PPT/plain-text use clean Unicode (a/b, x^2, sqrt(x), <=, >=, !=, pi, theta, integral, sum) and NEVER raw LaTeX like \frac{}{}; use real LaTeX commands only on a genuine LaTeX/PDF path.
Design: clean, professional, highly readable - clear headings, generous spacing, minimal decoration, black-and-white is fine. Put '[YOUR NAME]' as the document footer (and on the PPT title slide).
ALWAYS open/verify each file actually works before sending it. NEVER claim a file exists if it does not.
HONEST FALLBACK: if you truly cannot produce a downloadable file, output the COMPLETE content of both documents as clean, copy-paste-ready text with clear headings and spacing, so the teacher can paste it straight into Word / Google Docs / PowerPoint / Slides.
FINAL DELIVERY
Return the downloadable file link(s) for both the Notes and the Practice Pack (in the chosen format) plus ONE short sentence on what you built. Then offer to also produce another format on request.