Claude 101 Best Practices

These ten habits are the fastest path from "just installed Claude" to genuinely productive, across whichever interface you're using.

None of them are specific to one surface - they hold whether you're in the web app, the desktop app, mobile, the Chrome extension, or Slack.

How to Use This List

• Read through once, then let the habits form naturally as you use Claude day to day.
• Come back to this page if a conversation feels less useful than it should - the fix is usually one of the items below.
• These aren't sequential steps; treat them as a set of habits to build together, not a one-time setup process.

A - Starting a Conversation Well

• Give relevant context up front. Claude only knows what's in the current conversation plus its training, so a request with real background - audience, goal, constraints - gets a sharper first answer than a bare one-liner.
• Say what "done" looks like. If you know the format, length, or tone you want, say so from the start rather than correcting it after the fact.
• Start a new conversation for a new task. A fresh conversation gives Claude a clean slate, which is usually better than continuing an old thread that's drifted off topic.
• Attach the actual document instead of paraphrasing it. Sharing a file or pasted text as part of your message gives Claude the real source material to work from, rather than your summary of it.

B - Working Through a Task

• Edit or regenerate instead of restarting. If a reply isn't quite right, editing your message or asking for another attempt is usually faster than abandoning the conversation and starting over.
• Match the model to the task. Claude Haiku 4.5 is fast for simple questions, Claude Sonnet 5 is the solid default for everyday work, and Claude Opus 4.8 is worth the extra time for harder or higher-stakes tasks.
• Reach for the right interface, not just the closest one. Quick questions fit the web or mobile app, multi-file work fits the desktop app's Cowork mode, and coding tasks fit Code mode - picking deliberately beats defaulting to whatever's already open.
• Review autonomous work before relying on it. When using Cowork or Code mode, check what was actually changed or created, the same way you'd review a colleague's independent work.

C - Keeping It Sustainable

• Rename conversations you'll want to find again. A clear title makes an ongoing project or recurring task far easier to locate later than the auto-generated one.
• Know your plan tier's limits before you need them. Understanding whether you're on Free, Pro, Team, or Enterprise - and what that means for usage limits and model access - avoids surprises mid-task.

FAQs

Related

• What Claude Is and How Conversations Work - the context model behind several of these habits.
• Claude 101 Basics - the walkthroughs these habits build on.
• Choosing the Right Claude Interface for the Task - a deeper look at the interface-matching habit.

Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.