obsidian-refactor-lecturelisted

## Overview The skill turns a large set of lecture notes into a structured knowledge graph: - the **original lecture** becomes a "table of contents" — sections are replaced with a short summary + `[[wikilink]]`; - **extracted concepts** are created as separate notes named `<Discipline> – <Concept>.md`; - if a discipline MOC exists, it's updated with links to the new notes (no such MOC is guaranteed to exist right now — see "Lecture notes format" below). **Limit:** no more than **3 sets of notes** per run. If the user names more, ask which three to process now — the rest go in a follow-up run. --- ## Base rules Vault structure, tag taxonomy, frontmatter, file names — in `.claude/rules/`: `vault-struct.md`, `tags.md` (the "Structural tags" section), `note-types-frontmatter.md`, `file-naming.md`. --- ## Lecture notes format A lecture file follows the pattern `<NN>. <Discipline> лекция <YYYY-MM-DD>.md`, filed under `02. Сферы/03. Образование/02. Конспекты/`, and contains: ```yaml --- tags: - university # real lecture notes use this, not #lecture — check what's already on sibling notes before picking up: "[[02. Сферы]]" # observed real notes point straight at 02. Сферы, not at a per-discipline MOC aliases: [] down: [] links: [] other: [] --- ``` There's no confirmed per-discipline MOC or `discipline:` field in the current vault — only one real lecture note was available to check, and it links `up` straight to `02. Сферы`. If a `## Discipline` MOC turns out to exis