9 Practical Claude Tips from 8 Months of Daily Use (Non-Coding)

After 8 months of daily Claude use (mostly writing and research, not code), a Reddit user distilled 9 practical lessons they wish they'd known from day one. The advice applies to any developer using Claude as a thinking partner rather than an oracle.

Key Takeaways

• Editing beats generation. Feeding Claude a messy first draft and asking it to tighten yields far better results than a blank-page prompt. The model gets generic without a starting point.
• Don't dump everything into long context at once. The user used to paste 40 pages and ask a question. Now they tell Claude what to look for first, then paste—resulting in a "night and day" accuracy improvement.
• Force disagreement. Claude agrees too easily if you frame questions as "right?" Asking "what's the strongest argument against this" produces sharper pushback.
• Save style/instruction sets once. Setting up a persistent system prompt beats re-explaining in every chat. The user regrets not doing it earlier.
• Be specific with "make it human." Vague instructions like "make it sound human" do almost nothing. Concrete directives—"cut every sentence that sounds like writing, shorter words, leave one rough edge"—work much better.
• Use Claude as a rubber duck. Explaining a problem out loud, even to Claude, often surfaces the answer on your own.
• Read for hedging. When unsure, Claude says things like "this may vary." The user now asks it to flag confidence explicitly.
• Prefer screenshots and docs over copy-paste for structured content. Pasting a table as text loses the table; dropping an image preserves it.
• Think partnership, not vending machine. The worst months were when treating Claude as an oracle. The best months came from treating it like a sharp colleague who needs context.

The post is a goldmine for teams using Claude for non-code tasks like drafting, research, and analysis. Most public tips focus on Claude Code, making this perspective especially valuable.