Watch: practical Claude Code workflows

Start here: why this guide is useful

Use a short demonstration to understand the order of actions, then reproduce them in a disposable local project. Watching a successful video is not the same as verifying your environment. Pause after each important step, compare the visible output and record what differs. The useful result is a workflow you can repeat and explain yourself.

A concrete example

The following is an illustrative response format, not the result of an audit of your application. Use it to recognise what a useful answer should contain. Follow the detailed steps below, then compare the actual files, tests or output with this target. If the assistant only says “done”, ask for the changed artifact, the evidence and what remains unverified.

Observed step: identify the command or action shown.
Local result: record what actually happened.
Difference: explain environment or version mismatch before continuing.

Watch the session

This official Anthropic talk demonstrates practical Claude Code workflows. Use the embedded video, then try one idea on a small repository.

A three-step practice

Pick one task. Give Claude the project context and success criteria. Review the result and run the checks yourself.

Keep what worked

Write down the instructions that helped and the assumptions you had to correct. Reuse that context on your next task.

Read this tutorial as reference material:
https://nethanelfitoussi.com/article/claude-code-video?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Adapt example paths, commands and acceptance criteria to this repository rather than assuming they match.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.