AI Codex

Learning Paths

Which of these is you?

Pick the path that fits where you actually are — not a topic, not a product. Each one is sequenced to build on itself. Start at step 1, or jump to wherever you're stuck.

Used AI before but new to Claude? Path 1 is the right starting point.

Start path 1 →

Never used AI before? Read this first — it takes 8 minutes.

Start here →
1

For individuals

Claude for your work

For anyone using Claude personally who wants to get noticeably better at it. How to prompt well, what Claude is actually good at, the mistakes everyone makes first, and how to build a workflow that sticks.

8 steps

~40 min

2

For managers & department heads

Rolling out Claude to your team

For the person responsible for getting their team actually using Claude. From deciding where to start, to setting up Projects and system prompts, to knowing whether it's making a real difference.

8 steps

~41 min

3

For IT & operations leads

Setting up Claude for your company

For the person asked to deploy Claude org-wide. Three stages — evaluation, deployment, ongoing management — with the exact decisions you need to make at each step, plus the internal data architecture to support it long-term.

15 steps

~85 min

WHEN YOU'RE READY TO BUILD

Going further

Building AI tools for your team

Once you know what your team needs — and what you'd build if you could — this path covers the practical side: what to build, how to build it, the mistakes that kill early AI products, and how to deploy something that lasts.

10 steps

~64 min

FOR CLAUDE CODE USERS

For teams using Claude Code

Setting up Claude Code for your team

Six guides on the .claude folder: what to configure, what to write in CLAUDE.md, which decisions to make as a team, how to keep it accurate, and what the agent layer looks like when you are ready for it.

6 steps

~44 min

FOR ENGINEERING LEADS & OPS TEAMS

For engineering leads & ops teams

Building your internal AI stack

Eight guides on the architecture that makes AI agents actually work at scale: a single internal MCP server, the right data access patterns, caching that eliminates cold start, access control that works, and the skills layer that turns repeated workflows into one-command automation.

8 steps

~74 min

FOR DEVELOPERS

{ }

// technical

Building with the Claude API

Implementation guides that assume you can code. The messages array, streaming, RAG, evals, tool use, prompt caching, cost optimization, persistent memory, auth, and rate limiting.

20 steps

~144 min