Notes and review

kk organizes a class into three layers of notes: post-class notes for each session, unit notes that combine sessions by teaching unit, and an exam review page for a specific exam. All notes are local Markdown files.

Post-class notes

When you stop recording, kk generates notes for that session by default and shows a brief notice when they are ready. You can also select “Regenerate” on the session page, or turn off automatic generation under “Post-class notes” in Settings.

  • They include a title, key points, concept explanations, what the teacher stressed (including your bookmarks), questions to review and a glossary.
  • After sessions are merged or a recording is resumed, the notes update from the full content.
  • Notes are plain Markdown that you can edit in kk, with changes saved automatically. Notes you have edited are never overwritten: regenerating saves the new version separately so you can compare.

Unit notes

Post-class notes are one per session. To review by teaching unit, turn on “Organize by unit” for a course: kk combines the sessions and slides that belong to one unit into a formal unit note. The switch is per course, and with it off the library behaves exactly as before.

  1. Turn on Organize by unit. Choose “Units” in the “Units / List” switch at the top right of the course page, or use the course’s right-click menu.
  2. Import a syllabus (optional). Drag the course syllabus onto the course page. kk identifies the units (title, date range, matching chapters) and exams (date, weight, units covered) and first shows a confirmation table; rename, merge and reorder, then confirm to apply it. Without a syllabus you can create units by hand.
  3. Assign recordings. Recordings are assigned to units automatically, and you can adjust that with “Unit” in a recording’s right-click menu (multiple units allowed). While recording, the unit capsule on the live page lets you say which unit today covers.
  4. Generate the notes. Update the notes from the unit card. A card’s status is one of: no notes yet, up to date, needs update, or has recordings awaiting confirmation. Changing which unit a recording belongs to marks affected units “Needs update” instead of rewriting them automatically, so you do not spend allowance needlessly; the notice bar offers “Update” and “Undo”.

What a unit note contains

  • The teacher’s exam hints: only what the teacher actually said, with the session and minute.
  • A body organized by course type: for computational courses, “Method”, “Worked examples” and “Common mistakes” by problem type; for conceptual courses, key points by topic. Formulas are typeset from LaTeX and code is syntax highlighted.
  • Practice problems (answers collapsed by default), exam-ready summaries and a glossary.
  • Sources are clearly separated. What was taught in class is written directly; examples reconstructed from the teacher’s spoken explanation are marked “〔Reconstructed from the lecture〕”; content in the slides but not covered in class is marked “〔Slides〕”; assigned reading is marked “〔Reading〕”; and things you need to know that appear in neither are marked “〔Added〕”. kk does not invent exam information on the teacher’s behalf.
  • After writing, kk recomputes the examples and answers once more; anything that may be wrong is listed in a red callout at the top of the page for you to check.

Unit notes can be edited in the app: select the pencil at the right of the title row to edit the whole page. Changes are kept as a draft until you select “Done”. Once written back, the note counts as edited by you and later updates will not overwrite it.

Exam review page

Each exam gets its own review page to go through a day or two before. It is built from the already written and verified notes of the units in the exam’s scope, not from each session’s raw transcript, so it agrees with the unit notes and uses less allowance. Set up the exam first in the syllabus confirmation table or on the course page.

Using kk with Obsidian

kk’s project folder is an ordinary folder, so you can choose an existing Obsidian vault as the project folder, and the two do not interfere:

  • kk keeps its own data in a dot-prefixed .kk/ directory that Obsidian does not show, and never reads, writes or deletes .obsidian/.
  • File names are unique across the vault and look like date course · 笔记.md, for example 2026-11-03 CIS 2107 · 笔记.md, so [[links]] work reliably.
  • Note properties use Obsidian’s tags, aliases and date; kk’s own fields carry a kk- prefix. [[wikilinks]], ![[embeds]], tags and callouts are preserved as written.
  • Existing folders in the vault are not treated as courses; their Markdown files can still be opened and edited and are never written to automatically. You can turn one into a category by hand.
  • If a file is changed in Obsidian or by a cloud drive, kk reloads it. Before writing, kk checks whether the file was changed externally and, if so, does not overwrite it and saves the new version beside it instead.

Last updated: November 15, 2026