with one click
env-check
// 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.
// 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.
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.
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.
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 | env-check |
| description | 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. |
| argument-hint | [--full] |
Run the environment check script and report results to the player in a friendly way:
bash engine/environment-check.sh
Tell the player they're all set. If this is during game start, continue to the game.
Explain which optional tools are missing and when they'll need them:
Guide the player to fix each failure:
sudo systemctl start dockerIf $ARGUMENTS contains "--full", also check:
docker pull hello-worlddocker run --rm hello-worlddocker network create learn-test && docker network rm learn-testBe encouraging — don't make missing optional tools feel like failures.