Trackers, calculators and dashboards you describe in plain English and share with your team. This course is for people who already ask Claude for things and now want working tools back, not just documents: a task tracker with filters, a pricing calculator, a small dashboard your teammates can open on a phone. You will never type code. You describe what you want, Claude builds a self-contained interactive page called an artifact, and you learn to steer it, check it, polish it and share it. Everything happens in Claude on the web and in the desktop app. Across four short modules (about four hours in total) you build one real tool, the Autumn Ember Launch Tracker for Kettle & Kite, a fictional tea shop. The course stands on its own. If you have never made an artifact before, the Quick Start module gets you ready in 20 minutes. Skip this course if you want live data from your other apps, shared storage, or AI running inside a page. Those are covered in course 3 of the series.
Image coming soon: The finished Autumn Ember Launch Tracker: a title with "18 days to launch", a progress bar showing 2 of 10 tasks done, owner and status filter chips, and a table of tasks with owner, status pill and due date
Course example (fictional company). This is the tool you ship in the capstone.
What you'll be able to do
By the end of the course you will be able to:
Write a brief that gets a working tool on the first or second try. You will state what the tool is for, what data it holds, how people interact with it and what "done" looks like, so Claude isn't left to guess.
Update a tool people are already using without breaking it. You will make changes, check them, and know how to roll back if something goes wrong.
Prerequisites
Comfortable asking Claude for things. You have had ordinary conversations with Claude and can describe what you want in a few sentences. That is enough.
No coding. Nothing in this course asks you to read or write code. When Claude shows code, you can ignore it.
A Claude Pro plan or higher. Anyone can create artifacts, but sharing with roles, email invitations and public links depends on your plan (Anthropic: Share artifacts; Anthropic: What are artifacts). Plans change, so check the current plan table before you start.
Course 1 is optional.Claude Artifacts Essentials covers documents, decks and designs. This course doesn't depend on it. Lesson 01-01 gives you everything you need from it.
The roadmap
The course moves in one direction: get oriented, make your first artifact, build and polish the tracker, share it, then ship it. Module 01 is a shortcut for newcomers. If you have made and shared an artifact before, skim it or go straight to Module 02.
#
Module
Lessons
What you get out of it
00
Orientation
01 Syllabus
The map, the capstone, and how to study
01
Quick Start
01 Artifacts in 20 minutes
Your first artifact, opened, changed and found again. Meant for anyone who skipped course 1
02
Custom Pages
01 From request to working tool · 02 What a page can and can't do · 03 Make it look good and work on a phone
A working, good-looking tracker built from a written brief
03
Working With Others
01 Roles, comments, and public links · 02 Updating a tool people are using
The tracker shared with the right people, and a safe way to change it
04
Capstone
01 Ship the Autumn Ember Launch Tracker
The finished Autumn Ember Launch Tracker, shared with a teammate as a commenter
That is eight lessons in total. Each Module 02 lesson adds one layer to the same tracker, so do them in order.
Time commitment
The course takes about 4 hours: roughly 2 hours of lessons and 2 hours of hands-on building with Claude. A comfortable pace looks like this:
Sitting 1 (about 45 min): this syllabus and Module 01.
Sitting 2 (about 90 min): Module 02. By the end you have a working, polished tracker.
Sitting 3 (about 60 min): Module 03. Share the tracker and practise an update.
Sitting 4 (about 45 min): Module 04. Run the capstone checklist and ship.
If you can, leave a day between sittings. The spacing isn't just for convenience, as the next section explains. Your time will vary with how many rounds of changes you ask Claude for, and those rounds are part of the learning.
How to study in LearnOS
Build along, don't just read. Every lesson ends with a practice task done in Claude. The tracker only exists if you make it.
Recall before you re-read. After a lesson, close it and write down the four parts of a good brief, or the three sharing roles, from memory. Practising retrieval like this improves long-term retention more than restudying the same material. In Roediger & Karpicke (2006), students who were tested remembered more after two days and after a week than students who restudied, even though the restudy group felt more confident.
Use the flashcards and let the scheduler space them. Reviews spread over days beat the same number of reviews crammed together. A meta-analysis of hundreds of experiments found that the best gap between study sessions grows with how long you need to remember the material (Cepeda et al., 2006; open-access copy).
Chat with the lesson when a step doesn't work. Paste in what Claude built or said, and ask what to change in your request. The lesson chat pulls from the cited sections.
Keep a brief journal. Save each brief you write and note what Claude got wrong the first time. In Module 04 that journal becomes your checklist.
Reading the images in this course
Every image in the course is one of three kinds, and its caption tells you which:
"Image: Anthropic" — an official screenshot shown directly from Anthropic's documentation, with a link to the page it comes from. These show the real product. Anthropic updates its interface, so small details may differ from what you see today.
Official example links — links to examples Anthropic publishes. Open them to see the real thing working.
"Course example (fictional company)" — pages and mockups built for this course around Kettle & Kite, a fictional tea shop, and its launch team: Mara, Jonah and Priti. The hero image above is one of these. They show what your result should look like. They don't show Claude's own interface.
Here is an official screenshot of an artifact open in its viewer. The Share menu is open, showing an Always share latest version toggle, a version picker, an audience selector and Copy link.
Image: Anthropic, Claude Code artifacts docs. This screenshot comes from Anthropic's Claude Code documentation. The Share dialog in Claude on the web and in the desktop app may look different: the help center describes Can view, Commenter and Can edit roles there. Module 03 walks through it.
The capstone
You finish the course by shipping the Autumn Ember Launch Tracker. Kettle & Kite's autumn blend launches on Saturday 17 October 2026, and the team needs one page that shows who is doing what. The finished tool has:
Tasks with an owner, a status and a due date. Owners are Mara, Jonah and Priti, plus one "Whole team" task. Statuses are To do, Doing and Done.
Owner and status filters, so Priti can see only her open tasks.
A progress bar showing how many tasks are done, plus a countdown to launch day.
Light and dark modes, and a layout that works on a phone.
Shared with a teammate as a commenter, so they can leave feedback without changing the page.
You build it one layer at a time across Module 02: the brief, then a reality check against the page limits, then design. You share it in Module 03 and ship it with a final checklist in lesson 04-01. It's a small tool, but it uses every skill in the course. When you're done, you'll have a tracker pattern you can reuse for any launch, event or project your own team runs.
What this course omits
The course deliberately leaves some things out. Here is what, and where to find it:
Live data from connected apps, storing shared data, AI inside a page, and admin controls. Artifacts can connect to your apps, store data, and call Claude, and organisation owners have extra settings. All of that is covered in course 3, Live, Shared, AI-Powered Artifacts. In this course the tracker's tasks live inside the page itself.
Documents, decks and designs. For the basics of non-interactive artifacts, see course 1, Claude Artifacts Essentials. It's optional and not needed here.
Claude Code. Claude Code can also publish artifacts from a terminal session. This course sticks to Claude on the web and in the desktop app, and never asks you to use a terminal.
Part of the Claude Artifacts series. Each course stands on its own: 1. Claude Artifacts Essentials · 2. Build Interactive Tools with Claude Artifacts (this course) · 3. Live, Shared, AI-Powered Artifacts
Roediger & Karpicke, 2006 — the testing effect: retrieval practice beats restudying for long-term retention.
Cepeda et al., 2006 (open-access copy) — meta-analysis of distributed practice: spaced study beats massed study, and the best spacing grows with the retention interval.
Practice
Check your plan (2 min). Open Claude's settings and confirm which plan you're on. Compare it against the current plan table in What are artifacts and in Share artifacts.
Pick your route (1 min). Have you made and shared an artifact before? If yes, start at Module 02. If not, start at lesson 01-01.
Recall check. Without scrolling up, list the five features of the capstone tracker and the three kinds of images in this course. Then check your answers.
Start your brief journal. Write one sentence describing a tool your team could use: a tracker, a calculator or a small dashboard. You will come back to it after Module 02.
