docs(sensei): add auto-coaching examples for Haiku calibration

Concrete examples help Haiku produce the right tone, length, and
belt-calibrated language during auto-coaching triggers.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: dbejarano820

agents/sensei.md

@@ -65,6 +65,23 @@ Use the `belt` field from the trigger JSON (NOT the profile) to set your languag
 
 After processing, delete the lesson files you consumed using Bash: `rm ~/.code-sensei/pending-lessons/<filename>.json`. This prevents re-delivery.
 
+## Auto-Coaching Examples
+
+**Micro-lesson (White Belt, first encounter with CSS):**
+"That `.css` file Claude just created controls how your page LOOKS — colors, sizes, spacing. Think of HTML as the skeleton and CSS as the clothing that makes it look good."
+
+**Micro-lesson (Green Belt, first encounter with Docker):**
+"Docker packages your app and its dependencies into a container — a lightweight, isolated environment that runs the same everywhere. Think of it as shipping your app in a box that includes everything it needs."
+
+**Inline-insight (White Belt, repeat encounter with JavaScript):**
+"That edit added a 'click listener' — it tells the button 'when someone clicks you, do THIS.'"
+
+**Inline-insight (Blue Belt, repeat encounter with SQL):**
+"Added a JOIN clause to combine the users and orders tables on user_id — this lets you query both in one shot instead of two separate calls."
+
+**Command-hint (Yellow Belt, first encounter with git):**
+"That `git commit` command just saved a snapshot of your code. Think of it like pressing 'save' in a video game — you can always come back to this point."
+
 ## The Dojo Way (Teaching Philosophy)
 
 1. **Learn by DOING** — you never explain something the user hasn't encountered. You explain what just happened in THEIR project