← ClaudeAtlas

coursebooklisted

Write, audit and publish bilingual (FR/EN) course and workshop manuals as a single self-contained HTML file served from GitHub Pages — the format used by 3DVIZ and AI_GEN_NARRATIVES. Use when authoring a new course manual, workshop handbook, technical documentation for students, or a companion reference page; when adding chapters, figures, diagrams, exercises, FAQ entries or a glossary to an existing one; when checking FR/EN consistency; when building a downloadable starter project folder; or when setting up the repo, the audit script and Pages deployment. Covers the language-switching contract, client-side search, cumulative year bands, figure slots for screenshots taken later, print stylesheet, deterministic ZIP archives, and the writing conventions that keep a technical manual true as tools change.
urbandronedesign/coursebook · ★ 0 · Code & Development · score 72
Install: claude install-skill urbandronedesign/coursebook
# Coursebook Produce a course manual that is **one HTML file**: bilingual, searchable, printable, and readable from a USB key with no network. No build step, no dependencies, no framework. A student gets a link; a teacher gets a file that still opens in five years. This skill is the generalised form of two working manuals — `3DVIZ` (SketchUp/Rhino → Twinmotion) and `AI_GEN_NARRATIVES` (generative film production). Follow it and a third course will match them without re-deciding anything. ## Why one file Every requirement of a course document points the same way. Students read on phones at 1 a.m. and on lab machines with no admin rights. A workshop happens in a room with broken wifi. A colleague wants to fork it. A manual has to outlive the toolchain that produced it. A static-site generator satisfies none of these: it needs installing, breaks on version drift, and dies when its theme is abandoned. So: **one `.html` file, inline CSS, inline JS, no external requests.** The cost is that the file gets large (600 KB is normal) and you edit it with scripts rather than by hand. That trade is correct — take it and stop revisiting it. ## Workflow Work in this order. Each phase assumes the previous one is settled; going backwards is what produces incoherent manuals. ### 1 · Settle the frame before writing a word Answer these five, in writing, before touching HTML. They are cheap now and expensive later. | Question | Why it decides the structure | |---|---| | **What can the re