Skip to content

Commit ff1a38b

Browse files
author
Tiisetso
committed
Merge remote-tracking branch 'origin/dev' into dev
2 parents 4a2a8dd + f365b27 commit ff1a38b

8 files changed

Lines changed: 1011 additions & 169 deletions

File tree

‎AGENTS.md‎

Lines changed: 85 additions & 3 deletions
Large diffs are not rendered by default.

‎GLOSSARY.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# CookieMonster Foundations Glossary
2+
3+
This glossary records terms only after learners demonstrate that they can use them correctly. New terminology is introduced in the lessons first and promoted here after the debrief.
4+
5+
## Terms
6+
7+
_No terms have been confirmed yet._

‎HANDOVER-wpp-token-counter.md‎

Lines changed: 301 additions & 166 deletions
Large diffs are not rendered by default.

‎MISSION.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Mission: CookieMonster for motion designers
2+
3+
## Why
4+
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.
5+
6+
## Success looks like
7+
- A designer can explain the difference between JavaScript, Node.js, Bun, a terminal, an AI model, and a coding harness in plain language.
8+
- A designer can open the correct project folder, give CookieMonster a bounded brief, and predict what it can and cannot access.
9+
- A designer can choose a read-only or editing workflow intentionally and review evidence before accepting a result.
10+
- The team can apply the same workflow to small motion-production utilities and larger creative projects.
11+
12+
## Constraints
13+
- Assume no coding knowledge and avoid syntax-first teaching.
14+
- Use motion-design and studio-production analogies, but identify where each analogy stops being exact.
15+
- Keep every exercise low-risk, observable, and immediately relevant to creative work.
16+
- CookieMonster uses Bun and Electron in practice, even though Node.js provides the foundational ecosystem model.
17+
18+
## Out of scope
19+
- Teaching JavaScript programming in the foundation module.
20+
- Git branching, package authoring, application architecture, or production deployment before the team understands the harness loop.
21+
- Asking learners to trust an AI-produced change without reviewing the changed files or output.

