Enable a team of motion designers to use CookieMonster as a safe, practical creative-production partner without requiring them to become software engineers first. The training should replace “AI magic” with a usable mental model of runtimes, project folders, tools, permissions, and verification.
- A designer can explain the difference between JavaScript, Node.js, Bun, a terminal, an AI model, and a coding harness in plain language.
- A designer can open the correct project folder, give CookieMonster a bounded brief, and predict what it can and cannot access.
- A designer can choose a read-only or editing workflow intentionally and review evidence before accepting a result.
- The team can apply the same workflow to small motion-production utilities and larger creative projects.
- Assume no coding knowledge and avoid syntax-first teaching.
- Use motion-design and studio-production analogies, but identify where each analogy stops being exact.
- Keep every exercise low-risk, observable, and immediately relevant to creative work.
- CookieMonster uses Bun and Electron in practice, even though Node.js provides the foundational ecosystem model.
- Teaching JavaScript programming in the foundation module.
- Git branching, package authoring, application architecture, or production deployment before the team understands the harness loop.
- Asking learners to trust an AI-produced change without reviewing the changed files or output.