How to learn Claude in 1 weekend

Hey, it's Cindy. A weekend is enough to build familiarity with one useful workflow. It is not a promise that you will master every Claude feature. The easiest way to make the learning stick is to practise on a task whose quality you can already judge.

Friday: choose a task with a clear finish line

Pick something like turning meeting notes into a client update, comparing three proposals or summarising customer feedback. Avoid choosing “automate my business” as your first task. There are too many decisions hidden inside it to know what to practise first.

Our example is a client update from meeting notes. Collect a short set of notes and one finished update whose structure you like. Remove private information you do not need for the exercise. Write five checks: under 150 words, accurate facts, named owners where supplied, unresolved questions visible and no invented deadlines.

The AI Fluency foundations course is useful preparation for deciding what to delegate and how to judge the output. Your own checks are where those ideas become practical.

Saturday morning: learn the workspace you need

Open Claude 101 and use it to orient yourself. Then practise in one workspace. A chat is enough for our first exercise. You can start with a free Claude account; limits and access to additional surfaces depend on your plan. Check the current plans before buying anything.

Projects keep related instructions and reference material together. Cowork is relevant when your job involves working with files on your computer. Claude Code is useful for file-based and software work. Both need a paid plan. You do not need to install Claude Code to learn how to write a good client update.

Start a new chat, attach or paste your example and explain which parts you like. Ask Claude to identify the structure before drafting. Correct its interpretation if it misses something important. This teaches you to describe the output you want rather than hoping it guesses your taste.

Saturday midday: run the first example

Use these invented practice notes if you do not have your own:

Client: Example Studio
Homepage draft approved.
Maya will send the product photos on Tuesday.
Mobile layout still needs checking.
Launch date was discussed but not confirmed.
Next action: prepare the mobile review link.

A useful update should preserve Maya's commitment while leaving the launch date unconfirmed. It should not invent the person responsible for preparing the review link. This small exercise reveals whether the model treats gaps as questions or as opportunities to improvise.

Read the output beside the notes. Highlight unsupported facts, missing actions and language you would never use. Give specific feedback: “The launch date is unknown; put that in an open-questions section.” “The phrase ‘exciting milestone’ adds nothing here; remove it.”

Saturday afternoon: save the reusable context

If you are using a Project, create one for this recurring task, add the example material and put the reusable rules in its instructions. The Projects guide explains instructions and knowledge. New chats do not automatically carry every detail of an earlier conversation, so keep essential reference material where the project can access it.

If you stay in ordinary chat, save the reusable prompt in a document and paste it when needed. That is a perfectly useful starting setup. If you are already working in Claude Code, concise project guidance can go into CLAUDE.md; the memory documentation covers its role.

Keep one source of truth for the rules. If your saved prompt says 150 words but the project instructions say 300, Claude is being given a conflict you can remove yourself.

Copy this to build your reusable process

Help me turn meeting notes into a client update I can review and send. I am providing the notes, an example of the writing I like, and this checklist: [checklist]. First describe the example's structure and ask about any missing requirement that would change the result.

Draft an update under 150 words with progress, next actions and open questions. Use names and deadlines only when the notes support them. If an owner or date is missing, label it as unconfirmed rather than guessing. Keep the tone warm, clear and specific, and do not add promotional filler.

After the draft, show a separate fact-check table mapping each claim to its source note. Once I approve the result, produce a reusable instruction block with the required inputs, output format, missing-information rules and review checks. Keep the current notes out of that reusable block so I can use it on a different meeting. Do not send or post anything.

Sunday morning: make the process easy to repeat

Run the saved instructions on a second set of notes without the first conversation's context. This matters: a process that only works after twenty clarifications is not yet reusable.

For a repeated procedure in Claude Code, you can create a custom skill at .claude/skills/client-update/SKILL.md. The skills guide explains the format and invocation. /client-update would be your custom command, not a built-in Claude feature. Include your input requirements, steps and checks rather than one finished client email.

You can also keep the reusable prompt and stop there. Add a skill when it makes the workflow easier to invoke and maintain. Neither instructions nor skills automatically grant access to an app, and they do not make an output factually correct without review.

Sunday afternoon: try an awkward example

Give the process notes with an unnamed owner, conflicting dates and one genuinely unclear sentence. Good behaviour might be a question before drafting, or a draft with clearly marked unknowns. Decide which you prefer and update the saved instructions.

Then change the audience from a client to an internal team. If the task needs a different tone, make that an input rather than maintaining two nearly identical prompts. Your reusable system becomes more flexible when the variable parts are explicit.

If you need an app connection, test it separately after the core writing task works. A connector is useful when it retrieves material you need. It also adds permissions and another possible failure point. This weekend's example works with pasted notes, so no connection is required.

Check the result before calling the weekend finished

Use a small comparison table: input used, unsupported claims, missing actions, format issues and changes needed. The goal is not a perfect-looking score. It is evidence that you understand the process and can recognise its weak spots.

If the answer sounds generic, supply a better example and explain the difference. If instructions are ignored, look for contradictions or excessive detail. If it invents facts, strengthen the source requirement and missing-information rule. If a feature is unavailable on your plan, use the plain-chat version rather than treating an upgrade as the only way forward.

On Monday, you should have the original prompt, reusable instructions, two inspected examples and a short review checklist. Begin with that one task, then add another when you can explain why the first works. Find more practical workflows in all free guides.