Your first real workflow with Claude Code

Start here: why this guide is useful

Before asking an assistant to change an unfamiliar repository, make it inspect the project and propose the smallest useful task. This guide introduces a repeatable sequence: understand, constrain, implement, verify and explain. For example, changing a form should preserve the current user flow and include a check of the actual submission result.

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.

Scope: one agreed form behaviour.
Change: the relevant component and handler.
Evidence: actual submission result and remaining limitations.

Start with context

Open your project and ask Claude to explain the relevant files before making a change. Give it your goal, constraints, and a way to check the result.

Keep one task in focus

Describe one concrete improvement. Ask for a short plan, review it, then let Claude implement the agreed change. Store stable project instructions in CLAUDE.md.

Verify the result

Run the project’s tests and inspect the diff. Ask Claude to explain any failing check and resolve it before committing.

Try this prompt

Use the copyable prompt below on a small project. Adapt the test command to your repository. This is an introductory workflow; check the linked documentation for current commands.

Read this tutorial as reference material:
https://nethanelfitoussi.com/article/claude-code-workflow?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.

Read this project and explain its structure. Then propose a small implementation plan for [my task]. Wait for my review, implement it, run the relevant tests, and show me the diff.