@erclx/canon 5.52.0 → 5.53.0

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [5.53.0](https://github.com/erclx/canon/compare/v5.52.0...v5.53.0) (2026-10-21)
+
+
+### Features
+
+* **products:** drop teach, slides, and demo for a teach-craft skill ([#2588](https://github.com/erclx/canon/issues/2588)) ([bb1930f](https://github.com/erclx/canon/commit/bb1930fa8911ae637eddadbaabfa498e6e7f769d))
+
 ## [5.52.0](https://github.com/erclx/canon/compare/v5.51.0...v5.52.0) (2026-10-21)
 
 

package/README.md

@@ -72,8 +72,6 @@ Each domain has a canonical source in this repo and a thin install or sync CLI o
 | Governance     | Coding and authoring rules that load into a Claude session when a matching path is edited                               | Installed per project by `canon gov install`, refreshed by sync |
 | Tooling stacks | Golden configs, seeds, and a reference per framework                                                                    | Laid down by `canon init`, reconciled by `canon tooling sync`   |
 | Design system  | Ships a `DESIGN.md` intent format pointing at your stylesheet for values, a skill that drafts one, and a render command | `canon design render`                                           |
-| Slides         | A folder of HTML slides per deck, drawn in the project's tokens and rebuilt as editable shapes                          | `canon slides render` writes PowerPoint                         |
-| Teach          | Lessons, sources, and a glossary in one workspace, rendered to a small site                                             | `canon teach`                                                   |
 | Canvas         | Pages of HTML frames on a local pan and zoom surface, each frame drawn with the project's tokens                        | `canon canvas serve`                                            |
 | Transcripts    | A YouTube transcript with metadata frontmatter                                                                          | `canon transcripts <url>` writes it into any repo               |
 | Sandbox        | Scenario scaffolds that provision an isolated project state for verifying each domain flow                              | `canon sandbox`                                                 |
@@ -93,7 +91,7 @@ The workflow this toolkit ships is the workflow that built it. Several Claude Co
  <img src="demos/agent-view-light/demo.gif" alt="The canon landing page scrolling from the dispatch section to the branch graph, three workers and a planner on disjoint file sets with the pull request each opened">
 </picture>
 
-That recording is the landing page's own `dispatch` and `workers` sections, driven by `canon demo run` against a local build. The branch graph beside the pull request numbers is authored rather than read, because nothing on a build machine records which files four sessions held.
+That recording is the landing page's own `dispatch` and `workers` sections, driven through a browser against a local build. The branch graph beside the pull request numbers is authored rather than read, because nothing on a build machine records which files four sessions held.
 
 ## Documentation
 
@@ -182,7 +180,6 @@ Each domain carries an entry written for someone maintaining the toolkit rather
 - [Governance rules](canon/context/surfaces/governance.md)
 - [Tooling stacks](canon/context/surfaces/tooling.md)
 - [Design system](canon/context/features/design.md)
-- [Slides](canon/context/features/slides.md)
 - [Transcripts](canon/context/features/transcripts.md)
 - [Sandbox](canon/context/development/sandbox.md)
 

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "canon",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
-  "version": "5.52.0",
+  "version": "5.53.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/canon-cli/SKILL.md

@@ -45,14 +45,11 @@ Each verb here has a skill that owns the job. Load the skill rather than driving
 | Job                                          | Verb                | Skill                       |
 | -------------------------------------------- | ------------------- | --------------------------- |
 | Render the design system                     | `canon design`      | `canon:draw-figure`         |
-| Render a slide deck                          | `canon slides`      | `canon:make-deck`           |
 | Render an HTML source to a PNG               | `canon capture`     | `canon:design-identity`     |
 | Serve a directory and print the link         | `canon serve`       | none                        |
-| Record a running app                         | `canon demo`        | `canon:script-screencast`   |
 | Report one computed property across routes   | `canon inventory`   | `canon:target-check`        |
 | Walk a page through interactions and measure | `canon drive`       | `canon:ux-measure`          |
 | Fetch a YouTube transcript                   | `canon transcripts` | `canon:youtube-transcripts` |
-| Open a learning workspace                    | `canon teach`       | `canon:teach-workspace`     |
 | Work on the local canvas                     | `canon canvas`      | `canon:canvas-board`        |
 
 ## Session and ship

package/claude/skills/context-fold/REQUIREMENT.md

@@ -29,7 +29,6 @@ The context entries describe the repository the session opened with. An entry ke
 ## Out of scope
 
 - Marking outcomes, sweeping receipts, and archiving a task, which `task-complete` owns
-- Landing a teach promotion page, which `teach-workspace` owns
 - Creating or declining a task file, which `task-board` owns
 - Public-facing docs, which `docs-sync` owns
 - Regenerating the context catalog, which a commit hook owns

package/claude/skills/design-taste/references/kinds.md

@@ -47,7 +47,6 @@ Documentation, articles, reference pages, learning material. The reader arrived
 ## Kinds this file does not cover
 
 - **Transactional flows** such as checkout, sign-up and settings are read as application UI. Their distinctive rules, state coverage and error recovery, sit in the `ui` governance rules.
-- **Presentation surfaces** such as slide decks are drafted by `make-deck`, which carries the deck's design rules. Take the layer ordering and the floor from the body and the rest from it.
 - **Terminal and text-mode surfaces** have no layout engine and their own color rules, stated where the writing surface is decided rather than here.
 
 A read naming any of the three above takes the body's rules and says it has no per-kind guidance, naming the surface that governs it. A read naming a kind this file does not list at all says so rather than borrowing the nearest section.

package/claude/skills/draw-figure/REQUIREMENT.md

@@ -7,13 +7,13 @@ description: Why a figure decides between Mermaid, an architecture view, and fre
 
 ## Gap
 
-Without this skill, a session asked for a figure takes the first path it thinks of. A graph gets SVG coordinates nobody checked against a render, and a subject that is not a graph gets forced through Mermaid. In a teach lesson the renderer cannot load the hand font, so labels clip, and a check reading the standalone image passes them.
+Without this skill, a session asked for a figure takes the first path it thinks of. A graph gets SVG coordinates nobody checked against a render, and a subject that is not a graph gets forced through Mermaid.
 
 Asked to refresh one architecture view, it redraws every view beside it. It judges the source and calls the figure verified, though a valid source can render a picture asserting something false. Mermaid's theme writes literal hex values, so the figure stops re-coloring when the page switches palette.
 
 ## Must
 
-- The figure clears the standard's earn-its-place bar, and its path follows whether the subject reduces to a graph, with a teach lesson drawn freehand whatever its shape
+- The figure clears the standard's earn-its-place bar, and its path follows whether the subject reduces to a graph
 - An architecture view is drawn from its named source signal in `flowchart` or `sequenceDiagram`, and only the view the request names changes
 - The Mermaid render uses the hand-drawn look and the figure font stack, with every literal color rewritten to the host's custom property
 - The render is read back against what the figure means to say, and a figure bound for a rendered page is verified by a capture inside that page
@@ -31,5 +31,4 @@ Asked to refresh one architecture view, it redraws every view beside it. It judg
 
 - Mermaid's layout, budgets, and label rules inside the fence, which the mermaid standard owns
 - A UI screen mockup, and design tokens or the visual system, which `canvas-board` owns
-- Which lesson needs a figure and where it sits, which `teach-workspace` owns
 - Implementation detail behind an architecture view, which the context entry the caption points at owns

package/claude/skills/draw-figure/SKILL.md

@@ -30,12 +30,11 @@ Apply the standard's bar: a relationship, a boundary, a path, or a before-and-af
 
 Take the first that matches, and state which path was picked and why in one sentence:
 
-1. **A teach lesson**, a page in a learning workspace's `lessons/` folder: the hand-drawn path, any shape. The renderer cannot load the lesson's hand font, so Mermaid labels measure narrow and clip.
-2. **An architecture view**, meaning the request names system context, components, request flow, data pipeline, or deployment: the architecture set, then the Mermaid path.
-3. **Graph-shaped**, meaning the relationship, boundary, or path is already what a flowchart or sequence diagram expresses: the Mermaid path.
-4. **Anything else**, a spatial or physical arrangement no flowchart reduces to: the hand-drawn path.
+1. **An architecture view**, meaning the request names system context, components, request flow, data pipeline, or deployment: the architecture set, then the Mermaid path.
+2. **Graph-shaped**, meaning the relationship, boundary, or path is already what a flowchart or sequence diagram expresses: the Mermaid path.
+3. **Anything else**, a spatial or physical arrangement no flowchart reduces to: the hand-drawn path.
 
-The standard states this as a render-first policy rather than a ban on any tool-exported drawing, so outside a teach lesson a graph-shaped subject always routes through Mermaid even though that is itself an external renderer.
+The standard states this as a render-first policy rather than a ban on any tool-exported drawing, so a graph-shaped subject always routes through Mermaid even though that is itself an external renderer.
 
 ## Step 4: draw
 

package/claude/skills/draw-figure/references/figures.md

@@ -39,7 +39,6 @@ Route a graph-shaped subject, one whose relationship, boundary, or path a flowch
 
 - Reserve freehand inline SVG, plain shapes and lines authored in the markup, for a subject that is not graph-shaped
 - A figure that cannot express its subject through the deterministic path is a worse failure than an inconsistent hand-drawn one, so the hatch stays open
-- Draw a figure in a teach lesson freehand whatever its shape. Its hand font cannot load in the renderer, so Mermaid measures labels in a narrower fallback face and the page clips them.
 - State this as a render-first policy rather than a ban on a tool-exported drawing, since routing through Mermaid is itself running an external tool
 
 ## Wrapping and captioning

package/claude/skills/draw-figure/references/hand-drawn.md

@@ -5,7 +5,7 @@ description: Authoring a freehand SVG, its color and accessibility audit, and th
 
 # Hand-drawn path
 
-`draw-figure` reads this file when Step 3 routes a figure to a freehand drawing: a teach lesson whatever its subject, or a subject no flowchart reduces to.
+`draw-figure` reads this file when Step 3 routes a figure to a freehand drawing, for a subject no flowchart reduces to.
 
 ## Draw
 

package/claude/skills/pick-by-eye/REQUIREMENT.md

@@ -33,4 +33,3 @@ The evidence fails as well. Arms get reported without being rendered or judged,
 - Finding roughness by reading source, which `ux-audit` owns
 - Measuring what a running interface costs to paint, which `ux-measure` owns
 - Listing what to look at on a change already made, which `ui-checklist` owns
-- Scripting a recording of something already built, which `script-screencast` owns

package/claude/skills/pick-by-eye/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pick-by-eye
-description: Drafts several candidates for a decision judged by looking, lays them out side by side as frames on one canvas page, hands the operator the address, takes the pick through the structured question surface, and loops on the pick until they stop. Use when asked to "draft some options", "show me a few versions", "try a few variations", "mock up alternatives", "give me candidates for X", or when a choice is taste rather than correctness. Do NOT use when the request already names the answer and asks for it to be built, which is `plan-feature`. Do NOT use to read source for roughness, which is `ux-audit`, to measure what a running interface costs to paint, which is `ux-measure`, to write what to look at on a change already made, which is `ui-checklist`, or to script a recording, which is `script-screencast`.
+description: Drafts several candidates for a decision judged by looking, lays them out side by side as frames on one canvas page, hands the operator the address, takes the pick through the structured question surface, and loops on the pick until they stop. Use when asked to "draft some options", "show me a few versions", "try a few variations", "mock up alternatives", "give me candidates for X", or when a choice is taste rather than correctness. Do NOT use when the request already names the answer and asks for it to be built, which is `plan-feature`. Do NOT use to read source for roughness, which is `ux-audit`, to measure what a running interface costs to paint, which is `ux-measure`, or to write what to look at on a change already made, which is `ui-checklist`.
 metadata:
   family: decide
 ---

package/claude/skills/teach-craft/REQUIREMENT.md

@@ -0,0 +1,30 @@
+---
+name: teach-craft
+description: Scope boundary for the teaching judgment a session carries, and why it ships as knowledge rather than as a workspace
+---
+
+# Teach craft requirement
+
+## Gap
+
+Without this skill, a session asked to teach explains and calls a smooth reply a lesson. It teaches from recall, picks topics from the subject's order rather than the learner's errors, and asks nothing about what they know.
+
+Its quizzes leak the answer through option length or position, and nothing tests the learner later, so fluency passes for retention.
+
+## Must
+
+- Carry retrieval, spacing, interleaving, and placement as rules a session applies before picking what to teach next
+- Ask the learner's starting point and read the subject from sources, saying which claims rest on recall
+- State quiz design that leaks no answer, and pair a quiz with a teach-back
+- Hold that the wrong answer itself is what the next session places from
+
+## Must not
+
+- Name a verb, a folder, a markup contract, or a stylesheet, since the skill produces nothing of its own
+- Fire on a request to answer one question
+- Go unloaded when a session teaches across exchanges, since a craft body only its author types reaches no lesson
+
+## Out of scope
+
+- Where a lesson is stored or how it renders, which belongs to whatever surface the session writes to
+- A cited source ledger for the practice family, which is a follow-on task

package/claude/skills/teach-craft/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: teach-craft
+description: Carries the judgment for teaching a subject so it sticks, being retrieval over review, spacing, interleaving, placing the learner just past what they can do unaided, quiz design that leaks no answer, the teach-back, and what makes a lesson worth returning to. Use before teaching a subject over more than one exchange, when writing a quiz, a lesson, or a study plan, or when asked "teach me X", "quiz me on this", "how should I learn X", or "is this a good quiz question". Do NOT use to answer one question, which is an ordinary reply, or to write project documentation, which belongs to the surface owning that document.
+metadata:
+  family: answer
+---
+
+# Teach craft
+
+A session asked to teach explains, and a smooth explanation reads as a lesson learned. It is fluency, which decays within days. This skill carries what turns teaching into retention: test before telling, space the returns, and grade only what the learner produced unaided.
+
+It produces nothing of its own. The lesson lands wherever the session already writes, being the conversation, a file, or a page.
+
+## References
+
+- `${CLAUDE_SKILL_DIR}/references/pedagogy.md`: fluency against storage strength, retrieval practice, spacing and its ladder, interleaving, where to place the learner, and where difficulty helps
+- `${CLAUDE_SKILL_DIR}/references/lesson-craft.md`: restraint, quiz design, the teach-back, and what makes a lesson worth returning to
+
+Read `pedagogy.md` before picking what to teach next, and `lesson-craft.md` before writing a quiz or a lesson.
+
+## Before teaching
+
+- Ask what the learner already knows rather than assuming it. Difficulty with no floor under it teaches nobody.
+- Read the subject from sources rather than from recall, and say which claims rest on recall where no source was reachable
+- Open a returning learner on retrieval of what they got wrong last time, before anything new
+
+## While teaching
+
+- Place each step just past what the learner can do unaided, from what they got wrong rather than from the subject's own order
+- Carry a quiz and a teach-back, since recognition and production fail differently
+- Record the wrong answer itself rather than a count, since the next session places the learner from the misconception
+
+## Excuses and rebuttals
+
+| Excuse                                    | Rebuttal                                                                                     |
+| ----------------------------------------- | -------------------------------------------------------------------------------------------- |
+| They followed the explanation, so move on | Following is fluency. Advance on a retrieval the learner passed unaided.                     |
+| Review the last lesson before testing it  | Review rebuilds the fluency the test would have measured. Test first, then fill what missed. |
+| The answer is obvious from the options    | Then the distractors are not misconceptions anyone holds. Rewrite them.                      |

package/claude/skills/teach-craft/references/lesson-craft.md

@@ -0,0 +1,52 @@
+---
+title: Lesson craft reference
+description: Restraint, quiz design, teach back, and what makes a lesson worth returning to
+---
+
+# Lesson craft reference
+
+Judgment rather than shape. This file covers what makes a lesson worth opening twice, whatever surface it renders on.
+
+## Contents
+
+- [Restraint](#restraint)
+- [Quiz design](#quiz-design)
+- [Teach back](#teach-back)
+- [What makes a lesson worth returning to](#what-makes-a-lesson-worth-returning-to)
+
+## Restraint
+
+Every element competes with the material for attention.
+
+- Cut any decoration that carries no information
+- Use at most one accent color, reserved for the thing the learner acts on
+- Do not animate anything the learner did not trigger
+- Prefer whitespace over rules and boxes to separate sections
+
+## Quiz design
+
+The quiz is the retrieval, so a leak in its construction turns it into a reading test.
+
+- Write every option to the same length, in words and in characters. A longer option reads as the considered one.
+- Rotate the correct option's slot by question number, so question one puts it first, question two second, and so on. An author varying position by judgment settles on the first slot.
+- Make each wrong option a misconception someone actually holds. An obviously wrong option removes itself and shrinks the question.
+- Write one feedback block per question, covering the correct option and why each distractor fails, saying why rather than whether
+- Give feedback after the attempt, never alongside the question
+
+One feedback block reads as an explanation where a block per option reads as four verdicts, and only the explanation names what separates a wrong option from the answer. Name the correct option in the feedback text, since it is what a learner reads to find out whether they were right.
+
+## Teach back
+
+A quiz is recognition and a teach-back is production, which is the form retrieval practice prefers. Carry both: the quiz places the learner against options someone could hold, and the teach-back is where the learner finds out what they cannot say without help.
+
+- Ask for an explanation to a named audience rather than for an answer. Telling a non-programmer why a lazy quantifier is not an optional one has a floor, and "explain lazy quantifiers" has none.
+- Ask about the thing the lesson was for, not a detail beside it. A teach-back on a footnote tests attention rather than the material.
+- Carry a self-check, hidden until the learner opens it, listing what a complete explanation covers. A learner with no session in the room otherwise cannot grade the ask, and hidden leaks nothing.
+- Write the self-check as what the explanation has to cover rather than as the explanation itself. A model answer is read instead of produced, which turns the block back into reading.
+
+## What makes a lesson worth returning to
+
+- The worked example is complete. A learner returning for the example finds the whole thing rather than a fragment they have to reconstruct.
+- The lesson states what it assumes. A returning reader can tell in one line whether they are in the right place.
+- The hard part is named as the hard part. Material that flattens everything to one difficulty gives a returning reader nothing to navigate by.
+- Nothing depends on the session it was written in. A lesson referring to what was discussed is unreadable a week later.

package/claude/skills/{teach-workspace → teach-craft}/references/pedagogy.md

@@ -5,7 +5,7 @@ description: Fluency against storage strength, retrieval practice, spacing, inte
 
 # Pedagogy reference
 
-The rules a lesson is built from. Read this before picking what to teach next, not while writing the markup.
+The rules a lesson is built from. Read this before picking what to teach next.
 
 ## Fluency is not storage strength
 
@@ -43,8 +43,7 @@ The same total time spread across days beats the same time in one sitting. Forge
 
 The ladder is 1, 3, 7, 16, and 35 days. A topic retrieved unaided moves up a rung and a miss drops it back one, held inside the ladder at either end, so a topic the learner keeps missing stays on the shortest gap rather than restarting a sequence.
 
-- Do not compute a date from that ladder by hand. `canon teach list <topic> --json` reports both dates resolved for every item, a number to copy rather than a rule to apply.
-- An author told to widen a gap still picks it by judgment, the same reason quiz option order is drawn by a verb rather than stated here
+- Apply the ladder as written rather than picking a gap by judgment, since an author told to widen a gap settles on whatever feels right
 
 ## Interleaving
 
@@ -78,4 +77,13 @@ Parametric recall is confident where it is wrong, and a learner cannot audit it.
 - Read the subject from sources before teaching, and record each one with its link
 - Mark any claim resting on recall as resting on recall, in the lesson itself
 - List a source found and not opened as a lead, and never cite it
-- Choose which sources to read by the ladder under `### Choosing sources` in the teach standard, which also rules out the learner's own work as proof of a general claim
+- Rest each general claim on the highest rung of the ladder below that covers it
+- Never take the learner's own projects, or material specific to one employer, as proof of a general claim. Either may appear as a worked application labeled with whose it is.
+
+The ladder runs in three rungs, highest first.
+
+1. Documentation or a specification published by whoever owns the subject
+2. A canonical work on the subject, such as the standard text, a reference book, or a primary paper
+3. Other material, such as a tutorial, a course, or a post, and only for a claim the first two rungs do not cover
+
+A subject nobody owns, such as a mathematical topic or a craft, has no first rung, so its list starts at the second. Record a third-rung source with the claim it covers and why no higher rung does, since that reason is what a later session checks the choice against.

package/docs/agents/audits.md

@@ -77,7 +77,6 @@ The placement entry runs pinned to `--backend off`, so its tally stays comparabl
 | `records-plans`      | `canon records validate plans`      | Plan records against their shape                                                   | Reports        |
 | `records-groundwork` | `canon records validate groundwork` | Groundwork folders against their shape                                             | Reports        |
 | `records-intake`     | `canon records validate intake`     | Intake folders against their shape                                                 | Reports        |
-| `records-teach`      | `canon records validate teach`      | Teach records against their shape                                                  | Reports        |
 | `comments`           | `canon comments scan`               | Comment density by language and kind, and `TODO`, `FIXME`, `HACK`, `XXX`           | Reports        |
 | `test-order`         | `canon gov test-order`              | Implementations that reached branch history before their test                      | Reports        |
 | `secrets`            | `canon secrets scan`                | Credential-shaped values in the shipped tree                                       | Gates          |

package/docs/target/migrations.md

@@ -130,7 +130,7 @@ From the registry the walk reports `historyUnavailable`, so check both paths by
 | `git-commit`      | `commit`, `versioning`                                        |
 | `git-pr`          | `pr`, `publish`                                               |
 | `markdown-craft`  | `markdown`                                                    |
-| `teach-workspace` | `glossary`, `teach`                                           |
+| `teach-workspace` | `glossary`, `teach` <!-- canon-keep-retired -->               |
 | `plan-groundwork` | `groundwork`, `groundwork-spikes`                             |
 | `plan-intake`     | `intake`                                                      |
 | `plan-feature`    | `plan`, `plan-lifecycle`                                      |
@@ -148,6 +148,15 @@ The wireframes record is retired, and nothing deletes what a project holds.
 - Delete the `@canon/wireframes/index.md` line in your `CLAUDE.md` with the folder. `canon claude sync` does not rewrite it.
 - `canon gov sync` removes `.claude/rules/canon/standards/wireframes.md`
 
+## Keep or delete the retired product files, your call
+
+The learning workspace, the deck renderer, and the app recorder are retired with their verbs and skills, and nothing deletes what a project holds.
+
+- `.canon/teach/` holds rendered HTML that opens as it is, so it needs nothing <!-- canon-keep-retired -->
+- `.canon/slides/` and a `demos/` folder hold sources nothing renders any more, so delete them once nothing cites them <!-- canon-keep-retired -->
+- Replace a `canon:teach-workspace` reference with `canon:teach-craft` by hand, since `canon migrate skill-names` does not rewrite it <!-- canon-keep-retired -->
+- Delete a `canon:make-deck`, `canon:script-screencast`, `canon:record-screencast`, `canon:read-frames`, or `canon:video-craft` reference, since none has a successor <!-- canon-keep-retired -->
+
 ## Move decisions out of a held architecture record, once
 
 The toolkit no longer seeds `canon/ARCHITECTURE.md`, and a held file and its `CLAUDE.md` import stay. Move a trap a session would hit into that domain's `## Gotchas`, then delete the file and its `@canon/ARCHITECTURE.md` line.

package/docs/workflow/parallel-features.md

@@ -32,7 +32,7 @@ Assert the orchestrator role in one warm session with `canon:role-orchestrator`.
 
 - To pick otherwise, rewrite that line as `overridden at execution to <pick>,` plus the measurement, and add one line to the open task's `## Findings`
 
-- `canon records validate plans [plan]` reports a plan breaking its standard, plus `structure` misses that never set the exit, and takes `groundwork`, `intake`, and `teach`
+- `canon records validate plans [plan]` reports a plan breaking its standard, plus `structure` misses that never set the exit, and takes `groundwork` and `intake`
 - `canon records push` and `canon records pull` carry `.canon/` to and from a private repository. See [records](../agents/records.md).
 - `canon records size`, `canon records prune-tmp`, and `canon records stale canonical` report folder size, idle scratch, and releases since the requirements review
 - `canon tasks archive` moves a shipped plan to `.canon/plans/archive/` and retargets the task's `Plan:` line

package/docs/workflow/skill-map-on-request.md

@@ -10,24 +10,15 @@ These skills serve a request rather than a moment. With the [skill map](skill-ma
 
 ## Generate an artifact on demand
 
-| Skill                     | When to use                                                                        |
-| ------------------------- | ---------------------------------------------------------------------------------- |
-| `canon:create-rule`       | A project rule the toolkit does not ship                                           |
-| `canon:create-skill`      | A new `SKILL.md`                                                                   |
-| `canon:write-doc`         | A new `docs/` page, context entry, or `README.md`                                  |
-| `canon:draft-doc`         | Never on purpose. A pointer naming `write-doc` <!-- canon-keep-retired -->         |
-| `canon:plan-ready`        | Finished files a worker should copy                                                |
-| `canon:draft-ready`       | Never on purpose. A pointer naming `plan-ready` <!-- canon-keep-retired -->        |
-| `canon:draw-figure`       | A figure or architecture view inside a doc                                         |
-| `canon:draft-figure`      | Never on purpose. A pointer naming `draw-figure` <!-- canon-keep-retired -->       |
-| `canon:ci-workflow`       | A GitHub Actions workflow file                                                     |
-| `canon:make-deck`         | A deck rendered to editable PowerPoint                                             |
-| `canon:draft-slides`      | Never on purpose. A pointer naming `make-deck` <!-- canon-keep-retired -->         |
-| `canon:script-screencast` | A recording script with beats seeded                                               |
-| `canon:draft-screencast`  | Never on purpose. A pointer naming `script-screencast` <!-- canon-keep-retired --> |
-| `canon:record-screencast` | Recording a screencast draft into a finished mp4                                   |
-| `canon:design-identity`   | A logo mark and social card                                                        |
-| `canon:draft-identity`    | Never on purpose. A pointer naming `design-identity` <!-- canon-keep-retired -->   |
+| Skill                   | When to use                                       |
+| ----------------------- | ------------------------------------------------- |
+| `canon:create-rule`     | A project rule the toolkit does not ship          |
+| `canon:create-skill`    | A new `SKILL.md`                                  |
+| `canon:write-doc`       | A new `docs/` page, context entry, or `README.md` |
+| `canon:plan-ready`      | Finished files a worker should copy               |
+| `canon:draw-figure`     | A figure or architecture view inside a doc        |
+| `canon:ci-workflow`     | A GitHub Actions workflow file                    |
+| `canon:design-identity` | A logo mark and social card                       |
 
 ## Answer a question at any point
 
@@ -35,9 +26,6 @@ These skills serve a request rather than a moment. With the [skill map](skill-ma
 | --------------------------- | ----------------------------------------------------- |
 | `canon:canon-cli`           | To pick a `canon` verb, or learn which can lose edits |
 | `canon:youtube-transcripts` | A video transcript wanted as context                  |
-| `canon:read-frames`         | To read a recorded demo back frame by frame           |
-| `canon:teach-workspace`     | To learn a subject across sessions                    |
+| `canon:teach-craft`         | To teach a subject so it sticks                       |
 | `canon:markdown-craft`      | Before a substantial markdown edit                    |
 | `canon:write-human`         | Before drafting or revising prose                     |
-
-Ask `canon:teach-workspace` to promote a learning workspace's reference pages and glossaries. It proposes a destination per page and waits. An Anthropic-owned subject goes to the wiki, an internal one to the matching context entry, and the rest to the public docs. A project with no wiki folder gets a refusal naming the folder to create.

package/docs/workflow/skill-map.md

@@ -17,19 +17,18 @@ Groups run in the order a project meets them. Every name `canon claude skills li
 
 ## Decide what to build
 
-| Skill                      | When to use                                                                  |
-| -------------------------- | ---------------------------------------------------------------------------- |
-| `canon:plan-intake`        | The input is a pile of findings                                              |
-| `canon:plan-intake-answer` | An intake folder holds unread slots                                          |
-| `canon:backlog-triage`     | The backlog needs pruning                                                    |
-| `canon:plan-groundwork`    | The state is unmeasured and approaches compete                               |
-| `canon:decision-escalate`  | Open decisions turn on your preference                                       |
-| `canon:pick-by-eye`        | The call is taste, wanting candidates side by side                           |
-| `canon:draft-and-pick`     | Never on purpose. A pointer naming `pick-by-eye` <!-- canon-keep-retired --> |
-| `canon:canvas-board`       | A direction should be drawn as editable frames                               |
-| `canon:task-board`         | A decided item needs a file on the board                                     |
-| `canon:plan-feature`       | The approach is settled and needs a plan                                     |
-| `canon:codebase-layout`    | A change adds a file and needs a folder                                      |
+| Skill                      | When to use                                        |
+| -------------------------- | -------------------------------------------------- |
+| `canon:plan-intake`        | The input is a pile of findings                    |
+| `canon:plan-intake-answer` | An intake folder holds unread slots                |
+| `canon:backlog-triage`     | The backlog needs pruning                          |
+| `canon:plan-groundwork`    | The state is unmeasured and approaches compete     |
+| `canon:decision-escalate`  | Open decisions turn on your preference             |
+| `canon:pick-by-eye`        | The call is taste, wanting candidates side by side |
+| `canon:canvas-board`       | A direction should be drawn as editable frames     |
+| `canon:task-board`         | A decided item needs a file on the board           |
+| `canon:plan-feature`       | The approach is settled and needs a plan           |
+| `canon:codebase-layout`    | A change adds a file and needs a folder            |
 
 ## Build the feature
 
@@ -47,7 +46,6 @@ Groups run in the order a project meets them. Every name `canon claude skills li
 | `canon:search-craft`          | Before searching outside the project               |
 | `canon:systematic-debugging`  | A test fails or a bug surfaces                     |
 | `canon:design-taste`          | Drafting or judging an interface                   |
-| `canon:video-craft`           | Before composing or judging a video                |
 | `canon:ui-checklist`          | After a UI change, to list what to check           |
 
 ## Check the work before it leaves the branch

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/canon",
   "type": "module",
-  "version": "5.52.0",
+  "version": "5.53.0",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
   "license": "MIT",
   "bin": {
@@ -54,10 +54,7 @@
     "@preact/signals": "^2.11.3",
     "commander": "^13.1.0",
     "execa": "^9.5.2",
-    "highlight.js": "^11.12.0",
-    "jszip": "^3.10.1",
     "playwright-core": "1.64.1",
-    "pptxgenjs": "^4.0.1",
     "preact": "^11.0.0"
   },
   "devDependencies": {

package/scripts/core/regen-web-previews.ts

@@ -2,19 +2,14 @@
  * Writes `web/public/previews/design-tokens/index.html` and `design.css` by
  * calling `renderDesignDoc` directly, the in-process pattern
  * `regen-web-favicon.ts` already takes rather than spawning a subprocess.
- * Writes `web/public/previews/teach-workspace/` the same way, calling
- * `generateNav` over an isolated copy of one workspace.
  *
- * Both are embedded live in a landing section as an `<iframe>` rather than a
+ * It is embedded live in a landing section as an `<iframe>` rather than a
  * screenshot, since `web/e2e/home.spec.ts` asserts no `<img>` renders inside
  * `<main>`.
  */
-import { cpSync, existsSync, mkdtempSync, readFileSync, rmSync } from 'node:fs'
-import { tmpdir } from 'node:os'
-import { join } from 'node:path'
+import { readFileSync } from 'node:fs'
 import { DESIGN_DOCUMENT } from '@/design/regen'
 import { renderDesignDoc } from '@/design/render'
-import { generateNav } from '@/teach/nav'
 
 const root = new URL('../..', import.meta.url).pathname
 
@@ -33,63 +28,3 @@ if (!/--(color|space|type|radius)-/.test(css)) {
 }
 
 console.log('regen-web-previews: wrote web/public/previews/design-tokens/')
-
-/**
- * The workspace ships alone, on its own isolated nav tree, rather than
- * copied straight out of `.canon/teach/`. That folder cross-links every
- * sibling workspace by relative path, including the operator's own personal
- * study notes, so a copy carrying its live chrome would ship either dead
- * links or a path into content never meant to be public. Regenerating the
- * chrome over a scratch copy holding this one workspace alone is what keeps
- * the jump menus from naming anything else.
- *
- * `.canon/teach/` is gitignored session scratch, per `claude/skills/teach-workspace/references/teach.md`, so
- * it exists on the machine that authored the lesson and nowhere else,
- * including CI. `web/public/previews/teach-workspace/` is therefore the
- * durable copy: committed once the workspace exists, regenerated here as a
- * local convenience when authoring continues, and left untouched by a build
- * that cannot see the source, the same way a target without Playwright still
- * builds against a committed capture.
- */
-const TEACH_SLUG = '04-governance-rule-loading'
-const teachSource = `${root}.canon/teach/${TEACH_SLUG}`
-
-if (!existsSync(teachSource)) {
-  console.log(
-    `regen-web-previews: no workspace at .canon/teach/${TEACH_SLUG} on this machine, leaving the committed web/public/previews/teach-workspace/ as is`,
-  )
-} else {
-  const scratchRoot = mkdtempSync(join(tmpdir(), 'canon-teach-preview-'))
-  try {
-    cpSync(teachSource, join(scratchRoot, '.canon', 'teach', TEACH_SLUG), {
-      recursive: true,
-    })
-
-    const nav = await generateNav(scratchRoot)
-    if (!nav.ok) {
-      console.error(`regen-web-previews: ${nav.message}`)
-      process.exit(1)
-    }
-    if (nav.lessons === 0) {
-      console.error(
-        'regen-web-previews: teach-workspace render carries no lesson, refusing an empty preview',
-      )
-      process.exit(1)
-    }
-
-    const dest = `${root}web/public/previews/teach-workspace`
-    rmSync(dest, { recursive: true, force: true })
-    cpSync(join(scratchRoot, '.canon', 'teach'), dest, {
-      recursive: true,
-      // Only the rendered chrome ships. MISSION.md, RESOURCES.md, and
-      // GLOSSARY.md carry links relative to `.canon/teach/`, which resolve to
-      // nothing once copied under `web/public/`, and nothing links to them
-      // from the rendered pages anyway.
-      filter: (path) => !path.endsWith('.md'),
-    })
-  } finally {
-    rmSync(scratchRoot, { recursive: true, force: true })
-  }
-
-  console.log('regen-web-previews: wrote web/public/previews/teach-workspace/')
-}

package/src/audits/catalog.ts

@@ -496,7 +496,6 @@ const RECORD_KINDS: readonly (readonly [string, Corpus])[] = [
   ['plans', 'per-machine'],
   ['groundwork', 'per-machine'],
   ['intake', 'per-machine'],
-  ['teach', 'per-machine'],
 ]
 
 /**

package/src/browser/engine.ts

@@ -7,9 +7,8 @@
  * The two absences are different states with different remedies. A package that
  * never resolved means the target installed the CLI without the engine, and a
  * binary that was never downloaded means the engine is present and its browser
- * is not. Both were spelled inside `src/demo/` when `demo` was the only command
- * driving a browser, and a second command is what makes them shared rather than
- * local.
+ * is not. Every command driving a browser reads both, so they sit here rather
+ * than beside one caller.
  */
 
 /** Fetches the browser revision the pinned engine expects. */
@@ -72,9 +71,7 @@ export interface KeyboardPage {
  * browser in pointer modality, where that rule does not match, so a reader
  * calling it alone reports every correctly styled element as unstyled.
  *
- * It moved here when `@/driver/probes/focus` became the second call site,
- * matching how the launch-failure split moved out of `src/demo/` once
- * `canon inventory` became the second command driving a browser. One press
+ * It moved here when `@/driver/probes/focus` became the second call site. One press
  * covers the page rather than the element that happens to hold focus, so it
  * survives the blur every reader takes next.
  */

package/src/capture/render.ts

@@ -16,7 +16,7 @@ import { formatStamp, hashSource, stampPath } from '@/capture/stamp'
  * `src/commands/capture.ts` reaches it through a dynamic import so `src/cli.ts`
  * never resolves the engine at startup.
  *
- * It ships, like `@/demo/drive`, `@/inventory/walk`, and `@/driver/drive`.
+ * It ships, like `@/inventory/walk` and `@/driver/drive`.
  * Regenerating this repository's own committed images was the reason it stayed
  * behind, and it was a reason about one caller rather than about the mechanism:
  * a target renders its own generated pages and proves its own fonts resolved,