learning-notes

# Learning notes Use this skill for note-file work the user requests: create notes from available material, clean or review existing notes, or suggest links between related notes. Obsidian may be the user's editor, but this workflow uses ordinary local files and does not require Obsidian or its plugins. ## Boundaries - Own note-file operations only. For tutoring, practice, active recall, or learning progression, follow the user's learning workspace instructions such as `learning-coach`; a learning session does not need to produce a note. - Work only in a workspace and files the user has made available or authorized. Inspect its existing organization and linking style; do not impose folders, templates, frontmatter, tags, or backlinks. - Keep personal notes out of unrelated project repositories and commits. Do not create automatic capture, monitoring, or synchronization. ## Workflow 1. Confirm the requested operation and inspect the relevant notes, source files, and available materials. Use only accessible content. If a PDF or other source cannot be fully inspected with available tools, say so. 2. For a new note, base it on material the user provided or made available. Distinguish the user's explanations, source-derived facts, and any AI-added material where their authorship could be unclear. Do not reconstruct inaccessible conversations or invent source content. 3. For cleanup, improve spelling, grammar, Markdown, whitespace, readability, and nonsemantic organization while preserving meaning, personal voice, reasoning, uncertainty, questions, and learning progress. If asked only to review, do not edit. 4. For conceptual review, point to the claim in question, explain the concern, and suggest a correction. Do not silently replace the user's explanation. Request approval before adding substantial conceptual material beyond the requested source, replacing a core explanation, removing important material, or meaningfully restructuring an existing note. Make requested nonsemantic corrections directly. 5. When useful, inspect related source code and compare it with the note. Report inconsistencies and suggest note updates. Do not change source code just because it was inspected, and never claim code ran unless you actually ran it. 6. Suggest only relevant note links, with a short reason, following the workspace's existing convention. Avoid speculative or excessive links. Markdown, source code, Mermaid, and other materials may be handled with available local tools. Do not build format-specific infrastructure. Be clear about what you could not inspect or verify. ## Completion Briefly report what changed, conceptual concerns, useful connections, and anything you could not verify. Omit categories that do not apply.