Lesson 4 of 5 · about 6 min
Making things: documents, pages and visual outputs
When you finish, you can ask Claude to build something you can use, such as a checklist, a table or a simple page, and know how to refine it.
Stuck? Ask the AI tutorFrom text to something you can use
Many versions of Claude can show longer outputs, such as a document, a table, a diagram or a small interactive page, in a separate panel beside the chat. Anthropic has called this kind of output an artifact. Whether you see it, and what it can do, depends on your plan and the current version, so check the help pages.
The skill underneath does not change. You describe what you want to make, who it is for and what it must do. Then you look at the result, point to what is wrong, and ask for a change. You do not need to know how to code to ask for a simple checklist or a table.
Worked example: a volunteer schedule
A community garden in Nairobi needs a volunteer schedule. Weak request: "Make a schedule." Strong request: "Make a weekly table for our garden. Columns are Monday to Sunday. Rows are morning and afternoon. Leave room for three volunteer names in each slot. Add a note at the bottom about bringing water."
Look at the first version. Maybe the slots are too small. Reply: "Make the Saturday morning slot larger and add a column for tasks." Specific feedback beats "make it better." When the table is right, copy it into your own document or tool, since the working copy lives inside the app.
Asking for visuals and layouts
Claude can describe or draw simple visuals like flowcharts, outlines for a poster or a plain diagram, and it can read images you upload, such as a photo of a whiteboard or a chart. Treat what it reads from an image as a first pass. Blurry or small text can be misread, so check numbers and names.
For design work, name the purpose first. "A one-page flyer for a repair cafe, with big title, date, place and three bullet points" works better than "make a nice flyer." Ask for two options and choose. If you need final artwork, you will probably finish it in a design tool you trust.
Test it before you share it
Anything you build should be tested by a person. Click every link or button, read every line, and ask someone else to try it. If Claude made a calculator or form, enter easy numbers where you know the answer and see if it matches.
Do not put private details into something you plan to publish or share. Ask yourself who can open what you made. When in doubt, share a copy with the private parts removed.
Practice now
- Ask Claude to make a simple table or checklist for something real, such as a packing list for a trip. Give three rounds of specific feedback.
- Upload a photo of handwritten notes or a printed table and ask Claude to turn it into a clean list. Compare it with the original and mark any errors.
Use any AI assistant you have. Do not paste private, client or patient information into it.
Check yourself
1. Which feedback improves a first version most?
2. Claude reads text from your photo of a whiteboard. What next?
3. Before sharing something Claude helped you build, you should
Ask the AI tutor
Ask anything about this lesson, in any language. The tutor is an AI: it can be wrong, and it never needs your personal details.
AI-drafted. Checked by an automated validator and a separate AI reviewer; a person has not read every lesson. Translations and tutor answers are AI-made. Found a mistake? Tell us. AI can be wrong. General information only, not professional advice. Not affiliated with any AI company named. Current University is not accredited.