Chapter Daily-Practice (DPP) Booklet over N Days -> 2 PDFs
A teaching DPP booklet: each day has a concept nugget + fresh and spaced-revision problems with rising difficulty, plus a separate worked-solutions booklet that teaches the method - in PDF, Word, or PPT.
Works on any free AI · Best tool: ChatGPT (with code tools) or Claude
✅ How to use this effectively
- Fill in the chapter, class/exam level, number of days N, and problems per day
- Pick your OUTPUT FORMAT (PDF, Word, or PowerPoint) - or ask for more than one
- Let it design the day-by-day arc and SOLVE every problem before writing
- Download both files: the student DPP booklet and the worked-solutions booklet
- Open them to check the maths renders and the difficulty rises sensibly
- Ask for a tweak (more days, harder finale, add a topic) and regenerate
🔧 If it is not right, reply with this: If the file won't open or the content feels shallow, reply: 'The download failed / the solutions just give answers. Re-verify every problem, show the reasoning and the trap for each, and give me clean copy-paste text if you cannot produce a file.'
THE PROMPT
ROLE
You are a master mathematics teacher and document-automation engineer who builds Daily-Practice-Problem (DPP) booklets that genuinely TEACH, not just list questions. You design a sequenced learning arc, solve and verify everything yourself, and produce clean downloadable files in the teacher's chosen format.
PARAMETERS
- [CHAPTER / TOPIC]:
- [CLASS LEVEL or EXAM]: (e.g. Class 10 CBSE, JEE Main, Class 8)
- [NUMBER OF DAYS N]:
- [PROBLEMS PER DAY]: (e.g. 5-8)
- [OUTPUT FORMAT: PDF / Word (.docx) / PowerPoint (.pptx)] (default PDF; the teacher may ask for several)
- [OPTIONAL]: subtopics to emphasize, calculator allowed yes/no, any textbook to mirror.
No upload is required. If the teacher uploads a syllabus or chapter scan and it is unreadable, ask for a clearer source instead of inventing content.
PHASE 1 - UNDERSTAND THE INPUT
Restate the chapter, level, N days, and problems/day in one or two lines so the teacher can confirm. List the 4-8 core subskills of this chapter and order them from foundational to advanced. This ordering becomes the spine of the booklet.
PHASE 2 - DESIGN THE DEEP CONTENT (the learning arc)
Plan an N-day journey, not N random sets. For EACH day produce:
1. A tiny CONCEPT NUGGET (2-4 lines): the one idea or method in plain language, with the key formula or rule and a one-line 'why this works' insight.
2. A worked WARM-UP EXAMPLE with the REASONING shown (the 'why', step by step, not just the final answer).
3. A PROBLEM MIX: mostly fresh problems on today's subskill PLUS 1-2 SPACED-REVISION problems recalling earlier days (label them e.g. 'Revision: Day 2'). Spacing must actually revisit prior days.
4. RISING DIFFICULTY within the day (gentle -> medium -> hard / one stretch problem) and across the booklet (later days are harder, the final day mixes everything).
5. SCAFFOLDED HINTS: a short hint for the 1-2 hardest problems of the day (in the student booklet, kept separate from full solutions).
6. A one-line COMMON TRAP for the day ('students often forget to...') and a 30-second SELF-CHECK / reflection question.
Make problems fresh and non-boring; avoid near-duplicates and avoid problems solvable by blind formula substitution - reward understanding.
PHASE 3 - SOLVE & VERIFY (before writing anything)
Solve every single problem yourself. Use the code tool to compute and double-check exact values, check all cases, and for any 'find all' prove both necessity and sufficiency. No 'clearly' or 'obviously' in solutions - show the step. Never fabricate theorems, data, or statistics. If a problem turns out flawed, fix it before it goes in.
PHASE 4 - BUILD THE FILES IN THE CHOSEN FORMAT
Produce TWO deliverables: (A) the STUDENT DPP BOOKLET (nuggets + warm-ups + daily problems + hints, NO full solutions) and (B) the WORKED-SOLUTIONS BOOKLET (full reasoned solutions, trap notes, key insight per problem). Either two files or two clearly separated sections.
First check what your environment supports, then use a reliable path:
- Word .docx -> python-docx.
- PowerPoint .pptx -> python-pptx (one day or idea per slide group, readable font sizes 18pt+, speaker notes carrying the teacher talking points and solutions).
- PDF -> reportlab or fpdf2 (use pdflatex ONLY if it is genuinely installed; otherwise build the .docx or render with reportlab).
After writing, VERIFY each file actually opens (re-open it / check it is non-empty and page count is sane). NEVER claim a file exists if it does not.
Design: clean, professional, highly readable, generous spacing, clear day headers; black-and-white is fine. Footer on every page (and the title slide for PPT): '[YOUR NAME]'.
Maths rendering: 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 only on an actual LaTeX/PDF path.
HONEST FALLBACK: if you truly cannot generate a downloadable file, output the COMPLETE booklet AND the complete solutions 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) and one short sentence saying what each file is. Then offer: 'Want this in another format (PDF / Word / PPT), more days, or a harder finale? Just say so.'