How to use claude code

Claude Code has shipped a bunch of updates lately. Here are the ones I think actually matter — no fluff.

It now runs on Opus 4.8

The new version dropped at the end of May. Same price, but noticeably more reliable.

The biggest difference is that it's more honest. AI used to write code, feel great about it, and stay quiet about the bugs. This version actually tells you when it's unsure, and pushes back when a plan doesn't make sense instead of just plowing ahead. When you let it run on its own for a while, that matters more than any benchmark.

The scores went up too, of course — it's better at coding and math than the last version.

It can take on bigger jobs: Dynamic Workflows

This is a new feature. In short: for really big tasks, it splits the work into hundreds of small pieces and tackles them at the same time.

How big? It can take a whole project — hundreds of thousands of lines — and rewrite it in a different language, start to finish. That's the kind of job you wouldn't have trusted to an AI before. Now it's worth a shot. Just don't use it for small fixes; that's overkill.

Skills: stop teaching it the same thing over and over

Skills are basically pre-written instructions. Once one is set up, Claude knows how to handle a type of task without you explaining it from scratch every time.

A lot of people use Claude Code and never touch this, which is a shame. The most popular ones:

• find-skills — finds and installs other skills. Usually the first thing people add.
• frontend-design — for web design. Makes interfaces look good and less obviously "AI-made."
• superpowers — keeps you on a disciplined workflow: write the tests first, then the feature. Good for projects where quality matters.
• Document skills (PDF, Word, PPT, Excel) — great for handling these files. The favorite for anyone doing office work.

Honestly, the most useful skill is often one you write yourself, shaped around how you actually work.

A few quick reminders

• When you start on a project, drop a CLAUDE.md file in it with your stack, how to run things, and any gotchas. Claude reads it and gets up to speed, so you're not repeating yourself.
• Your usage is shared with the web version, so keep an eye on it — especially during big tasks.
• Don't leave all permissions on for convenience. Letting it run on its own while touching untrusted content is risky. Get into the habit of glancing before you approve.