← ask sheen Teacher Training Handbook Open the canvas

sheen robotics · teacher training handbookask sheen — the AI coding tutor inside the sheenbot canvas

Platform: sheen.bot coding canvas Board: sheenbot∞ Audience: teachers July 2026 edition

ask sheen is the AI coding tutor built into the top-right corner of the coding canvas. It runs on one rule: help students think — never think for them. It asks before it answers, scaffolds before it solves, and the full answer is always the student's explicit last choice. This handbook walks you through all three modes — the dialogue flows, classroom procedures, and teaching scenarios — so you can turn it into a patient teaching assistant in every seat.

Note: the interface figures in this handbook are 1:1 reconstructions of the live product's UI and copy (the dialogue content is illustrative). The product itself is the source of truth.

01

Meet ask sheen: the launcher and the three modes

Open the canvas (a logged-in project or the free, no-account canvas at sheen.bot/canvas-try) and you'll find a round blue button pinned to the top-right corner — that's ask sheen. Nothing to install; it works on the laptops, tablets and phones your classroom already has.

sheen.bot — coding canvas
1 ask sheen2 ask sheen3
Figure 1 · The launcher in the canvas's top-right corner
  • 1At rest it's just sheen's face — no canvas space wasted;
  • 2On hover (or a tap on tablets) it expands to "ask sheen";
  • 3While a panel is minimized the button pulses — "you have a session waiting". One click restores it with the whole conversation intact.

Clicking the button opens a two-step entry: step 1 picks who is coding, step 2 picks what to do. The age choice is remembered on the device, so returning students land straight on step 2.

ask sheenHi, I'm sheen! I help you think — I never do the thinking for you.

Hi Alex 👋

Who is coding today?

Younger (voice & pictures)
Older (type or talk)
1
ask sheenI'm sheen — your thinking buddy, not your homework machine. 🧠
Change

What do you want to do?

Build something newI'll guide you step by step, then give you a scaffold to finish.Resumes your current session.3
I'm stuck — help me debugI give layered hints so you find the problem yourself.
Explain my codeI'll walk you top-to-down through what each block does.
2
Figure 2 · The entry dialog: step 1 (age) on the left, step 2 (mode) on the right.
  • 1Logged-in students are greeted by name. "Younger" = questions read aloud + big picture choices; "Older" = open questions, typed or spoken;
  • 2"Change" (top-left) switches the age band any time — remind students to switch on shared devices;
  • 3A mode you've already opened shows "Resumes your current session" — closing the dialog never loses progress.

The three modes at a glance

Build something new

From a one-sentence idea to a runnable scaffold, guided through six stages. Best for project kick-offs and free creation.

I'm stuck — help me debug

Layered hints on the student's own program: the area first, then the block, only then the fix. Best for debugging time.

Explain my code

Turns any program into a step-by-step walkthrough that spotlights blocks on the canvas. Best for revision, review and presentations.

Teaching tip

In the first lesson, walk the whole class through the two-step entry together: pick the age band, then learn the three icons (wand = build it, wrench = fix it, book = explain it). From then on your classroom shorthand can simply be "ask sheen's wand / wrench / book".

02

Mode 1 "Build something new": from idea to scaffold

The student states an idea (say, "tell us when the classroom gets too hot") and sheen advances through six stages — Idea → Sense → Do → When → Plan → Build — asking exactly one guiding question per stage. Which sensor, what threshold, what happens when: every decision belongs to the student.

Build it with meI'll help you think it through — you do the building. 2
IdeaSenseDoWhenPlanBuild 1

Great idea! An automatic "too hot" alert is really useful. First, let's work out how the program will know it's hot.

How do you want to sense the temperature? Tell me your thinking.

With the temperature & humidity sensor — above 30 degrees counts as too hot.
3
ConversationListening…4
Figure 3 · A guided question (older band, "Sense" stage).
  • 1Stage chips: light blue = done, solid blue = current, grey = still to come — students always know where they are;
  • 2Header buttons: minimize (peek at the canvas), start over (fresh session), close (progress kept);
  • 3Three ways to answer: type, tap the mic and talk, or tap the speaker to hear the question read aloud;
  • 4"Conversation" mode goes fully hands-free: sheen reads the question, auto-opens the mic, and a pause auto-submits the answer.

After the six stages sheen recaps the whole plan in plain language and asks the student to confirm — the student owns the design before a single block is placed. Confirming also picks the delivery:

IdeaSenseDoWhenPlanBuild
Here is your plan

