Watch the 3Blue1Brown YouTube series on machine learning. Understand how these things work and that they are not magical all-knowing answer machines or even anything intelligent - they are next-most-likely-word predictors. That's all. Demistify and keep that in mind with everything you do afterwards.
I presume you don't want to drop thousands of dollars on video cards so pay Sam/Dario your 20 bucks a month.
Ask the LLM to build things you have already done before. You need to know the correct answer so you can evaluate the solution the LLM provides you.
Start with single-file scripts you have written, you can do this in just the ChatGPT or Claude web interface. Start with a vague prompt which doesn't specify many constraints or details. See what they get right and wrong. Try being much more specific and detailed. Make it ask you questions about what you want before it starts work.
Try the small/old/dumb model with no thinking and try the big/new/smart model with full thinking and notice the difference in capability.
Learn to setup an agent software in a sandbox of some kind. I prefer Pi in a Podman container, with only access to the project directory, but there are a million options out there these days.
From this agent software, ask for explanations on a codebase you already know. Again the purpose is to know the answer in advance so you can evaluate the response provided. Ask it to just tell you some answers. Ask it to give you a code flow and reference to read more yourself.
Build something larger, like a program across multiple files. Again try being vague and being specific, see the difference in what it spits out.
Use it to troubleshoot a problem you have solved, like your favourite bug, and also just a boring regular bug. Try different types of issue.
Learn to create an AGENTS.md for a project or SKILL.md for reusable instructions anywhere, but don't stuff it full of useless nonsense you think the model needs. Build it from experience of only what the thing gets wrong.
Some people say you can ask LLMs to write their own md files, but imo these things generate way too much text. You could ask it to do that as a starting point then trim it down to remove all the extra unnecessary verbose crap.
Through all this, try asking it the same thing multiple times in different new sessions. Notice the answers vary. Sometimes it gets it wrong and sometimes right. Same question, same model, same everything, different answer.
Notice you need to know the right answer to evaluate the response. In situations where you don't know the answer yourself, hopefully you've seen enough wrong answers now to not trust it. Use these things to guide your own investigation, like the exercise above where you asked for code flow and references to read yourself. I think of this as "LLM as search engine, not answer engine".
That seems to be 95% of what people use these things for. This set of skills would have been useful for the last 18 months and seems to be the way the industry momentum is moving at the moment.