Tips // Claude in practice

Tips for working better with Claude

One short tip at a time, with an example you can copy. Move through them at random or search for what you need.

PromptingBasicClaude.ai

If the output fails, fix only the culprit component

Read the output as a diagnosis: generic means too little context, wrong length or tone means a missing limit.

Do not rewrite the whole prompt: you lose what worked and do not know what fixed the problem. Change one thing, resend and compare. When each round improves little, stop iterating and edit by hand.

Example
Write the client follow-up about the two-day delay on the analytics deliverable. Cause: a data quality problem, already resolved; new delivery on Thursday. Accountable tone, no excessive apologies. Under 120 words.
#prompting#iteration#diagnosis