Stage Design
The baseline method for building ONE stage, a single classroom, with this runtime.
Install
npx skills add THU-MAIC/OpenMAIC --skill stage-design -g -a claude-code -y- Repository
- THU-MAIC/OpenMAIC42.4k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,440 tokens
- Runs scripts
- No, instructions only
What it does
The baseline method for building ONE stage, a single classroom, with this runtime. Covers how the plan is settled in conversation, the order the generation tools are called in, how the classroom roster is written, when narration has to be re-synthesized, and what must be true before a stage is called done. Load this before generating or rebuilding any stage from scratch, whatever its subject; it is the floor the topic skills build on, not an alternative to them.
Building one stage
A stage is one classroom: one settled plan, one roster, one deck of pages. This is how a stage is built here, whatever its subject.
A topic skill (deep-interactive, vocational, deep-research,
teacher-style-clone, …) may shape what the stage contains, its structure, its
page types, how scenes are named, and where one is active its instructions win
on those questions. The sequence below is not one of those questions: it is the
same under every topic skill. Read this one first, then the topic skill.
Nothing here applies to a stage that already has pages. A stage with persisted
pages is edited, not built (see pro-editing).
The build sequence
Build a NEW stage only when there are no persisted pages yet. Then, in this order:
