Chapter Artifact Skill

ACC never pre-authors artifacts. The conductor generates them at runtime, in the learner's workspace, from the code it just wrote. This skill holds the rules and the templates so every artifact looks and reads the same across courses.

Files:

• references/conventions.md: the rules. File rules, visual tokens, fixed section order for the chapter page and the summary page, content rules, and a checklist.
• templates/chapter.html.tmpl: skeleton for one chapter page.
• templates/summary.html.tmpl: skeleton for the lesson summary page.

Who uses this and when

The course-conductor, at runtime. After a chapter's verification command passes, the conductor:

1. Reads artifact_conventions_path (the absolute path of references/conventions.md, returned by nextChapter).
2. Copies the shape of templates/chapter.html.tmpl, fills every {{ placeholder }}, and removes the template comments.
3. Writes the result to artifact_path (<workspace>/artifacts/NN-<id>.html).
4. Calls verifyChapter. The MCP records the artifact path in state when the file exists.

After the e2e gate, the conductor does the same with templates/summary.html.tmpl and writes summary_artifact_path (<workspace>/artifacts/summary.html).

Lesson authors, at validation time. Open a generated artifact next to the conventions and check the "Checklist" part. A page that fails the checklist means the chapter brief or the tests need work, not the template.

Anyone reviewing an artifact. Run the checklist. The most common defects: snippets rewritten instead of copied, a generic diagram instead of this chapter's flow, test names invented instead of read from the test files.

Rules

• templates/chapter.html.tmpl is the chapter page. templates/summary.html.tmpl is the lesson summary page.
• Read references/conventions.md before you write or judge a page. Every rule lives there.