lc-loggerlisted

# LC Logger Log solved LeetCode problems (and other interview-prep work) into the user's Obsidian vault, where a Dataview dashboard aggregates them. The user's priority is zero-friction logging: a bare URL means "log this for today" — don't ask questions unless something is truly ambiguous. ## Where things live The Obsidian vault is the user's connected folder. Inside it: - Daily notes: `@@DAILY_NOTES_FOLDER@@/@@DATE_FORMAT@@.md` - Daily note template: `@@DAILY_NOTE_TEMPLATE@@` - Dashboard (never edit when logging): `@@DASHBOARD_PATH@@` ## Entry format Entries are plain bullets (no checkboxes — unchecked boxes are treated as placeholders and ignored by the dashboard) under the `@@PREP_HEADING@@` heading: ``` - LC #<number> <Canonical Title> · <@@DIFFICULTIES_PIPE@@> · <topic> #@@TAG_LC@@ ``` Example: `- LC #200 Number of Islands · Medium · bfs/dfs #@@TAG_LC@@` The ` · ` separators matter — the dashboard splits on them (problem · difficulty · topic). **Topic must be one of** (lowercase, exact strings, so dashboard grouping stays consistent): @@TOPICS_INLINE@@ Rules for topics — these keep the dashboard's grouping and the user's QuickAdd dropdown consistent: - Always lowercase. - Never invent a topic string outside this list. If the problem's natural tag isn't in the list (union find, trie, monotonic stack, math...), offer the closest taxonomy matches in the topic question and include the unmapped tag as an option too — let the user decide; their choice may legitima