teachlisted

The user wants structured learning across multiple sessions — not a one-off explanation. ## Before you write anything ### 1. Pick a learning project folder Never treat the user's open thread folder, default chat folder, or git project as the teaching workspace. **Required layout:** `<default-chat-folder>/bigbud-learn/<topic-slug>/` Example: if the default chat folder is `~/Documents` and the topic is budgeting, every file goes under `~/Documents/bigbud-learn/personal-budgeting/` — **not** `~/Documents/MISSION.md`. - `<default-chat-folder>` is set in **bigbud Settings → File Access → default chat folder**. - bigbud injects the resolved paths when this skill runs — treat that runtime block as authoritative. - Derive `<topic-slug>` from the topic (e.g. `personal-budgeting`, `beginner-photography`). - **Create the `<topic-slug>` folder first**, then write files inside it. - Each subject gets its own `<topic-slug>` folder so projects never overwrite each other. - If the user names a different dedicated folder, use that instead. - If a project folder already has `MISSION.md` or `lessons/`, treat it as a **resume**. **Never write teaching files at these locations:** - The default chat folder root (`MISSION.md` directly in Documents is wrong) - `bigbud-learn/` without a `<topic-slug>` subfolder - A directory containing `.git`, unless the user explicitly asks to learn inside that repo - Home, Desktop, or other non-dedicated locations If runtime context lists **misplaced teach