A "classroom heat alert": the program keeps reading the temperature. Above 30 °C it turns the light red and plays a warning tone; back below 30 °C it switches the light off.

  1. Initialize the board and the temperature & humidity sensor
  2. Forever: read the current temperature
  3. If the temperature is above 30 °C: RGB light red + buzzer warning
  4. Otherwise: switch the RGB light off

How do you want to build it?

Challenge — build a scaffold, I'll finish it Build the complete program for me Change something 1
Figure 4 · Plan confirmation: own the plan first, then choose the delivery.
  • 1"Challenge" is the recommended default — a scaffold with gaps the student finishes. "The complete program" exists too, but it is always the student's explicit choice, never something sheen volunteers. "Change something" loops back into the dialogue.

Picking the right blocks

Placed 12 blocks…  ·  Building your scaffold usually takes 10–20 seconds.

Figure 5 · Progress while building: staged narration (Reading your plan → Picking the right blocks → Wiring everything up) plus a live block counter. Ordinary replies start streaming within ~2–5 seconds; the scaffold takes 10–20 seconds — tell students up front so the wait feels normal.
Your starting scaffold

This is a starting point — not the finished program. Your job is to fill the gaps below.

Your turn — fill these in

if temperature > (empty slot) then — real canvas block

Fill in the "too hot" threshold

Think: at what temperature does your classroom feel too hot? Try a number between 28 and 32, then test it for real.

1
Set onboard LED, colour slot empty — real canvas block

Pick the alert colour

Which colour says "warning" best? Why?

Before you build — explain it
  • Why does the "if" check live inside the "forever" loop?
  • What would the program do if > became <?
2
Add scaffold to a new project3
Figure 6 · Scaffold delivery (Challenge mode).
  • 1Every gap comes with a real block picture and a hint that says what to think about, not what to type; tapping a block picture locates it on the canvas or in the toolbox;
  • 2The "explain it" prompts are ready-made for pair-explaining or cold-calling — "you understand it when you can explain it";
  • 3The scaffold always opens as a new project — it never overwrites the student's work. Before delivery sheen also test-runs the program in the simulator and silently rebuilds it once if it fails.

Classroom procedure

  1. Have students describe the idea in one full sentence (board template: "I want to build a ____ that ____ when ____");
  2. Students answer stage by stage — encourage reasons, not "right answers";
  3. Pause at the Plan stage: each student reads their plan to a partner before tapping "Challenge";
  4. Scaffold lands in a new project → fill the gaps → run on the board or simulator → answer the "explain it" prompts.
Teaching tip
  • Make "Challenge" the class default: "Pick Challenge first. If you truly can't finish, come back for the complete program — but be ready to explain every block to me."
  • If a student types gibberish, sheen gently pushes back: "Hmm, I couldn't make sense of that. Tell me in a few words what you want to build or what problem you want to solve." — a built-in exercise in stating requirements clearly.
  • With younger groups, lean on voice: questions are read aloud and answers can be spoken — typing speed is never the bottleneck.
03

Mode 2 "I'm stuck — help me debug": layered hints

When a program doesn't behave, students pick this mode. sheen first asks them to describe in their own words what the program should do (often half the diagnosis right there), then helps in three escalating layers — one layer at a time, with the answer always last:

Hint 1 — the area

"The problem lives around here" — the region glows on the canvas; the student goes looking.

Hint 2 — the suspect block

Names the suspicious block with the reasoning, plus a question to chew on. Still no answer.

Hint 3 — the fix

Only when truly stuck: the concrete change, applied to the student's own blocks, opened as a new project.

Stuck? Let's find it togetherI'll nudge you toward the problem — not just hand you the answer.

In your own words, what should your program do?1

This helps me understand what to look for.

When I press button A, the onboard light should turn green.
Hint 1 — the area

Your light-control blocks look fine. The problem is more likely around the button check — look at the blocks that read the button. Do they actually fire when you run it?

Show me on the canvas2
Hint 2 — the suspect block

This block Button B is pressed — real canvas block looks suspicious: your goal is to trigger on button A, but it checks button B. Think: when would the light turn on right now?

Show me on the canvas
Hint 3 — the fix

Change the B in the button check to A — pressing A will then enter the light-up branch.

Still stuck? Tell me exactly where — or just tap “show me more”.