‎RESOURCES.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# CookieMonster Foundations Resources
2+
3+
## Knowledge
4+
5+
- [Node.js: Introduction to Node.js](https://nodejs.org/learn/getting-started/introduction-to-nodejs)
6+
The official foundation for understanding JavaScript running outside a browser. Use for: runtime, process, filesystem, and network concepts.
7+
- [Node.js: Modules and packages](https://nodejs.org/api/packages.html)
8+
The official description of packages and `package.json`. Use for: explaining how a JavaScript project declares its structure.
9+
- [npm: package.json](https://docs.npmjs.com/cli/v11/configuring-npm/package-json/)
10+
The official package-manifest reference, including scripts and dependencies. Use for: distinguishing a project manifest from the installed packages.
11+
- [Bun documentation](https://bun.sh/docs)
12+
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.
13+
- [OpenCode: Tools](https://opencode.ai/docs/tools/)
14+
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.
15+
- [OpenCode: Agents](https://opencode.ai/docs/agents/)
16+
The upstream explanation of agents, Plan, Build, and tool permissions. Use for: teaching read-only exploration versus implementation.
17+
- [Local: CookieMonster `package.json`](package.json)
18+
The live project manifest. Use for: showing that this repository selects Bun and exposes named development, lint, and type-check commands.
19+
- [Local: OpenCode README](README.md)
20+
The upstream product overview on which CookieMonster is built. Use for: grounding “coding harness” in the actual product rather than a generic chatbot analogy.
21+
22+
## Wisdom (Communities)
23+
24+
- Team show-and-tell after each module
25+
Learners bring one useful result and one confusing or unsafe moment. Use for: developing shared judgement about briefs, scope, and verification.
26+
- Paired first project
27+
A learner drives CookieMonster while a second learner acts as reviewer. Use for: making approval and evidence-checking a visible team habit.
28+
29+
## Gaps
30+
31+
- The team’s first concrete motion-design use cases and existing comfort with terminals have not yet been recorded.
32+
- Team-specific rules for client data, approved project locations, and acceptable external context need to be added before production exercises.
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# CookieMonster training for motion designers
2+
3+
This course teaches CookieMonster as a creative production system, not as a chat box and not as a compressed computer-science degree.
4+
5+
## Recommended course
6+
7+
1. **The machine behind the magic — Node and the coding harness (60 min)**
8+
Learn what executes code, what the model does, what the harness does, and why project scope and verification matter.
9+
2. **Files, folders, projects, and Git (60 min)**
10+
Learn the source-of-truth model: where work lives, how paths work, what changed, and how work can be recovered.
11+
3. **Briefing an agent like a production team (60 min)**
12+
Turn creative intent into an objective, constraints, references, acceptance criteria, and a verification request.
13+
4. **Plan, Build, permissions, and review (75 min)**
14+
Explore read-only, approve bounded actions, inspect diffs and outputs, and recover when a run goes wrong.
15+
5. **Motion-design workflows (90 min)**
16+
Apply the loop to batch utilities, asset preparation, expressions/scripts, data-driven graphics, and project documentation.
17+
6. **Capstone: one real team workflow (90 min)**
18+
Each learner completes a small real task and explains the evidence that makes the result trustworthy.
19+
20+
## Foundation module files
21+
22+
- [Interactive learner lesson](lesson-01-node-and-the-coding-harness.html)
23+
- [Facilitator guide](lesson-01-facilitator-guide.md)
24+
25+
Open the lesson on Windows:
26+
27+
```powershell
28+
Start-Process .\docs\training\cookiemonster\lesson-01-node-and-the-coding-harness.html
29+
```
30+
31+
## Teaching rule
32+
33+
Do not begin with JavaScript syntax. First give learners the system map:
34+
35+
> intent → harness → model decision → tool action → changed project → verification
36+
37+
Syntax becomes useful later, when a learner needs to read or adjust a small piece of code. It is not the entry ticket for using CookieMonster responsibly.
Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
# Lesson 01 facilitator guide: Node and the coding harness
2+
3+
## Outcome
4+
5+
At the end of 60 minutes, each learner should be able to sketch the CookieMonster system from memory and answer:
6+
7+
1. What is executing the code?
8+
2. What folder and context can the harness access?
9+
3. What tools and permissions does the agent have?
10+
4. What evidence will prove the task is complete?
11+
12+
They do not need to write JavaScript.
13+
14+
## Preparation
15+
16+
- Open `lesson-01-node-and-the-coding-harness.html` in a browser.
17+
- Have CookieMonster available for a live demonstration.
18+
- Create a disposable folder containing two or three harmless text files, or use a copy of a non-sensitive creative project.
19+
- Confirm the organization’s rules for client data before showing a real project.
20+
21+
## Run of show
22+
23+
### 0–5 min — Reset the framing
24+
25+
Ask: “When you type a request into CookieMonster, what actually does the work?” Collect answers without correcting them yet.
26+
27+
State the lesson promise: they will leave able to see the machinery, choose the safe mode, and detect when the agent has not really finished.
28+
29+
### 5–18 min — JavaScript, Node.js, and Bun
30+
31+
Use the After Effects analogy:
32+
33+
- An expression is instructions; After Effects is the application that interprets and executes them.
34+
- A `.js` file is instructions; a JavaScript runtime executes them.
35+
- A browser contains a runtime with browser abilities.
36+
- Node.js is a runtime outside the browser with operating-system abilities such as files and networking.
37+
- CookieMonster’s repository primarily uses Bun, a Node.js-compatible runtime and toolkit. The conceptual model transfers, but the command used here is often `bun`, not `node` or `npm`.
38+
39+
Where the analogy stops: Node.js is not a visual application, timeline, renderer, or permanent background service. A Node process begins, does work, and either keeps running or exits.
40+
41+
Show the root `package.json`, but only point out:
42+
43+
- `packageManager`: which toolkit this project expects;
44+
- `scripts`: named project actions;
45+
- `dependencies`: reusable packages the project needs.
46+
47+
Do not explain JSON syntax yet.
48+
49+
### 18–33 min — The harness
50+
51+
Define the coding harness as the working system around the model. It assembles context, gives the model tools, enforces permissions, runs actions, captures results, and maintains the session.
52+
53+
Use the studio analogy:
54+
55+
- model = creative problem-solver;
56+
- harness = producer plus production desk;
57+
- project folder = the job folder;
58+
- tools = departments and equipment;
59+
- permissions = approval gates;
60+
- tests, previews, and diffs = QC;
61+
- session = the job’s working conversation and activity history.
62+
63+
Where the analogy stops: the model and harness are software components, not accountable human specialists. The user remains responsible for the brief, approvals, and final judgement.
64+
65+
### 33–43 min — Map CookieMonster
66+
67+
Walk left to right through the system map in the lesson:
68+
69+
1. The designer supplies intent and selects a project folder.
70+
2. CookieMonster/OpenCode manages the session, rules, context, tools, and permissions.
71+
3. The WPP-hosted model decides the next useful step from the context it receives.
72+
4. Local tools inspect or change the project and return evidence.
73+
5. The harness repeats the loop until it reports an outcome or needs a decision.
74+
75+
Emphasize: the model does not directly possess a folder, terminal, or magic view of the whole computer. The harness mediates those capabilities.
76+
77+
### 43–53 min — Safe live demonstration
78+
79+
Open a disposable folder in CookieMonster. Start in Plan and use:
80+
81+
> Without changing anything, inspect this folder. Explain what is here, what you still do not know, and propose one small useful change. Cite the files you used as evidence.
82+
83+
Ask the room to identify the objective, scope, mode, tools, and evidence.
84+
85+
Then switch intentionally to Build and use:
86+
87+
> Create `handoff-notes.md`. Summarize the folder in five bullets, add a section called “Questions”, and do not change any existing file. Afterward, list exactly what changed.
88+
89+
Review the file and change summary. The success is not that the agent said “done”; the success is that the requested artifact exists, is in scope, and matches the acceptance criteria.
90+
91+
### 53–60 min — Quiz and debrief
92+
93+
Use the interactive check in the lesson. Then ask each learner to finish this sentence:
94+
95+
> CookieMonster can act on a project because the harness…
96+
97+
Do not add terms to `GLOSSARY.md` until learners can explain them without reading the lesson.
98+
99+
## Misconceptions to catch
100+
101+
- “Node is JavaScript.” JavaScript is the language; Node.js is one runtime that executes it.
102+
- “The terminal is Node.” The terminal launches commands; Node or Bun may be one of the programs it launches.
103+
- “CookieMonster is the model.” CookieMonster is the desktop harness; the model is one component behind it.
104+
- “The model sees my computer.” It receives selected context and tool results through the harness.
105+
- “A confident final message proves the work.” Completion requires external evidence: changed files, a diff, a test, a preview, or another observable result.
106+
- “Plan can never act.” Treat Plan as the analysis-first mode and still read any approval prompt; exact permissions can be configured.
107+
108+
## Assessment rubric
109+
110+
Ready for module 2:
111+
112+
- Correctly places runtime, model, harness, tools, and project folder on the map.
113+
- Can explain why selecting the wrong folder changes the task’s scope.
114+
- Uses Plan for uncertain exploration and Build only when an edit is intended.
115+
- Names an appropriate verification method before accepting “done.”
116+
117+
Needs another pass:
118+
119+
- Treats CookieMonster as an all-seeing chatbot.
120+
- Cannot distinguish the terminal, runtime, model, and harness.
121+
- Accepts prose as proof of a file or visual change.
122+
- Cannot state which folder is in scope.

0 commit comments

Comments
 (0)