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.
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.
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.
Hi Alex 👋
Who is coding today?
What do you want to do?
From a one-sentence idea to a runnable scaffold, guided through six stages. Best for project kick-offs and free creation.
Layered hints on the student's own program: the area first, then the block, only then the fix. Best for debugging time.
Turns any program into a step-by-step walkthrough that spotlights blocks on the canvas. Best for revision, review and presentations.
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".
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.
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.
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:
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.
How do you want to build it?
Picking the right blocks
Placed 12 blocks… · Building your scaffold usually takes 10–20 seconds.
This is a starting point — not the finished program. Your job is to fill the gaps below.
Your turn — fill these in
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.
1Pick the alert colour
Which colour says "warning" best? Why?
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:
"The problem lives around here" — the region glows on the canvas; the student goes looking.
Names the suspicious block with the reasoning, plus a question to chew on. Still no answer.
Only when truly stuck: the concrete change, applied to the student's own blocks, opened as a new project.
In your own words, what should your program do?1
This helps me understand what to look for.
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 canvas2This 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?
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”.
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.
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 canvasThe 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.
Which sensor will spot "too hot"?(reading aloud)
| Action | Where | What happens |
|---|---|---|
| Minimize | Arrows icon, panel header | Panel 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 header | Panel closes but the session survives — reopening the same mode shows "Resumes your current session." |
| Start over | Circular-arrow icon, panel header | Clears that mode's conversation for a genuinely fresh start (new task) |
| Change age band | "Change" chip, entry step 2 | Switches Younger / Older; the choice is stored per device — switch it when students share hardware |
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."
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."
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."
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?"
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."
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."
Questions first, scaffold second; the full answer is always the student's explicit choice at the end of the flow.
Idea → Sense → Do → When → Plan → Build. One question per stage; every decision is the student's.
Area → block → fix, one layer at a time. Saying where you think the bug is earns sharper hints — effort is rewarded, shortcuts aren't.
Each explanation step lights up its blocks, with read-aloud — programs become visible stories.
Younger: auto read-aloud + big picture choices. Older: open questions about conditions, loops and sequence.
Read-aloud, speech input, and a hands-free conversation mode — reading or typing speed is never the barrier.
On-board modules, pin usage, bus conflicts — clashing wiring plans are flagged before the student hits run.
Blocks in the chat are real pictures — tap one and the canvas finds it, or the toolbox guides you to it.
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.
| Symptom / question | Why | What to do |
|---|---|---|
| "Workspace is empty — add some blocks first." | "Explain" and "help me debug" both work on the program on the canvas | Have 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 blip | Tap "Try again"; with a full class, stagger the "Build" taps a little |
| Students spam "Show me more" straight to the answer | Bare taps do escalate one layer at a time | By 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 tablet | The band is remembered per device | Entry step 2 → "Change" |
| No read-aloud / mic doesn't work | Browser permission missing or unsupported | Check the browser's microphone permission; use a current Chrome / Edge. Typing keeps working regardless |
| The walkthrough doesn't match the canvas | The program was edited after the walkthrough was generated | Tap 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 |
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.