Where are you stuck? (optional)
3
Still stuck? Show me more Open suggested fix as new project 4
Figure 7 · A layered-hint session: the opening goal question on the left; the three hint layers fully revealed on the right.
  • 1Stating the goal comes first — many "bugs" get solved by the student in this very step;
  • 2Every hint offers "Show me on the canvas": the panel steps aside and the relevant blocks glow;
  • 3Engagement is rewarded: a student who types or says where they think the bug is gets a sharper hint at the same level — not the answer. Only bare taps on the button move down a level;
  • 4A "Just show me the fix" button appears only after the first two layers; an accepted fix is applied to the student's own blocks and opened as a new project, keeping the original for comparison.
Teaching tip
  • Class rule: "After each hint, say 'I think the problem is…' out loud before you tap for more." That turns debugging into hypothesis-and-test;
  • Circulation strategy: students ask sheen first; you only take over when someone is still stuck after Hint 3 — your time goes to the genuinely hard cases;
  • The fix opening in a new project is perfect for a compare-and-contrast: "what exactly changed between the broken and fixed versions?"
04

Mode 3 "Explain my code": every program becomes a story

One tap turns the workspace into a step-by-step walkthrough: an overview first, then each step lights up exactly the blocks it covers — read aloud automatically for younger students. The walkthrough card floats at the bottom of the canvas, clear of the blocks.

sheen.bot — coding canvas
The heat-alert program on the real canvas, if-block spotlighted 1
Explain Step 3 / 5
Check whether it's too hot

This step compares the variable "temperature" with 30. Only when the temperature is above 30 does the block inside run — the onboard LED turns red. This is where your program makes a decision.

show on canvas
Prev Next
2
Figure 8 · Explain mode: the step card and the canvas spotlight move together.
  • 1The blocks covered by the current step glow on the canvas (here, the "if" check and everything inside it); the spotlight follows as you change steps;
  • 2Card buttons, left to right: read aloud, re-fetch the explanation (use after editing the program), minimize, close; Prev / Next move freely in both directions.

Four high-value uses

  • Inheriting a project — when teams rotate or continue last term's build, a new member reads the code in minutes, not lessons;
  • Learning from examples — open a class sample, hear it explained block by block, then remix it;
  • Classroom review — project a student's build and let sheen narrate it to the whole class, blocks glowing in sync — far clearer than describing code out loud;
  • Presentation rehearsal — before a demo or assessment, students hear their program explained once, then close the card and retell it themselves.
Teaching tip

The walkthrough is generated from the current canvas: after editing the program, tap the refresh button ("re-fetch the explanation"). An empty canvas shows "Workspace is empty — add some blocks first." Switching age band or interface language regenerates the walkthrough for the new audience.

05

Controls that work across all three modes

Voice: read-aloud, speak-to-answer, hands-free

  • Read aloud — the speaker button next to every question reads it out; the younger band auto-plays it, so reading level is never a barrier;
  • Speak your answer — tap the mic and talk; a live transcript fills the input box. Great for slow typists;
  • Conversation mode — fully hands-free: sheen reads the question, auto-opens the mic ("Speaking…" / "Listening…"), and a pause submits the answer.

Which sensor will spot "too hot"?(reading aloud)

🌡️Temp & humidity
💡Light sensor
🎤Sound sensor
Figure 9 · The younger band: questions auto-read, big picture choices to tap, and a big mic to talk into. Six-year-olds who can't read yet can still complete the whole flow.

Session management

ActionWhereWhat happens
MinimizeArrows icon, panel headerPanel steps aside so the canvas (e.g. highlighted blocks) is visible; a pulsing "ask sheen" pill appears top-right — one click restores, conversation intact
Close✕ in the panel headerPanel closes but the session survives — reopening the same mode shows "Resumes your current session."
Start overCircular-arrow icon, panel headerClears that mode's conversation for a genuinely fresh start (new task)
Change age band"Change" chip, entry step 2Switches Younger / Older; the choice is stored per device — switch it when students share hardware

Block pictures and hardware awareness

  • When sheen mentions a block it shows the real block picture (e.g. DHT11 sensor read temperature — real canvas block) — tap it and the canvas locates the block, or guides the student to it in the toolbox;
  • sheen knows the sheenbot∞ board: which modules are built in, which pins they occupy, which combinations conflict. A wiring plan that collides with an on-board module or the I²C bus gets flagged before the student hits run.

Feedback: help the AI get better

Help improve the AITell us how this build went — it helps the AI get better.
Good Needs work
Optional — tell us what was wrong or what you changed…
Send my corrected blocks as an example
Send feedback
Figure 10 · The feedback dialog: after any guided build or debugging session, a "Feedback" button sits at the bottom of the panel. When you spot a weak generation, fix the blocks yourself, tick "Send my corrected blocks as an example", and submit — your correction becomes a teaching example that improves the AI for every classroom.
06

