dsh-nerd-mode 0.4.6 → 0.5.2

package/skills/humanizer/agents/openai.yaml

@@ -1,4 +1,4 @@
-interface:
-  display_name: "Humanizer"
-  short_description: "Make AI-written text sound like the writer"
-  default_prompt: "Use $humanizer to rewrite this text in my voice without changing its facts."
+interface:
+  display_name: "Humanizer"
+  short_description: "Make AI-written text sound like the writer"
+  default_prompt: "Use $humanizer to rewrite this text in my voice without changing its facts."

package/skills/humanizer/scripts/validate-package.py

@@ -1,146 +1,146 @@
-#!/usr/bin/env python3
-"""Check Humanizer's package files without external dependencies."""
-
-from __future__ import annotations
-
-import json
-import re
-from pathlib import Path
-
-
-ROOT = Path(__file__).resolve().parent.parent
-
-
-def read_package_file(path: Path) -> str:
-    try:
-        return path.read_text(encoding="utf-8")
-    except OSError as error:
-        raise SystemExit(f"Cannot read {path.relative_to(ROOT)}: {error}")
-
-
-SKILL_PATH = ROOT / "SKILL.md"
-SKILL = read_package_file(SKILL_PATH)
-README = read_package_file(ROOT / "README.md")
-CHANGELOG = read_package_file(ROOT / "CHANGELOG.md")
-try:
-    PLUGIN = json.loads(read_package_file(ROOT / ".claude-plugin" / "plugin.json"))
-except json.JSONDecodeError as error:
-    raise SystemExit(f"Fix the JSON in .claude-plugin/plugin.json: {error}")
-try:
-    CURSOR_PLUGIN = json.loads(
-        read_package_file(ROOT / ".cursor-plugin" / "plugin.json")
-    )
-except json.JSONDecodeError as error:
-    raise SystemExit(f"Fix the JSON in .cursor-plugin/plugin.json: {error}")
-
-
-def require_match(match: re.Match[str] | None, message: str) -> re.Match[str]:
-    if match is None:
-        raise SystemExit(message)
-    return match
-
-
-yaml_metadata = require_match(
-    re.match(r"\A---\n(.*?)\n---\n", SKILL, re.DOTALL),
-    "SKILL.md must begin with YAML metadata",
-).group(1)
-
-for unsupported_field in ("version:", "compatibility:", "allowed-tools:"):
-    if re.search(rf"(?m)^{re.escape(unsupported_field)}", yaml_metadata):
-        raise SystemExit(f"Remove unsupported YAML field: {unsupported_field[:-1]}")
-
-skill_version = require_match(
-    re.search(r'(?m)^\s+version:\s*["\']?([0-9]+\.[0-9]+\.[0-9]+)["\']?\s*$', yaml_metadata),
-    "Add metadata.version to SKILL.md as a three-part version",
-).group(1)
-changelog_version = require_match(
-    re.search(r"(?m)^## ([0-9]+\.[0-9]+\.[0-9]+)$", CHANGELOG),
-    "Add a version heading to CHANGELOG.md",
-).group(1)
-
-package_versions = {
-    skill_version,
-    changelog_version,
-    str(PLUGIN.get("version", "")),
-    str(CURSOR_PLUGIN.get("version", "")),
-}
-if len(package_versions) != 1:
-    raise SystemExit(
-        f"Use one package version in all files: {sorted(package_versions)}"
-    )
-
-skill_files = {path.relative_to(ROOT) for path in ROOT.rglob("SKILL.md")}
-if SKILL_PATH.is_symlink() or skill_files != {Path("SKILL.md")}:
-    raise SystemExit("Keep one regular SKILL.md at the repo root")
-if PLUGIN.get("skills") != ["./"]:
-    raise SystemExit("Point the Claude plugin skill loader at the repo root")
-if CURSOR_PLUGIN.get("name") != "humanizer":
-    raise SystemExit("Set the Cursor plugin name to humanizer")
-if "skills" in CURSOR_PLUGIN:
-    raise SystemExit("Omit skills from the Cursor plugin so it loads the root SKILL.md")
-
-skill_description = " ".join(
-    require_match(
-        re.search(r"(?m)^description: \|\n((?:  .*\n)+)", yaml_metadata + "\n"),
-        "Write the SKILL.md description as an indented block",
-    ).group(1).split()
-)
-MARKETPLACE = json.loads(read_package_file(ROOT / ".claude-plugin" / "marketplace.json"))
-package_descriptions = {
-    str(PLUGIN.get("description", "")),
-    str(CURSOR_PLUGIN.get("description", "")),
-    *(str(plugin.get("description", "")) for plugin in MARKETPLACE.get("plugins", [])),
-}
-if len(package_descriptions) != 1 or not skill_description.startswith(
-    next(iter(package_descriptions))
-):
-    raise SystemExit(
-        "Use the first sentence of the SKILL.md description in every plugin manifest: "
-        f"{sorted(package_descriptions)}"
-    )
-
-skill_patterns = dict(
-    (int(number), name)
-    for number, name in re.findall(r"(?m)^### ([0-9]+)\. (.+)$", SKILL)
-)
-pattern_numbers = list(skill_patterns)
-pattern_count = len(pattern_numbers)
-if pattern_count == 0 or pattern_numbers != list(range(1, pattern_count + 1)):
-    raise SystemExit(f"Number SKILL.md patterns from 1 upward without gaps: {pattern_numbers}")
-
-readme_patterns = dict(
-    (int(number), name)
-    for number, name in re.findall(r"(?m)^\| ([0-9]+) \| \*\*(.+?)\*\*", README)
-)
-if sorted(readme_patterns) != pattern_numbers:
-    raise SystemExit(
-        f"List patterns 1 through {pattern_count} once each in the README tables: {sorted(readme_patterns)}"
-    )
-renamed = [
-    f"{number}: {readme_patterns[number]!r} should be {name!r}"
-    for number, name in skill_patterns.items()
-    if readme_patterns[number] != name
-]
-if renamed:
-    raise SystemExit("Match the README pattern names to SKILL.md: " + "; ".join(renamed))
-if f"## The {pattern_count} patterns" not in README:
-    raise SystemExit(f"Title the README pattern section 'The {pattern_count} patterns'")
-
-# A renumber can leave a section reference pointing at the wrong pattern or at
-# nothing. CHANGELOG.md keeps the numbers each release used, so read SKILL.md only.
-skill_references = sorted({int(number) for number in re.findall(r"§([0-9]+)", SKILL)})
-missing_patterns = [
-    number for number in skill_references if not 1 <= number <= pattern_count
-]
-if missing_patterns:
-    raise SystemExit(
-        f"Point every SKILL.md section reference at a pattern from 1 to "
-        f"{pattern_count}: {missing_patterns}"
-    )
-
-# Every word of SKILL.md is read on each use, so the budget is in words.
-skill_words = len(SKILL.split())
-if skill_words > 5500:
-    raise SystemExit(f"Keep SKILL.md at 5,500 words or fewer; it has {skill_words}")
-
-print(f"Humanizer package v{skill_version} is valid")
+#!/usr/bin/env python3
+"""Check Humanizer's package files without external dependencies."""
+
+from __future__ import annotations
+
+import json
+import re
+from pathlib import Path
+
+
+ROOT = Path(__file__).resolve().parent.parent
+
+
+def read_package_file(path: Path) -> str:
+    try:
+        return path.read_text(encoding="utf-8")
+    except OSError as error:
+        raise SystemExit(f"Cannot read {path.relative_to(ROOT)}: {error}")
+
+
+SKILL_PATH = ROOT / "SKILL.md"
+SKILL = read_package_file(SKILL_PATH)
+README = read_package_file(ROOT / "README.md")
+CHANGELOG = read_package_file(ROOT / "CHANGELOG.md")
+try:
+    PLUGIN = json.loads(read_package_file(ROOT / ".claude-plugin" / "plugin.json"))
+except json.JSONDecodeError as error:
+    raise SystemExit(f"Fix the JSON in .claude-plugin/plugin.json: {error}")
+try:
+    CURSOR_PLUGIN = json.loads(
+        read_package_file(ROOT / ".cursor-plugin" / "plugin.json")
+    )
+except json.JSONDecodeError as error:
+    raise SystemExit(f"Fix the JSON in .cursor-plugin/plugin.json: {error}")
+
+
+def require_match(match: re.Match[str] | None, message: str) -> re.Match[str]:
+    if match is None:
+        raise SystemExit(message)
+    return match
+
+
+yaml_metadata = require_match(
+    re.match(r"\A---\n(.*?)\n---\n", SKILL, re.DOTALL),
+    "SKILL.md must begin with YAML metadata",
+).group(1)
+
+for unsupported_field in ("version:", "compatibility:", "allowed-tools:"):
+    if re.search(rf"(?m)^{re.escape(unsupported_field)}", yaml_metadata):
+        raise SystemExit(f"Remove unsupported YAML field: {unsupported_field[:-1]}")
+
+skill_version = require_match(
+    re.search(r'(?m)^\s+version:\s*["\']?([0-9]+\.[0-9]+\.[0-9]+)["\']?\s*$', yaml_metadata),
+    "Add metadata.version to SKILL.md as a three-part version",
+).group(1)
+changelog_version = require_match(
+    re.search(r"(?m)^## ([0-9]+\.[0-9]+\.[0-9]+)$", CHANGELOG),
+    "Add a version heading to CHANGELOG.md",
+).group(1)
+
+package_versions = {
+    skill_version,
+    changelog_version,
+    str(PLUGIN.get("version", "")),
+    str(CURSOR_PLUGIN.get("version", "")),
+}
+if len(package_versions) != 1:
+    raise SystemExit(
+        f"Use one package version in all files: {sorted(package_versions)}"
+    )
+
+skill_files = {path.relative_to(ROOT) for path in ROOT.rglob("SKILL.md")}
+if SKILL_PATH.is_symlink() or skill_files != {Path("SKILL.md")}:
+    raise SystemExit("Keep one regular SKILL.md at the repo root")
+if PLUGIN.get("skills") != ["./"]:
+    raise SystemExit("Point the Claude plugin skill loader at the repo root")
+if CURSOR_PLUGIN.get("name") != "humanizer":
+    raise SystemExit("Set the Cursor plugin name to humanizer")
+if "skills" in CURSOR_PLUGIN:
+    raise SystemExit("Omit skills from the Cursor plugin so it loads the root SKILL.md")
+
+skill_description = " ".join(
+    require_match(
+        re.search(r"(?m)^description: \|\n((?:  .*\n)+)", yaml_metadata + "\n"),
+        "Write the SKILL.md description as an indented block",
+    ).group(1).split()
+)
+MARKETPLACE = json.loads(read_package_file(ROOT / ".claude-plugin" / "marketplace.json"))
+package_descriptions = {
+    str(PLUGIN.get("description", "")),
+    str(CURSOR_PLUGIN.get("description", "")),
+    *(str(plugin.get("description", "")) for plugin in MARKETPLACE.get("plugins", [])),
+}
+if len(package_descriptions) != 1 or not skill_description.startswith(
+    next(iter(package_descriptions))
+):
+    raise SystemExit(
+        "Use the first sentence of the SKILL.md description in every plugin manifest: "
+        f"{sorted(package_descriptions)}"
+    )
+
+skill_patterns = dict(
+    (int(number), name)
+    for number, name in re.findall(r"(?m)^### ([0-9]+)\. (.+)$", SKILL)
+)
+pattern_numbers = list(skill_patterns)
+pattern_count = len(pattern_numbers)
+if pattern_count == 0 or pattern_numbers != list(range(1, pattern_count + 1)):
+    raise SystemExit(f"Number SKILL.md patterns from 1 upward without gaps: {pattern_numbers}")
+
+readme_patterns = dict(
+    (int(number), name)
+    for number, name in re.findall(r"(?m)^\| ([0-9]+) \| \*\*(.+?)\*\*", README)
+)
+if sorted(readme_patterns) != pattern_numbers:
+    raise SystemExit(
+        f"List patterns 1 through {pattern_count} once each in the README tables: {sorted(readme_patterns)}"
+    )
+renamed = [
+    f"{number}: {readme_patterns[number]!r} should be {name!r}"
+    for number, name in skill_patterns.items()
+    if readme_patterns[number] != name
+]
+if renamed:
+    raise SystemExit("Match the README pattern names to SKILL.md: " + "; ".join(renamed))
+if f"## The {pattern_count} patterns" not in README:
+    raise SystemExit(f"Title the README pattern section 'The {pattern_count} patterns'")
+
+# A renumber can leave a section reference pointing at the wrong pattern or at
+# nothing. CHANGELOG.md keeps the numbers each release used, so read SKILL.md only.
+skill_references = sorted({int(number) for number in re.findall(r"§([0-9]+)", SKILL)})
+missing_patterns = [
+    number for number in skill_references if not 1 <= number <= pattern_count
+]
+if missing_patterns:
+    raise SystemExit(
+        f"Point every SKILL.md section reference at a pattern from 1 to "
+        f"{pattern_count}: {missing_patterns}"
+    )
+
+# Every word of SKILL.md is read on each use, so the budget is in words.
+skill_words = len(SKILL.split())
+if skill_words > 5500:
+    raise SystemExit(f"Keep SKILL.md at 5,500 words or fewer; it has {skill_words}")
+
+print(f"Humanizer package v{skill_version} is valid")

