wonglisted

# Wong — end-of-day learning guidebook (formerly daily-log) Turn a full day of Claude Code work (across every session and repo) into a single dated markdown file written as a **teaching guide**, so the user can genuinely learn the work: re-implement the code by hand, understand *why* each decision was made, and be able to explain how it works because they actually understand it. The output is NOT a changelog. It is a **beginner's textbook** — written so simply and conversationally that someone with *no* software background could read it top to bottom and understand both what was done and why. Every technical term is defined in plain language the first time it appears; code stays technical but is wrapped in plain-English explanation. Depth and the "why" matter more than completeness of trivia. See the full **Writing style — REQUIRED** rules in step 4. ## Step 0. Read the effort level from the command The user may pass an effort level as the first argument: **light**, **medium**, or **heavy**. If none is given, default to **heavy**. (They may also pass a date; a `YYYY-MM-DD` token is the date, a light/medium/heavy token is the effort. Either order, both optional. e.g. `/wong medium`, `/wong light 2026-06-25`.) Effort controls token usage — it scales BOTH the digest size (via `--effort` on the collector) AND how much you do while writing: - **light** — cheapest. Document only the **top 2–3** pieces of work. Do **not** run `git show`/extra file reads; rely on the digest +