prepdojo-logginglisted

# PrepDojo Logging 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. This skill is generic: every path, tag, and taxonomy comes from the user's own `prepdojo.json`, never from this file. ## Find the vault, read the config (once per session) All personalization lives in `prepdojo.json` at the user's vault root, written by PrepDojo's `generate.py`. Locate it ONCE per session, in this order, stopping at the first success: 1. **Pointer file.** Read `~/.claude/prepdojo-vault.json` (shape: `{"vault_path": "..."}`). If `<vault_path>/prepdojo.json` exists and parses, use it. 2. **Working folder.** Check the current working folder for `prepdojo.json`, then each parent up to three levels. 3. **Shallow search.** Search the session's accessible folders (connected/mounted folders, uploaded folders) for `prepdojo.json`, depth-limited (e.g. `find <root> -maxdepth 3 -name prepdojo.json -not -path '*/.*'`). Exactly one hit: use it silently. Several hits: ask the user which vault they mean. 4. **Ask.** If nothing is found, ask the user where their vault is — they may need to connect the folder to the session. Never guess, and never create a `prepdojo.json` yourself; only `generate.py` writes it. After locating via steps 2–4, write the pointer file (create `~/.clau