deep-interactive
/deep-interactive
Deep Interactive courses. Plans the course so the learner manipulates something on most pages — simulations, diagrams they explore, code they run, games, 3D scenes — with slides reserved for the opening frame and the closing consolidation. Use when the topic has a mechanism, a variable to vary, a process to trace, or a structure to inspect.
- Author
- thu-maic ↗
- Repository
- openmaic ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Deep Interactive courses. Plans the course so the learner manipulates something on most pages — simulations, diagrams they explore, code they run, games, 3D scenes — with slides reserved for the opening frame and the closing consolidation. Use when the topic has a mechanism, a variable to vary, a process to trace, or a structure to inspect.
Original author description
Deep Interactive courses. Plans the course so the learner manipulates something on most pages — simulations, diagrams they explore, code they run, games, 3D scenes — with slides reserved for the opening frame and the closing consolidation. Use when the topic has a mechanism, a variable to vary, a process to trace, or a structure to inspect.
How it works
- Structure
- Choosing a widget type
- widgetOutline
- Scene naming
- keyPoints
SKILL.md preview
--- name: deep-interactive title: "深度交互" description: Deep Interactive courses. Plans the course so the learner manipulates something on most pages — simulations, diagrams they explore, code they run, games, 3D scenes — with slides reserved for the opening frame and the closing consolidation. Use when the topic has a mechanism, a variable to vary, a process to trace, or a structure to inspect. --- # Deep Interactive course design Default to **doing**, not reading. A page earns the `slide` type only when the learner has nothing to manipulate on it. ## Structure - Scene 1 is a `slide`: it frames the question the course answers and tells the learner what they are about to play with. One page, no more. - The body is `interactive`. Each body scene isolates **one** mechanism, one variable, one structure — so the learner can change it and watch the result. - The last scene is a `slide` or a `quiz` that consolidates what the manipulation showed. - Consecutive interactive scenes must not use the same `widgetType`. Two simulations in a row is a design failure; vary the modality as the concept moves from "watch it" to "trace it" to "predict it". ## Choosing a widget type | widgetType | Use when the learner should… | | ----------------- | ---------------------------------------------------------------- | | `simulation` | vary parameters and watch a system respond in real time | | `diagram` | explore structure, flow or hierarchy by expanding and following | | `code` | read, modify and run a short program that embodies the idea | | `game` | make repeated decisions under a rule set and see the score move | | `visualization3d` | inspect a spatial object or scene from angles a slide cannot show | ## widgetOutline Every `interactive` scene must carry a `widgetOutline` populated for its type — an interactive scene with an empty widget outline degrades to a generic page and defeats the whole point. - `simulation`: `concept`, `keyVariables` (the actual sliders/inputs) - `diagram`: `diagramType`, `nodes` (with `label`, and `parentId` for hierarchy) - `code`: `language`, `concept` - `game`: `gameType`, `challenge`, `playerControls` - `visualization3d`: `visualizationType`, `objects`, `interactions` ## Scene naming Titles name what the learner does or discovers, not the topic heading. - Good: 「拖动倾角,看射程怎么变」「顺着数据流走一遍」「猜下一步会发生什么」 - Bad: 「抛体运动」「数据流概述」「知识点回顾」 ## keyPoints For an interactive scene, `keyPoints` describe the **interaction and what it reveals** — what the learner changes, what they observe, what conclusion the observation forces. Not a bullet list of facts to be read out.
Files in this package (2)
- SKILL.md 3 KB
- outline-constraints.json 1 KB
Versions
The database has no other skills named deep-interactive.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version a16dbe1545f4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100claude-docs-course
Generate an interactive, self-contained HTML course on any Claude documentation topic. Use this skill when the user wants to create an interactive course, tutorial, or deep-dive walkthrough about a Claude feature, API concept, SDK pattern, or prompt engineering technique.… - 100book-to-course
Turn a book or document (EPUB, PDF, HTML, DOCX, Markdown, TXT — e.g. a programming course book) into a complete interactive beginner-friendly course delivered as a local web page, with step-by-step explanations, animations, quizzes, chapter tests, flashcards, hints, programming… - 100explainer-design-system
Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger… - 100codebase-to-course
Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger… - 90workshop-style
Hands-on workshop — the learner works through the course instead of watching it, with an exercise or a check every couple of pages, short slides that only set up the next task, guiding narration that asks more than it tells, and a closing page where the pieces come together in… - 100iblai-api-studio-course-create
Create a course on Open edX Studio (studio.learn.iblai.app) from the terminal — POST the org key and display name (optionally number and run) to Studio's course-management endpoint and get the course key back; list the user's courses, read a course summary, derive the course…