learn

# MasterMind — Learn The invokable form of `~/.mastermind/engineering/core/agent-loop.md` → "Learn the stack before you build." Topic/task: **$ARGUMENTS**. Goal: reach genuine, *current* understanding — enough to build to standard — fast, and cheap on context. ## 1. Detect what's actually used Read `package.json`/lockfile, configs, and representative source to see the exact stack (framework + **versions**, styling, state, data, test runner) and the team's conventions. Installed versions matter — APIs drift, so learn the version that's actually here. ## 2. Map the skill-tree Use the relevant **roadmap.sh** role/topic map as the checklist of what matters and to spot your gaps. Don't learn the whole tree — learn the branch the task touches. ## 3. Learn to current standards Read the **primary docs** for the specific APIs the task needs (verify against the installed version) and skim one battle-tested example (the field's `curriculum.md` lists them). Prefer primary sources; never rely on stale memory (the field's `learning-sources.md`). ## 4. Ground it in this codebase Grep for how the pattern is already used here and match it. Consistency beats novelty. ## 5. Grill your assumptions before you build The costly bugs come from assumptions you never checked. Before committing code: - **List what you believe** about the APIs you'll use (behavior, signatures, return values, limits, versions, edge cases) — specifically ("`getFile` streams any size" — true?). - **Answer from the...