Idea-to-Action Studio

What you will make

A notes-to-checklist helper with source references

• Parse a simple text convention into structured checklist records.
• Keep human review and source evidence attached to assistant suggestions.
• Save and export an editable plan using browser-local data.
• Compare a workflow against a stated, repeatable baseline.

Settle in together

Laptop or desktop with a modern browser for editing. Phones can read the guide and observe or try the preview. Start with fictional data.

Allow about 5 minutes to get ready. Six missions in order. Try one or two 5–12 minute activities, take a break, and resume at the next activity. Plan several short sittings per mission; the full 75–90 minute lesson remains the detailed reference. End each sitting with a saved copy and one sentence: next time we will… Times are estimates awaiting family pilots.

• For ages 9–12, work beside a parent on a computer with a keyboard. A phone can read the guide and watch; use a computer for editing. Older learners may try the full lesson's stretch task after the core checks.
• Open the first mission's browser workspace and press Run before installing anything. No payment, child account, or AI key is needed for that introduction. If the runtime reports unavailable, keep your files, read its error, and use the course-specific fallback below with adult help.
• The initial buildChecklist copies every nonempty line, including facts. Draft validation is initially weak, Save/Load do not save yet and export initially contains only task text. Missions add these features in order; supplied drafts make AI optional.
• Parent-guided same-version local handoff: keep the current workspace tab open and record one exact edited line/value from File index.html (such as your changed heading or installed exportPlan). Use Export backup, then the trusted parent-page Download index.html. Keep both downloads; JSON is a backup, not an executable app. Download /lab-starters/productivity-apps.zip, extract a fresh productivity-apps folder, and replace only its root index.html with the downloaded current source. Confirm its actual name is index.html, not index.html.txt, and open it as plain text to find the recorded edited line before claiming local evidence. No packages are needed. Open that replaced file in a separate LOCAL app tab. Record/recreate the same fictional notes, edited tasks and checkboxes locally: workspace appStorage does not automatically populate this tab's app memory. Check your known source edit and its expected behavior there. Open DevTools Console for the LOCAL app tab, not the guardian page or opaque preview. If file-origin storage is blocked, a parent runs python3 -m http.server 8080 --bind 127.0.0.1 from that extracted folder and opens http://127.0.0.1:8080/index.html; re-enter the fixture because this is another origin. Keep the workspace/JSON backup if a browser or storage check fails, and record that check as pending or failed rather than credited to a pristine download. Repeat transfer and verification after further code edits.
• Replace complete named functions from the full lessons once, preserving render and button handlers. The embedded preview blocks learner-initiated Download text; the trusted Download index.html handoff enables the required standalone report check without changing that restriction.
• Keep original four notes: Project: Moon Garden; TODO: Draw three moon flowers; Fact: The display uses blue paper; TODO: Build a paper rocket, each on its own line. Mission 1 adds a fifth TODO for a welcome sign; mission 3 restores the original four for shared draft references. All notes stay fictional and local.
• Keep the original starter unchanged as a reference. Export a working copy before a risky edit or reset. Work and the optional progress checklist stay on this device; an export is your portable backup. A checked box records your own report, not a verified assessment.
• Use invented names, notes and records. The parent handles accounts, optional AI and sharing. Predict together, let the child make one choice, change one thing, test it, then explain what happened. An assistant is optional; the supplied code and a partner work too.