A practical map through the Claude Code course: what remains essential, what to treat as terminal-specific, and what exercises make the course useful for economics research.
The course was made for a broad audience, so it spends real time on terminal setup and a deployed app. Economists should use it as a map of the core primitives: files, context, permissions, skills, MCPs, plugins, subagents, and Git.
I now usually point economists toward the Codex desktop app first, but the Claude Code course still explains the concepts behind agentic work very clearly. Use this guide to separate the durable habits from the app-builder examples.
Open the full course on YouTube →Claude Code is not just a chatbot and not only a coding tool. For economists, the useful mental model is a local research assistant that can read files, run commands, and carry out multi-step work in your actual project folder.
The YouTube-summary exercise is a good low-risk first move. Translate it to economics: summarize a seminar, extract references from a talk, or turn a transcript into a short research memo.
The website example is useful primarily as a demo of skills, but it can also be applied directly to your personal academic site. The broader lesson is that installed skills can package repeatable workflows.
This is the operational core. Economists do not need to become terminal wizards, but they do need to understand paths, tool approvals, context windows, compaction, voice input, and permission boundaries.
The course explains why giant CLAUDE.md files can backfire. For research projects, keep instructions short: commands to run, files never to edit, what counts as a valid output, and how results should be checked.
This is the highest-leverage section for research work. Slow down on skills first, then learn enough about MCPs, plugins, and subagents to know which concept fits a given economics workflow.
Most economists will not build apps, so you can skip or skim this section. Seeing how to work on bigger software projects can nevertheless be useful for structuring tasks and delegating to agents in your own larger research projects.
Use Claude Code with yt-dlp on the transcript of some economics seminar on YouTube. Ask for a one-page memo with claims, citations to check, open questions, and follow-up readings.
Write a skill that tells Claude Code how you prefer to have your tables formatted, your Beamer decks styled, or how to convert papers to Beamer decks according to your preferences.
Try a Claude Connector, MCP, or Codex plugin for email, calendar, Drive, or Notion. Keep the task narrow: seminar prep, referee-report triage, or coauthor follow-up.
Ask Claude Code for an evaluation of a pre-agentic coding era project folder's code. Then ask it how it would suggest cleaning it up, and implement its suggestions.
The slide deck above is the full public deck I used for the course. The timestamped plan on this page is the economist-specific layer: where to slow down, where to skim, and what exercises to do after watching.