How to Use Claude for Coding

Claude handles coding tasks well when you treat it like a colleague who just joined the project. It does not know your repo, your conventions, or your stack unless you tell it. The more context you provide up front, the less time you spend fixing the output.

The minimum coding brief

• Stack — language, framework, key libraries
• Scope — which files or functions are involved
• Goal — what the code should do when it works
• Constraints — patterns to follow, things to avoid, no new dependencies
• Verification — how you will check the result (tests, build, manual check)

Example: implementing a new feature

Bad

Add pagination to my app.

Better

Add cursor-based pagination to the /api/products endpoint.
Stack: Next.js App Router, TypeScript, Prisma with PostgreSQL.
Return 20 items per page with a nextCursor field.

Best

Stack: Next.js App Router, TypeScript, Prisma with PostgreSQL.
Goal: Add cursor-based pagination to GET /api/products.

Requirements:
- 20 items per page
- Response shape: { items: Product[], nextCursor: string | null }
- Cursor is the product ID of the last item
- When nextCursor is null, there are no more pages
- Match the existing error handling pattern in /api/orders (attached below)

Constraints:
- Only modify src/app/api/products/route.ts and its test
- No new dependencies
- Use the existing Prisma client instance

First: explain your approach in 3-4 bullets.
Then: write the implementation.
Then: write or update the test.

Existing error handling pattern:
[PASTE RELEVANT CODE FROM /api/orders]

The best version works because Claude knows the response shape, the cursor strategy, the file scope, and has a reference pattern to follow. It also separates planning from implementation.

Example: fixing a bug

Stack: React 18, TypeScript, Zustand for state.
Bug: The cart total shows stale values after removing an item.
File: src/store/cartStore.ts

Steps to reproduce:
1. Add two items to cart
2. Remove one item
3. Total still shows the sum of both items until page refresh

Relevant code:
[PASTE THE STORE FILE OR THE RELEVANT FUNCTIONS]

Propose a fix. Explain the root cause in 2-3 sentences before writing code.

Example: explaining code before changing it

Before making any changes, explain how the billing retry logic works
in src/lib/billing.ts (pasted below).

Cover:
- What triggers a retry
- How many retries are attempted
- What happens when all retries fail
- Any side effects (emails, webhooks, database writes)

Then propose the smallest change to add an idempotency key based on invoiceId.
Do not write the change until I approve the plan.

[PASTE FILE]

Providing codebase context effectively

• Paste relevant types or interfaces — these define the contract
• Paste one example of the pattern you want followed — 'match error handling in auth.ts'
• Include the test file if one exists — Claude can update it alongside the change
• Mention the build/test command so Claude can suggest a verification step

Common coding mistakes with Claude

• Asking for code without specifying the language or framework version
• Not providing existing patterns — Claude invents its own, which may not match your codebase
• Accepting code without reading it — always review before merging
• Asking Claude to edit a file it has not seen — paste the relevant code
• Skipping the plan step for complex changes — plans catch scope issues early

Related reading: /blog/how-to-get-better-code-from-claude for quality techniques, /blog/how-to-debug-and-review-code-with-claude for debugging workflows, and /blog/how-to-use-claude-code-for-real-development-tasks for the Claude Code tool.