How to fix a small bug with Claude

Now that we’ve got Claude setup, let’s take it for a quick test drive. This guide shows how to fix a bug with Claude.

Prerequisites

ℹ️ We’ve provided a sandbox repo for your convenience, however feel free to adapt the steps to a repo of your choosing as well.

Get the sandbox repo installed and running locally
For context, it’s a React SPA that simulates an auction application. Users add in Bids, current bid should so go up and the Users should not be able to bid lower than the current bid.
- You can also run this prompt to have Claude read:
```
Explain the code in the "sandbox" folder to me
```
We’ve left some deliberately awful and buggy code in the src/hooks/useBidding.ts file. Take a minute to read through and take note of what’s wrong.

This logic in `useBidding.ts` isn't working, could you fix this?

You will be prompted before any edits are made, if Claude makes a mistake, this is when you can intervene.

Some other follow up prompts you can try out:

How can we make the `useBidding` hook better?

Explain how {{ insert filename or function here }} works

Feel free to continue to experiement too.

Claude is capable of taking plain language directions and traversing the file system to find the relevant files to pull in as context but this can sometimes backfire. For minimum friction, we always encourage users to clearly instruct Claude which files it should look into as a starting point when debugging
If tests are provided, Claude is also able to iterate upon itself and validate that the code modifications still adhere to the previous tests assertions. Taking a step back, we find Test Driven Development really flourishes with Ai Tooling.