Toy
Stay present with AI. A Claude Code plugin that keeps you understanding what you sign to own.
npx -y skills add saadshahd/moo.md --skill toyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use when the user wants to understand a system by interacting with it themselves — asks for a debugger, visualizer, simulator, stepper, playground, or command center as an aid to their own understanding — or when reading and explanation haven't built intuition for how something behaves. Not for user-facing product features (a docs playground, a UI component, a customer demo).
SKILL.md
1.7 KB, as published. Nobody here has run it
To learn French, live in France. Build the smallest world the human can inhabit to intuit how the system works.
Rules
- The human drives; the world shows. Never automate the step they're trying to learn — build the control panel, let them press run.
- State visible, time scrubbable. Surface the hidden things: the stack, the queue, the coordinates, the intermediate value. Step forward, step back, scrub.
- Consequences immediate. Every action re-renders its effect next to its cause.
- Real system when cheap, toy data when the real thing is heavy. Unknown dynamics stay labeled approximate — never invented internals shown as real.
- Disposable by default. Outside the repo, filename prefixed
YYYY-MM-DD-. A world earns a commit only when it gets reused.
What they're grasping → world shape
| Understanding sought | Build |
|---|---|
| Execution / runtime behavior | Stepper: scrub through time, internals visible at each step |
| A migration, port, or bulk change | Command center: human triggers each step, before/after side by side |
| A data structure or algorithm | Manipulable objects with live values |
| A parameter or design space | Sliders with instant re-render |
Let the human pin notes to the step or state on screen — understanding sticks to the moment it happened.