A SMALL FIRST WIN
Before you start
Use Claude Code with access to a project you are authorized to edit. Follow its official setup guide for your preferred environment. You need the project's normal preview and test commands.
- A project backup or a clean Git branch
- One page and one clear change
- Acceptance criteria and the normal checks
Use sample or approved information for your first run. Keep the review step visible before you expand the workflow.
LET’S DO THE WORK
Follow these four steps
- 01
Open the project and define the change
Use a clean branch or project copy. Open Claude Code in the project. Write down the page, the element, its desired behavior, and what a successful result looks like.
You’re ready when: You can explain the change in one sentence and undo it.
Step 1 · illustrated workflow - 02
Let Claude find and edit the right file
Send the prompt. Ask it to follow repository instructions and preserve unrelated work. If it finds several matching buttons, identify the correct one before it edits.
You’re ready when: The proposed files match the requested page.
Step 2 · illustrated workflow - 03
Review the diff and the page
Inspect the actual changed lines. Open the normal project preview and check desktop and mobile sizes. Click the CTA in a safe preview to confirm its destination. Read the test results and any stated limitations.
You’re ready when: Only the intended behavior changed and the evidence supports that.
Step 3 · illustrated workflow - 04
Decide whether it is ready to release
Use your project's normal review and deployment process after the checks pass. For a repeated maintenance job, save a written checklist or a Claude Code skill. A saved skill alone is not a schedule.
You’re ready when: The release follows your existing project process.
Step 4 · illustrated workflow
COPY, ADAPT, AND TRY
Your first run starts here.
Practice change brief Page: contact page. Button: change Get started to Book a call. Destination: keep the existing booking URL. Check: desktop and mobile layout.
Inspect this repository and its project instructions. On the contact page, change the primary CTA label from Get started to Book a call. Preserve the existing destination and other content. Locate the relevant component, implement the smallest change, and run the project's relevant checks. Show the changed files, a summary of the diff, and any check you could not run. Do not commit, push, deploy, change dependencies, or edit environment files. Ask if the page or button is ambiguous.
Proposed change Contact CTA: Get started → Book a call Destination: unchanged Evidence: changed file and diff Checks: actual results, with any gaps Release: waiting for your decision
Actual output will vary. Use this example to judge structure and accuracy, not as a promise of a successful run.
KEEP THE USEFUL PART
Make it repeatable.
After the first result meets your needs, use this follow-on prompt to carry the method forward.
For the next small website change, follow the same process: inspect project instructions, identify the smallest edit, preserve unrelated work, run relevant checks, and return a reviewable diff. The new change is [specific request]. Stop before commit, push, or deployment.
If this feature is not available
If you do not have repository access, ask Claude or ChatGPT to prepare a precise change brief for your developer. A text suggestion has not changed the live website.
YOUR FINAL CHECK
Is the result ready to use?
- Changed files match the requested scope
- Links and mobile layout checked
- Actual test results reported accurately
- Deployment is a separate, intentional step
Sources & access
Provider documentation reviewed October 31, 2026. These are original instructional recipes, not account-tested builds. Plan access, labels, and features can change.
Prompts and examples are written by Automately. Workflow illustrations are schematic, not screenshots of the providers’ interfaces.