coding-agent-loop

Build a designed, self-contained HTML academic map of the child's subjects, topics, and materials, plus real coaching notes for the parent on how to teach them better.

Build a designed, self-contained HTML progress report for the child — how she's actually doing, and what to work on next — surfaced in the Progress tab for both parent and child.

Create clear, child-ready study material (notes, worked examples, a revision sheet) for a topic, matched to the child's level and their own uploaded materials, packaged as one activity.

Create a practice test for the child from their materials and progress — child-facing questions with a separate parent-only answer key, packaged as one activity.

Extract genuine interest signals from the child's own conversations and keep memory/interests.md current — a Pulse-only skill, not triggered by a direct parent request.

Extract durable things the parent has said in chat and keep memory/preferences.md current — a Pulse-only skill, not triggered by a direct parent request.

A fun, off-syllabus "something new to explore" activity for the child — a light cover page plus a chat-driven discovery, tailored to grade and interests learned over time. Parent-initiated, handed off like any other activity.

Age/grade-appropriate approach for a coding/programming subject — read this BEFORE create-study-material or create-test when the topic is coding/programming, in addition to that skill.

Read a newly uploaded file from the inbox, classify it, move it into the right subject/topic folder, and write a metadata JSON.

Extract the actual text/content from a file of ANY format — PDF, Word, PowerPoint, Excel, images, scans, archives. The canonical "how do I read this file" reference, reused by process-file, Pulse ingestion, and browser downloads.

Publish a family artifact (a progress report or the academic map) to a shareable destination — a shared folder, a static host, Google Drive, or GitHub Pages — tracking config vs status in files.

Back up the family's learning workspace to a durable destination (local git checkpoint, a private GitHub repo, or an object store like Cloudflare R2 / S3), tracking config vs status in files.

Send the parent a notification at the right moments — the child finished a session, a test/report is ready, a backup completed, or a decision is needed.