- new standing rule: put explanations directly into NN-topic.js, not
just chat; /tmp verification is fine but conclusions must land in files
- replace stiff '锚点' wording with plainer phrasing (核心一句 etc.)
- include user's own softening of a few rule phrasings
- teach the underlying mechanism, not a bare rule; lead with the anchor
sentence and let rules fall out as consequences
- worked example: arrow body & return anchored on '=> expects an
expression' (user corrected an earlier {-first draft)
- prefer running code to show the real error/output
- flat single-file structure: NN-topic.js per topic (concepts as
comments + demo + exercises in one file), replacing the old
NN-topic/ folder with separate notes.md + practice.js
- 00-concepts/ cross-topic notes (mistakes log, call-forms,
value-vs-reference, shortcircuit bash-vs-js)
- move quokka_playground.js from repo root into js_notes/
- add project CLAUDE.md
Jaydon