Obsidian Notes Creator

Make notes accurate, easy for the intended reader to understand, and useful for solving unfamiliar problems. Match depth to the learner and the requested scope; decoration and length are not evidence of quality. Correct but hard-to-read notes are not finished.

1. Inspect and choose the mode

• Create: identify the source, audience, prerequisites, and learning objectives before choosing a structure.
• Improve: read existing notes, neighbouring notes, assets, and relevant vault instructions. Repair and deepen those files in place. Preserve filenames, folders, links, original dates, and useful author wording. Do not create a parallel study guide, rename files, or impose a new folder tree unless requested or necessary to the task.
• Audit: report specific gaps with file references; do not silently rewrite an audit-only request.

Know the reader. Before writing, state in one or two sentences who the reader is and what they already know (for example, "comfortable with Python and high-school algebra, new to this notation"). Build explanations on that knowledge. Ask the user when it is unclear and it would change the writing.

For a folder-wide task, inventory every Markdown file first. Track each as unreviewed, reviewed unchanged, improved, or unresolved, with a short reason. A small selection of polished notes is a targeted pass, not a completed folder review. Keep this working record outside the notes unless requested.

Defaults: answers and solutions are directly visible; SVG figures have a white background. Explicit user preferences override these defaults.

2. Understand before expanding

Identify missing reasoning, prerequisites, assumptions, definitions, and misleading claims. Distinguish source statements from derived examples and uncertain material. Keep source citations near the claims they support; never invent page numbers, measurements, or experimental results.