Claude Track
Module 10
Claude Track — Module 10
Good Wasn't Good Enough: Maya's team could get passable descriptions from Claude, but not great ones. Adding a reasoning step ("identify the key selling point first, then write") and using the conversation as a refinement loop — "make it 20% shorter", "remove the passive voice" — pushed quality from acceptable to on-brand.

Advanced Techniques in Claude Code

These techniques separate good results from exceptional ones. All of them work directly in the Claude Code chat panel in VS Code — no code required.

Chain of Thought

Add "Think step by step before answering" to any complex request. Claude reasons through the problem out loud, which surfaces assumptions you can catch and correct before the final output appears.

Iterative Refinement

Treat the conversation as a drafting loop. After Claude's first response, follow up: "Make it 20% shorter." "Remove all passive voice." "Add a specific example." Each turn tightens the result.

Task Decomposition

Break large tasks into steps across messages: "Step 1: list the issues in @report.md." Review, then: "Step 2: draft fixes for the top 3." Errors in step 1 don't corrupt step 2.

Custom Instructions

VS Code's Claude Code supports a CLAUDE.md file at the root of your project. Put standing instructions here — tone, conventions, banned phrases — so every session starts with the right context automatically.

Using CLAUDE.md for Standing Instructions

CLAUDE.md — ThreadCo project instructions
# ThreadCo — Claude Standing Instructions

## Brand Voice
- Friendly, direct, slightly playful. Never corporate.
- Sustainability is a feature, not a badge. Mention it naturally.
- Forbidden words: vibrant, perfect, stylish, must-have, luxurious
- No exclamation marks in product copy.

## Code Conventions
- TypeScript everywhere. Prefer `const` over `let`.
- All async functions must handle errors explicitly.
- Test files live in __tests__/ next to the source file.

## Review Checklist
When reviewing any pull request, always check:
1. Does it have tests?
2. Are error states handled?
3. Does the UI copy match the brand voice above?

Refinement Loop in Practice

TurnWhat you typeWhat changes
1Write a product description for the Sunset Gradient Tee (@sunset-tee.md)First draft — correct but generic
2Good start. Make it exactly 2 sentences. Cut any adjectives that don't describe a physical property.Tighter, more concrete
3The second sentence is too functional. Rewrite it to evoke the feeling of wearing it, not just the spec.Sensory, brand-authentic
4Perfect. Now apply the same approach to @midnight-tee.md and @wave-crop.md.Batch — Claude uses the refined style as the implicit example
i
Slash Commands Speed This Up

Claude Code has built-in slash commands: /clear resets the conversation, /compact summarises history to free up context, /review triggers a code review on the current file. Type / in the chat panel to see all available commands.

i
CLAUDE.md vs .windsurfrules — Not the Same File

CLAUDE.md is the standing-instructions file for Claude Code in VS Code. If you also use Windsurf, that IDE uses a separate file called .windsurfrules — same concept, different tool, different filename. Do not confuse them or use one in place of the other.