Classroom scenarios and suggested scripts

① Project kick-off · starting from zero

One sentence from the student → six guided stages → confirmed plan → scaffold. The hardest part of a kick-off — "I don't know where to start" — is carried by sheen, so everyone gets moving.
Script: "Tell sheen your idea first. Screenshot 'Here is your plan' and show me before you build."

② Differentiation · same task, many levels

Stronger students take the "Challenge" scaffold, fill the gaps, then extend it. Students who need support may take the complete program — as long as they can explain every block. Younger groups switch to the voice-and-pictures band.
Script: "The complete program is fine — but then you're the teacher: explain it to your partner."

③ Debugging time · too many hands up

During debugging, the class asks sheen first: digest Hints 1 and 2 alone; only students still stuck after Hint 3 raise a hand. You go from firefighter to consultant on the hard cases.
Script: "Let sheen point the way first — and tell it where you think the bug is; your hints get sharper."

④ Review · narrated show-and-tell

Project a student's build, open "Explain my code", and let sheen walk the whole class through it, blocks glowing in sync — while the author adds the design decisions behind it.
Script: "Watch the highlighted blocks — where does your program do this differently?"

⑤ Inherit & remix · second-hand code

Open last term's project, a teammate's build, or a class sample: "Explain" it first to understand it, then use "help me debug" with the new target described ("now it should trigger when it gets dark") and sheen works out what to adjust.
Script: "Have sheen explain it once before you change a single block."

⑥ Presentations · rehearse the story

Before demos, fairs or assessment: students hear sheen explain their program, learn what a good code walkthrough sounds like, then close the card and retell it in their own words to their group.
Script: "Listen to how sheen tells it — now tell it better, with your own reasons."

07

Feature highlights (for introducing it to students and parents)

A tutor, not an answer machine

Questions first, scaffold second; the full answer is always the student's explicit choice at the end of the flow.

Six-stage guidance

Idea → Sense → Do → When → Plan → Build. One question per stage; every decision is the student's.

Layered hints

Area → block → fix, one layer at a time. Saying where you think the bug is earns sharper hints — effort is rewarded, shortcuts aren't.

Walkthroughs tied to the canvas

Each explanation step lights up its blocks, with read-aloud — programs become visible stories.

Age-aware by design

Younger: auto read-aloud + big picture choices. Older: open questions about conditions, loops and sequence.

Voice throughout

Read-aloud, speech input, and a hands-free conversation mode — reading or typing speed is never the barrier.

It knows the board

On-board modules, pin usage, bus conflicts — clashing wiring plans are flagged before the student hits run.

Real block pictures

Blocks in the chat are real pictures — tap one and the canvas finds it, or the toolbox guides you to it.

Never overwrites student work

Scaffolds and fixes always open as new projects; generated programs are test-run in the simulator first.

The one-liner for parents: ask sheen doesn't write code for your child — it's an always-available coding coach whose first question is "what do you think?" Nothing to install; it runs on the devices the school already has.

08

Quick troubleshooting

Symptom / questionWhyWhat to do
"Workspace is empty — add some blocks first.""Explain" and "help me debug" both work on the program on the canvasHave the student place blocks first, or start with "Build something new"
"Hmm, I couldn't make sense of that…"The input was noise (random taps, gibberish)Coach the student to state the goal in one full sentence — that's the exercise
"The server is busy right now. Please try again in a moment."Peak load or a network blipTap "Try again"; with a full class, stagger the "Build" taps a little
Students spam "Show me more" straight to the answerBare taps do escalate one layer at a timeBy design "Just show me the fix" only appears after the first two layers; add the class rule "say where you think the bug is first"
Will the scaffold overwrite student work?No — scaffolds and fixes always open as a new project; the original stays untouched
Wrong age band on a shared tabletThe band is remembered per deviceEntry step 2 → "Change"
No read-aloud / mic doesn't workBrowser permission missing or unsupportedCheck the browser's microphone permission; use a current Chrome / Edge. Typing keeps working regardless
The walkthrough doesn't match the canvasThe program was edited after the walkthrough was generatedTap the refresh button on the card ("re-fetch the explanation")
How long do things take?Replies start streaming in ~2–5 s; scaffolds take 10–20 s with live progress — set expectations up front
Closing the training session

Reserve the last 20 minutes for every teacher to complete the triangle hands-on: build a heat alert with the wand → break it on purpose and trace it with the wrench → finish by hearing the book explain it. Teachers who have felt the full loop once will demo it naturally in class.