What next

You have finished the course. You can start your app, keep it current, change its modules, and build one of your own. From here you teach yourself, with Claude as the guide. This page shows where to go.

Where you are on the path

Stage	What you can do	Where you learned it
Artifact maker	Build small things with Claude in chat	Before the course
Runner	Start the app, find your way, change wording and data by asking	Lessons 1–5
Modifier	Change existing modules and take a change back	Lesson 6
Module builder	Design a module for your own work and have Claude build it on a block	Lesson 7, and from here on

Lesson 8 made you a daily user. The next step is to become a module builder in earnest: to notice what your job needs and turn it into a module without a lesson to follow.

Become a module builder

A good module starts with a list you keep somewhere else: a spreadsheet, a notebook, a long email thread. Ask yourself three questions:

What are the rows? Accounts, business reviews, feature requests, risks, ideas.
What do I need to see at a glance? Those become the table's columns.
Which block fits? A list of things with fields is a datatable. A list with a status and due dates can use the task view.

Then describe it to Claude and ask for a plan before anything is built:

"I track feature requests from customers in a spreadsheet: the request, the customer, who asked, when, and whether Product has answered. I want a Requests module for it. Propose the columns and the view, and wait for my yes."

Build one module at a time, use it for a week, then change it. A module you have outgrown is a good sign. The how-to steps are in Add a column, Manage modules and Bring in data.

Find a mentor

Power users such as a colleague who has built several modules are mentors, not builders. They review a module file you wrote, explain a pattern, or show you a module they built. They do not build your app for you, and you do not hand it over. Good questions to bring:

"How would you split this module in two?"
"Is there a field kind that fits this column better?"

See Working with a mentor.

Advanced articles

These are look-up articles, not lessons. Read one when you need it.

When you want to	Read
Save a point you can go back to, and go back	Checkpoints
Run several modules on one block	Many modules on one block
Find your way in the code	Reading the code
Change how a whole block works	Changing a block
Teach Claude a job you repeat, such as your start of day	Skills
Take a newer version of the kit	Kit updates

Habits that keep you building

One change at a time. Ask for one thing, look at it on screen, then ask for the next. See How to ask Claude.
Read before you keep. Ask Claude what it changed and why. See Review a change.
Write rules down. When you settle how a module should work, ask Claude to put it in a wiki page.
Use the test. Before any change, ask: does this help me build, run and change my own app? If it makes you depend on someone else, choose another way.

When something breaks

Describe what you see to Claude, in your own words, and paste any error. Most problems are solved in one or two turns. See When something breaks.

Look things up

Words for the vocabulary.
Prompts for a library of prompts by task.
Every module in the kit for what you can still add.
FAQ.

Back to the course overview.