package/skills/study/SKILL.md

@@ -1,78 +1,81 @@
----
-name: study
-description: "[v0.4.6] Teach one concept or help complete one task, using the supplied material as scope and defaulting to chat output."
-argument-hint: "<concept or task>"
----
-# Study
-
-Teach one concept or help complete one task. This skill owns the standards for teaching and lecture writing, including lecture drafts. `study-plus` owns tracked sessions, tracker updates, the choice of lecture paths, and book assembly. Never load or call `study-plus` from this skill.
-
-The upper layer selects the path for multiple independent concepts. Follow that path and do not ask again.
-
-## Teach accurately
-
-- Use supplied material to set the scope, title, chapter boundaries, and order. Treat it as a reference, not as truth. Check important or uncertain claims when needed, prefer accuracy, and flag differences.
-- Use an approved graph or supplied material by default. Do not research the web for every lecture.
-- Cover the major ideas, relationships, and qualifications. Explain intuition first, then terminology, then formal detail. Choose a structure that fits the content. Do not force a fixed section template.
-- Use examples and analogies when they help. State where an analogy stops matching. Include exam topics only when they matter to the request.
-- Use tables or figures when they clarify the material. Define every mathematical symbol and its role. In derivations, justify each meaningful step, explain the result, and check algebra, arithmetic, assumptions, and units.
-- Write math in LaTeX. Put one expression in each math span. Keep prose outside math spans.
-- Give every symbol a noun and a role. Define each symbol once, where the reader first meets it: inside the sentence for an inline mention, or in one line directly above the first display formula that uses it. Keep the line in the formula's reading order, and switch to one symbol per line when a definition needs an explanatory clause. Do not restate a symbol that an earlier sentence or definition line already made clear.
-- When four or more symbols each appear in two or more formulas, put a short table of just those symbols before the first formula. The table is a lookup aid, not a definition, so it does not remove any symbol from the line above a formula.
-- Compare three or more numbers in a short table before the first formula.
-- State bounds as verbal comparisons. Explain each formula once in plain words without symbols.
-- Use “you” for the reader’s actions and “we” for shared work. Avoid generic “one” and passive wording when the reader acts. Correct misleading terminology at first use.
-- Justify each meaningful derivation step before showing it. Put one meaningful move on each display line, and split long equality chains where the object changes. Mark approximations and assumptions.
-- Prefer verbs to abstract nouns. Open each paragraph with its claim, then support it. State each fact once. Avoid rhetorical questions that ask the reader to infer a conclusion. Keep lecture questions sparse and purposeful.
-- Name headings for their content. Number them only when useful.
-- For a task, produce the requested usable artifact and explain the important steps. Do not expand it into a project or return an avoidable partial result.
-
-## Teach at the given level
-
-The upper layer may give a teaching brief of up to three lines: `Goal`, `Background`, and `Teaching level`. Treat it as context for writing, and never read `graph.md` or any other tracker file to obtain it.
-
-`standard` uses every rule in this file unchanged. A missing `Teaching level` line means `standard`.
-
-For `beginner`:
-
-- Split the lecture into 3 to 7 numbered steps when the concept takes more than one move.
-- Explain each term at first use, including terms that `standard` assumes, such as a prerequisite idea or a notation convention.
-- Add one worked example per step when an example helps.
-- Never add a prerequisite recap block. No level adds one.
-
-For `advanced`:
-
-- Use one pass without numbered steps, unless the derivation needs them.
-- Skip the intuition for an idea only when the `Background` line names that idea as known. Start from the formal statement.
-- Use at most one example per idea. Keep the qualifications and edge cases that matter for the stated goal.
-
-Accuracy rules outrank the level. No level removes a symbol definition, a justification for a derivation step, a stated assumption or approximation, or a bound. No level adds filler, repeated explanation, or a section the concept does not need. The level affects the lecture only.
-
-For a one-off request with no graph, derive the level from the brief the upper layer supplies and from the request and the supplied material. A brief from an upper layer is final: never ask again for a goal or a background it leaves out. A bare topic, or "I want to learn X", states no goal. When no brief arrives and neither the request nor the supplied material states a goal or a background, ask one combined question before teaching: what the learner wants to reach and whether they have met the topic before. State the derived level in one line, then teach. Write no file.
-
-## Format the answer
-
-- For one concept, use an H1 named for the concept.
-- For a one-off multi-concept book, use ordinary Markdown, not a fenced block. Use an H1 for the book or topic, H2 headings for Chapters, and H3 headings for concept Sections. Name each Section after its concept. Follow the supplied book order when it exists.
-- For a task, title the requested artifact or task. Explain the reason for non-obvious steps.
-- Give the complete answer when it fits. If a platform limit forces continuation, state which chapters are covered and which remain, then wait.
-- Do not quiz, grade, score, or log. You may offer similar practice, but do not impose it.
-
-## Write lecture drafts
-
-The upper layer may hand you an approved concept graph, the relevant supplied material, the teaching brief, and one destination file per concept. Then write one complete draft per concept at the given level, under the same writing standard. A draft is prepared teaching material, not teaching.
-
-- Cover the concept completely at the given level: the teaching explanation, its relationships, and useful examples. Write no assessment questions, no answers, and no grading criteria. Actual questions stay unseen.
-- Write only the destinations you are given, and one Chapter per batch when the upper layer splits the work. Never invent a path, and never read or write `graph.md`, `state.md`, `log.md`, `plan.md`, or any other tracker file.
-- Frontmatter is exactly `status: draft` and the concept number. Add no date. The body opens with an H1 named for the concept.
-- Preparation is not teaching. Change no learner state and append nothing to the log.
-- Keep a valid existing draft or dated lecture at a destination. Report it instead of overwriting. Leave an occupied or unrecognized target alone and report it.
-- Report the paths you wrote and every destination you refused. Print no draft in chat.
-
-## Files and figures
-
-Default to chat output. If the learner asks to save a lecture or other artifact, save it to the requested path and show the same content in chat when practical.
-
-When an SVG would materially clarify a relationship, create it by default. When the upper layer scopes a Course, write `study/<course>/diagrams/<name>.svg`. When the guide runs alone, write `diagrams/<name>.svg` and create no folder under `study/`. Load `diagram` for its visual authoring rules, but use this study-specific path instead of its generic default. Sanitize `course` and `name` as single lowercase kebab-case path segments with no slashes or dot segments. If either is unclear, choose a safe fallback. Before writing, confirm the resolved parent stays inside the intended `diagrams/` root and the target is not `study/<course>/graph.md`, `state.md`, `log.md`, or `plan.md`. Compute plotted points rather than placing them by eye. Before replacing an SVG with the same name, copy the old file to `<name>.svg.bak`, replacing any older backup.
-
-Never read or write `study/<course>/graph.md`, `state.md`, `log.md`, or `plan.md`. Do not read or change tracker state. Study-plus owns the choice of lecture paths and the automatic lecture save during tracked sessions. Study may read or write ordinary artifacts, including lectures, drafts, and figures, at paths the user or the upper layer gives it.
+---
+name: study
+description: "[v0.5.2] Teach one concept or help complete one task, using the supplied material as scope and defaulting to chat output."
+argument-hint: "<concept or task>"
+---
+# Study
+
+Teach one concept or help complete one task. This skill owns the standards for teaching and lecture writing, including lecture drafts. `study-plus` owns tracked sessions, tracker updates, the choice of lecture paths, and book assembly. Never load or call `study-plus` from this skill.
+
+The upper layer selects the path for multiple independent concepts. Follow that path and do not ask again.
+
+## Teach accurately
+
+- Use supplied material to set the scope, title, chapter boundaries, and order. Treat it as a reference, not as truth. Check important or uncertain claims when needed, prefer accuracy, and flag differences.
+- Use an approved graph or supplied material by default. Do not research the web for every lecture.
+- Cover the major ideas, relationships, and qualifications. Start from one concrete instance when the concept has one, then explain the intuition, the terminology, and the formal detail. Choose a structure that fits the content. Do not force a fixed section template.
+- Use examples and analogies when they help. State where an analogy stops matching. Include exam topics only when they matter to the request.
+- Use a figure when the concept has a process, a flow, or a relation between parts; use a table when the reader must compare values. Put the figure next to the paragraph it explains, with one caption sentence that states the point, and do not restate the figure in prose. When no honest figure exists, stay with prose and do not invent one. Define every mathematical symbol and its role. In derivations, justify each meaningful step, explain the result, and check algebra, arithmetic, assumptions, and units.
+- Write math in LaTeX. Put one expression in each math span. Keep prose outside math spans.
+- Give every symbol a noun and a role. Define each symbol once, where the reader first meets it: inside the sentence for an inline mention, or in one line directly above the first display formula that uses it. Keep the line in the formula's reading order, and switch to one symbol per line when a definition needs an explanatory clause. Do not restate a symbol that an earlier sentence or definition line already made clear.
+- When four or more symbols each appear in two or more formulas, put a short table of just those symbols before the first formula. The table is a lookup aid, not a definition, so it does not remove any symbol from the line above a formula.
+- Compare three or more numbers in a short table before the first formula.
+- State bounds as verbal comparisons. Explain each formula once in plain words without symbols.
+- Use “you” for the reader’s actions and “we” for shared work. Avoid generic “one” and passive wording when the reader acts. Correct misleading terminology at first use.
+- Justify each meaningful derivation step before showing it. Put one meaningful move on each display line, and split long equality chains where the object changes. Mark approximations and assumptions.
+- Prefer verbs to abstract nouns. Open each paragraph with its claim, then support it. State each fact once. Number the moves when the concept takes more than one; the level may drop the numbers. Delete asides, restatements, and footnotes that only decorate. Avoid rhetorical questions that ask the reader to infer a conclusion. Keep lecture questions sparse and purposeful.
+- Name headings for their content. Number them only when useful.
+- For a task, produce the requested usable artifact and explain the important steps. Do not expand it into a project or return an avoidable partial result.
+
+## Teach at the given level
+
+The upper layer may give a teaching brief of up to three lines: `Goal`, `Background`, and `Teaching level`. Treat it as context for writing, and never read `graph.md` or any other tracker file to obtain it.
+
+`standard` uses every rule in this file unchanged. A missing `Teaching level` line means `standard`.
+
+For `beginner`:
+
+- Split the lecture into 3 to 7 numbered steps when the concept takes more than one move.
+- Explain each term at first use, including terms that `standard` assumes, such as a prerequisite idea or a notation convention.
+- Add one worked example per step when an example helps.
+- Never add a prerequisite recap block. No level adds one.
+
+For `advanced`:
+
+- Use one pass without numbered steps, unless the derivation needs them.
+- Skip the intuition and the concrete opening for an idea only when the `Background` line names that idea as known. Start from the formal statement.
+- Use at most one example per idea. Keep the qualifications and edge cases that matter for the stated goal.
+- Keep the figures. A position figure or a relation figure locates the idea; it does not count as an example.
+
+Accuracy rules outrank the level. No level removes a symbol definition, a justification for a derivation step, a stated assumption or approximation, or a bound. No level adds filler, repeated explanation, or a section the concept does not need. The level affects the lecture only.
+
+For a one-off request with no graph, derive the level from the brief the upper layer supplies and from the request and the supplied material. A brief from an upper layer is final: never ask again for a goal or a background it leaves out. A bare topic, or "I want to learn X", states no goal. When no brief arrives and neither the request nor the supplied material states a goal or a background, ask one combined question before teaching: what the learner wants to reach and whether they have met the topic before. State the derived level in one line, then teach. Write no file.
+
+## Format the answer
+
+- For one concept, use an H1 named for the concept.
+- For a one-off multi-concept book, use ordinary Markdown, not a fenced block. Use an H1 for the book or topic, H2 headings for Chapters, and H3 headings for concept Sections. Name each Section after its concept. Follow the supplied book order when it exists.
+- When the answer has chapters, open each chapter with one figure that shows its concepts and how they connect. Place it in the first section of the chapter. A single-concept answer gets no chapter figure.
+- For a task, title the requested artifact or task. Explain the reason for non-obvious steps.
+- Give the complete answer when it fits. If a platform limit forces continuation, state which chapters are covered and which remain, then wait.
+- Do not quiz, grade, score, or log. You may offer similar practice, but do not impose it.
+
+## Write lecture drafts
+
+The upper layer may hand you an approved concept graph, the relevant supplied material, the teaching brief, and one destination file per concept. Then write one complete draft per concept at the given level, under the same writing standard. A draft is prepared teaching material, not teaching.
+
+- Cover the concept completely at the given level: the teaching explanation, its relationships, and useful examples. Write no assessment questions, no answers, and no grading criteria. Actual questions stay unseen.
+- In a chapter batch, the first draft of the chapter opens with the chapter figure, written under the Course's `diagrams/`; the destination list covers lectures only. Later drafts in the chapter do not repeat it.
+- Write only the destinations you are given, and one Chapter per batch when the upper layer splits the work. Never invent a path, and never read or write `graph.md`, `state.md`, `log.md`, `plan.md`, or any other tracker file.
+- Frontmatter is exactly `status: draft` and the concept number. Add no date. The body opens with an H1 named for the concept.
+- Preparation is not teaching. Change no learner state and append nothing to the log.
+- Keep a valid existing draft or dated lecture at a destination. Report it instead of overwriting. Leave an occupied or unrecognized target alone and report it.
+- Report the paths you wrote and every destination you refused. Print no draft in chat.
+
+## Files and figures
+
+Default to chat output. If the learner asks to save a lecture or other artifact, save it to the requested path and show the same content in chat when practical.
+
+When the upper layer scopes a Course, write a figure to `study/<course>/diagrams/<name>.svg`. When the guide runs alone, write `diagrams/<name>.svg` and create no folder under `study/`. Load `diagram` for its visual authoring rules, but use this study-specific path instead of its generic default. Sanitize `course` and `name` as single lowercase kebab-case path segments with no slashes or dot segments. If either is unclear, choose a safe fallback. Before writing, confirm the resolved parent stays inside the intended `diagrams/` root and the target is not `study/<course>/graph.md`, `state.md`, `log.md`, or `plan.md`. Compute plotted points rather than placing them by eye. Before replacing an SVG with the same name, copy the old file to `<name>.svg.bak`, replacing any older backup.
+
+Never read or write `study/<course>/graph.md`, `state.md`, `log.md`, or `plan.md`. Do not read or change tracker state. Study-plus owns the choice of lecture paths and the automatic lecture save during tracked sessions. Study may read or write ordinary artifacts, including lectures, drafts, and figures, at paths the user or the upper layer gives it.