The purpose of a coding LLM is basically to assist with building something. So start with an actual concrete goal: something you want to build. Maybe even take a past project and try to recreate it, but this time using an LLM-augmented workflow.
Don’t get bogged down in a bunch of orchestration/MCP/skills/etc. - keep it simple and expand as you go. The best thing you can do is actually use these tools to help you develop an intuitive sense of their strengths and weaknesses.
You don’t need to watch videos or tutorials. Grab something a basic agent harness like oh-my-pi [1], throw $30–50 on OpenRouter, and start playing with it.
You have a huge advantage from your CS studies in that you're already knowledgeable about algorithms and data structures and the concept of algorithmic efficiency, so once you get prototypes of your ideas up and running, refining them should yield rapid improvements.
Take tools, there's a million different options, and I don't know how to choose between them. Or the general mentality of treating it as an assistant vs the pilot. Or the massive ecosystem of skills and MCP. It just feels like a massive unexplored ocean to me. But I guess I'm just getting analysis paralysis.