chapter-content-generator
Installation
SKILL.md
Chapter Content Generator
Version: 1.11
Version 1.11 Features:
- Precise, objective-first MicroSim specifications - Every specification block now states what the learner must learn and prove, and the complete content the sim needs, instead of how to build the sim. New structured fields (
Bloom Level,Bloom Verb,Learning Objective,Evidence of Mastery,Misconceptions,Instructional Rationale,Content,Provenance,Rules,Learner Activity,Feedback,Starting State,Chapter Anchors) and a self-check are defined in the newreferences/microsim-specification-rules.md. Layout, pixel sizes, colors, control placement and library calls are left to the microsim-generator. The rules come from a 112-MicroSim batch run in which agents reported 450 missing specification details and 49% of the sims had to depart from their spec. - Bloom fields the batch tools can parse -
**Bloom Level:**and**Bloom Verb:**are separate header lines. The previous inline form,Learning objective (Bloom level: X; verb: Y):, could not be parsed, and the tools labeled 109 of 112 sims "Create". - Fixed impossible or conflicting instructions in
content-element-types.md- the Bloom list named only four of the six levels, Mermaid edges were required to be clickable (Mermaid cannot do this), a graph example asked for mouse-wheel zoom inside an embedded page, examples hard-coded 500 px iframe placeholders, and an unclosed code block swallowed the MicroSim example.
Version 1.10 Features:
- Mascot placement rules single-sourced - Step 2.4 principle 4 no longer carries its own copy of the Chapter 1 self-introduction pattern or the mascot frequency numbers. Both now live in the canonical
$BK_HOME/skills/book-installer/references/mascot-placement-rules.md, which every skill in the library references instead of restating. This ends the drift that had left conflicting per-chapter counts in two different placement tables. - Version tracked in frontmatter - as
metadata.ibook.version, undermetadata:rather than a bareversion:key, which strict packaging validation would reject.
Version 1.09 Features:
- BREAKING: CIS-driven elaboration budget - Per-concept word count and non-text-element requirements are no longer a flat chapter-wide target ("3000-5000 words, 4-6 non-text elements"). Each concept now gets its own word-count range and minimum non-text-element requirement computed from its Concept Impact Score (CIS), read from the
CIS Scorecolumn thatbook-chapter-generatorv1.0.0+ writes into each chapter's "Concepts Covered" table. Foundational, high-impact concepts get real elaboration (worked examples, diagrams); narrow, low-impact concepts get efficient, brief treatment. See "Elaboration Budget" (Step 2.3b) below. Requires chapters generated bybook-chapter-generatorv1.0.0+ (table format) and alearning-graph.jsonfromlearning-graph-generatorv1.06+ (hasnode.cis).
Version 0.09 Features:
- Mascot self-introduction in Chapter 1 - When the project CONTENT-GENERATION-GUIDE.md defines a pedagogical mascot, the FIRST mascot admonition in Chapter 1 must be a self-introduction that names the mascot and enumerates each pose-role it will play across the book. The pattern is defined once for the whole library in
mascot-placement-rules.md(see Step 2.4, principle 4)