Back to Blogs
Everything I Wish Someone Had Sent Me When I Started With Claude Code

Everything I Wish Someone Had Sent Me When I Started With Claude Code

Lets Code•April 25, 2026

So you opened your terminal, typed claude, and now you’re trying to figure out what the hell to do next.

I get it. I’ve been there. The first week with Claude Code is genuinely confusing : there are docs, courses, awesome lists, plugins, subagents, skills, MCP servers, and roughly nineteen Discord servers all telling you slightly different things. Anthropic ships fast, the community ships faster, and half the tutorials you find on Google were already outdated by the time they got indexed.

So I made you a list. This is what I’d send a friend if they texted me “okay where do I actually start.” Nothing in here is filler. If a resource is on this list, I either learned something real from it or I keep going back to it. If it’s not here, it probably wasn’t worth your evening.

A small note before we start. I don’t get anything for linking these. No affiliate codes, no sponsorships. Just stuff I think is good. If something on this list goes downhill, tell me and I’ll yank it out.

The official stuff (read these first)

I know, I know —> “read the docs” is the most boring advice in tech. But hear me out: the Anthropic docs and engineering blog are unusually good. Half of what you’ll read on Medium is just someone’s paraphrase of these pages anyway, so you might as well get it from the source.

The docs you’ll actually use

The blogs worth subscribing to

  • Anthropic Engineering Blog — Easily one of the best engineering blogs in AI right now. Tool design, parallel agents, session management, tool-use patterns. Read the backlog.
  • Claude.com Blog — Product news, hackathon recaps, customer stories.
  • Anthropic News — Model launches and research drops.
  • Anthropic Learn Hub — A nice front door to courses, AI Fluency stuff, and frameworks.

Free courses that don’t waste your time

Anthropic put four full courses on Anthropic Academy (Skilljar) and they’re all free. No credit card, no email gate, no “upgrade to unlock module 3.” If you take all four, you’ll spend about ten hours and come out the other side genuinely good at this.

The big four (do them in this order)

  1. Claude with the Anthropic API — Stops Claude from just being a chatbot in your browser. Covers messages, streaming, tool use, prompt caching.
  2. Introduction to Agent Skills — What Skills actually are, when to write one, and how they’re different from prompts and subagents.
  3. Introduction to Model Context Protocol — The thing that lets Claude do stuff in your environment instead of just talking about it.
  4. Claude Code in Action — The full Claude Code workflow. Hooks, custom commands, context management, the works.

The shorter ones, if you’re impatient

If you prefer Coursera’s vibe

YouTube — for when you want to watch someone else use it

Honestly, half the trick to Claude Code is flow — when to plan, when to let it run, when to cut your losses and start a new session. That stuff is hard to learn from text. Watching someone work with it for an hour will teach you things no doc ever will.

Blogs and deep-dives that changed how I think

These are the posts I keep going back to. Some are official, some are written by random folks who happened to nail something the official docs danced around.

The ones I’d hand to my past self

Community writing that’s worth your time

Independent stuff that’s somehow better than it has any right to be

  • ClaudeLog — Run by InventorBlack (a Claude Developer Ambassador). Not affiliated with Anthropic. Probably the best independent knowledge base for power-user techniques.
  • Awesome Claude AI Resources Directory — A web-based aggregator that pulls from across the ecosystem. Good for browsing.

The awesome lists (your real homepage from now on)

If you bookmark nothing else from this post, bookmark these. The Claude Code ecosystem moves so fast that the only sane way to keep up is to watch what gets added to these repos every couple of weeks.

Subagents, skills, and plugins worth installing

The awesome lists above have everything. These are the ones I’d actually try first.

Subagents

Skills

Plugins

  • frontend-design — For when you don’t want your UI to look like every other AI-generated landing page.
  • artifacts-builder — Multi-component HTML artifacts with React, Tailwind, shadcn/ui.
  • mcp-builder — A skill that helps you write better MCP servers (yes, very meta).
  • tdd-guard — Forces TDD workflows. Either you love this idea or you hate it.
  • commands — Production-ready slash commands.
  • cc-sessions — Hooks, subagents, commands, and git/task management bundled together.
  • ralph-claude-code — An autonomous dev loop with intelligent exit detection.
  • Continuous Claude — Runs Claude Code in a loop, auto-creating PRs. Use with caution.

The “guides as repos” people

These aren’t tools, they’re whole guides published as GitHub repos. Each one is genuinely useful in a different way:

How to write a CLAUDE.md that doesn’t suck

Your CLAUDE.md is the single highest-leverage thing in your project. Get it right and Claude feels psychic. Get it wrong and you spend your whole day fighting with it.

The patterns that show up everywhere:

  • Less is more. Past 300 lines, performance starts dropping. HumanLayer keeps theirs under sixty.
  • WHAT / WHY / HOW. Map the codebase, explain the purpose, tell Claude how to verify its own changes.
  • Progressive disclosure. Don’t dump everything in one file. Link out to other markdown files Claude can pull in only when relevant.
  • Concrete commands beat abstract principles. “Run bun test” is more useful than “Always test your code.”

Going deeper — research, papers, and the why behind it all

If you’ve read everything above and still want more, you’re at the point where the research papers start paying off.

Tools that play nicely with Claude Code

The official surfaces

Companion tools that quietly make life better

  • recall — Full-text search across your past Claude Code sessions. You’ll wonder how you lived without it.
  • Rulesync — Translate configs between Claude Code, Cursor, Aider, etc.
  • run-claude-docker — Run Claude Code in an isolated Docker sandbox. Sleep better.
  • CCHub — Desktop app for managing the whole ecosystem (MCP marketplace, profiles, skills, plugins).
  • Repomix — Pack your repo into a single AI-friendly file. Great for one-shot prompts.
  • ccundo — Granular undo, by reading directly from session files.
  • claude-code-docs (mirror) — A mirror of Anthropic’s docs with full-text search. Sometimes faster than the real site.

Where the community actually hangs out

If you only have three weeks, do this

If this list feels like a lot — yeah, it is. Here’s the actual plan I’d give a friend.

Week 1 — Get something done.

  1. Install Claude Code. Read the Overview.
  2. Read Best Practices for Claude Code. Yes, the whole thing.
  3. Take Claude Code in Action on Skilljar. Three hours, well spent.
  4. Write a tiny CLAUDE.md for one real project, using HumanLayer’s guide.

Week 2 — Get good.

  1. Read How Anthropic Teams Use Claude Code.
  2. Take Introduction to Subagents and Skills in Claude Code.
  3. Browse hesreallyhim/awesome-claude-code. Install two or three things. No more.
  4. Try Plan Mode on something non-trivial.

Week 3 — Go deep.

  1. Take Introduction to Model Context Protocol.
  2. Build a tiny MCP server for an API you already use.
  3. Read the Agent SDK post and start something small with it.
  4. Subscribe to the Anthropic Engineering blog and r/ClaudeAI.

After that — just keep showing up.

One last thing

A list like this is partially out of date the moment it goes live. Stuff ships every week. The durable advice — the only advice that’ll still be true a year from now —> is this: bookmark the awesome-lists, follow the Anthropic Engineering blog, and spend more time using the tool than reading about it.

Reading about Claude Code is fun. Using it is what actually makes you better at it.

If you found something I missed that genuinely belongs on this list, let me know —> I’ll keep this updated as the ecosystem evolves.

L

Lets Code

Contributing Writer

Share this article