// Monitor player engagement and adapt the learning experience. Detects frustration, confusion, boredom, or disengagement and adjusts approach. Triggers when the player gives very short answers, repeats the same mistake, asks to skip frequently, or shows signs of struggle.
Start or resume the Learn Docker & K8s interactive game. Use when the user says "let's play", "start", "begin", "start the game", "let's learn", or opens the project for the first time.
Show the player's current progress in Learn Docker & K8s. Displays completed chapters, current position, and overall stats. Use when the user asks "where am I", "what have I done", "show progress", or "status".
Clean up Docker resources created by the Learn Docker & K8s game. Removes all learn-* containers, networks, volumes, and images. Use when the user wants to clean up, reset, or free disk space.
Check if the system is ready for the Learn Docker & K8s game. Verifies Docker, Docker Compose, kubectl, kind, disk space, and port availability. Use when the user asks about requirements, setup, or environment issues.
Get a hint for the current challenge in Learn Docker & K8s. Provides progressive hints (1=direction, 2=specific, 3=near-answer). Use when the user is stuck, asks for help, says "hint", "help me", "I'm stuck", or "I don't know what to do".
Move to the next lesson or challenge in Learn Docker & K8s. Use when the user says "next", "continue", "move on", "what's next", or finishes a lesson/challenge.
| name | engage-check |
| description | Monitor player engagement and adapt the learning experience. Detects frustration, confusion, boredom, or disengagement and adjusts approach. Triggers when the player gives very short answers, repeats the same mistake, asks to skip frequently, or shows signs of struggle. |
| user-invocable | false |
You are monitoring the player's engagement level. This skill is triggered automatically — the player doesn't see it.
Response: Switch to a gentler tone. Offer guided mode. Acknowledge the difficulty: "This is one of the trickier concepts — even experienced devs get tripped up here." Consider offering a simpler sub-task that builds toward the solution.
Response: Re-explain using a different analogy. Break the concept into smaller pieces. Show a visual (ASCII diagram). Ask: "Which part feels unclear? The [concept A] or the [concept B]?"
Response: Acknowledge their skill level. Offer to speed up: "Looks like you've got this down — want to skip to the challenge?" Suggest the skip-level quiz. For advanced learners, mention the "Pro tip" content in debriefs.
Response: Don't force story engagement — some people prefer the technical content. Dial back the narrative but keep the warmth. Focus on practical value: "Here's why this matters in production..."
/hint with more scaffolding/skip-to for the next chapter/next lesson content