One thing to focus on is teaching the skill to onboarding yourself into a new project. As an example, one part of that skill that I've learned from my current employer: It is actually socially acceptable to say "Hi, I've been working on $ticket recently and don't have a specific question but I feel rather lost. Could I grab 30 minutes on your calendar and you walk me through how SaltStack actually gets data values and turns them into resources and I take notes and ask questions?". For a long time, I would instead either:
A) Try to learn this by doing, which usually involved being very frustrated, taking 3x as long, and writing really quite poor-quality code. I only had the cognitive space to think about making the bare minimum change to accomplish the immediate goal, so I couldn't practice the habit of "do a small refactor to make the change easy, then make the easy change."
B) Ask for good tutorial documentation on the subject matter, which might not exist, especially if the code lives outside of a popular framework.
C) Ask differently-phrased questions that led me to get feedback from a previous employer that I was "trying to understand the universe", which led me to focus on strategy A.
Knowing that I can get walkthroughs, especially of business logic or code that lives outside a framework, is really hugely impactful. (side note: if you've wondered why people reach for frameworks while you think they are overcomplicated, this one reason why)
There's probably a whole blog post I would write with the goal of expanding a new-project-joiner's vocabulary of questions that is socially reasonable to ask.