- Node.js: Introduction to Node.js The official foundation for understanding JavaScript running outside a browser. Use for: runtime, process, filesystem, and network concepts.
- Node.js: Modules and packages
The official description of packages and
package.json. Use for: explaining how a JavaScript project declares its structure. - npm: package.json The official package-manifest reference, including scripts and dependencies. Use for: distinguishing a project manifest from the installed packages.
- Bun documentation The official explanation of Bun as a runtime, package manager, test runner, and bundler. Use for: mapping the general Node.js mental model to CookieMonster's actual development stack.
- OpenCode: Tools The upstream harness documentation for tool access and permissions. Use for: explaining how an AI model gains bounded abilities to inspect and change a project.
- OpenCode: Agents The upstream explanation of agents, Plan, Build, and tool permissions. Use for: teaching read-only exploration versus implementation.
- Local: CookieMonster
package.jsonThe live project manifest. Use for: showing that this repository selects Bun and exposes named development, lint, and type-check commands. - Local: OpenCode README The upstream product overview on which CookieMonster is built. Use for: grounding “coding harness” in the actual product rather than a generic chatbot analogy.
- Team show-and-tell after each module Learners bring one useful result and one confusing or unsafe moment. Use for: developing shared judgement about briefs, scope, and verification.
- Paired first project A learner drives CookieMonster while a second learner acts as reviewer. Use for: making approval and evidence-checking a visible team habit.
- The team’s first concrete motion-design use cases and existing comfort with terminals have not yet been recorded.
- Team-specific rules for client data, approved project locations, and acceptable external context need to be added before production exercises.