Skip to Content
ReferenceBest Practices

Best Practices

Tips for working effectively with Claude in Blueberry.

Context Awareness

Let Claude See First

Before asking Claude to make changes, let it understand the context:

Look at the current file and tell me what it does.

Claude will call blueberry_get_context and see your open file.

Be Specific About Scope

Instead of “fix the bug”, try:

There's a bug in the login function on line 42. The user state isn't being updated after successful login.

Terminal Commands

Check Before Running

Ask Claude to explain commands before running them:

What command should I run to start the dev server? Don't run it yet, just tell me.

Use Appropriate Terminals

If you have multiple terminals, specify which one:

Run the tests in the "Tests" terminal tab.

Handle Long-Running Processes

For dev servers and watchers:

Start the dev server, then let me know when it's ready.

Claude can check the terminal output to confirm the server started.

Preview Browser

Describe What You See

After Claude opens a preview, describe any issues:

Open localhost:3000/dashboard. The chart should show user data but it's empty.

Use Screenshots Wisely

Screenshots are useful for visual issues:

Take a screenshot of the current page. The button alignment looks off.

Read Content for Data Issues

For content problems, use content capture:

Read the content of the current page. Are all the user names showing correctly?

File Operations

One Thing at a Time

Ask Claude to make one change, verify it works, then continue:

First, add the import statement. Let me check it compiles.

Review Before Saving

Ask Claude to show the changes before applying:

Show me what the updated function would look like before you make the change.

Working with Errors

Share Error Context

When you hit an error, give Claude the full picture:

I'm getting a TypeScript error. Check the terminal for the error message and look at the file it mentions.

Let Claude Debug

Claude can investigate issues:

The page isn't loading. Check the console logs in the preview for any errors.

Project Understanding

Start New Sessions Right

At the start of a session, orient Claude:

I'm working on a Next.js app. The main page is src/app/page.tsx. Take a look at the project structure.

Reference Documentation

If you have docs in your project:

Check the README for how the API authentication works.

Common Patterns

Code Review

Look at my recent changes in the Source Control panel and review them for any issues.

Testing

Run the test suite and summarize any failures.

Debugging

The form isn't submitting. Open the page, fill in the form, and check the network tab for what happens.

Documentation

Based on this function, write a JSDoc comment explaining what it does.
Last updated on