DEV Community

Samarth Bhamare
Samarth Bhamare

Posted on

everything i wish someone told me before i started using claude

i spent the first two weeks using claude completely wrong.

i'd open it, type a vague question, get a decent answer, and think "okay, that's useful i guess." then i'd close the tab and forget about it. i wasn't getting anything close to what people were describing — the hours saved, the output quality, the feeling that you had a smart collaborator instead of a search engine.

turns out i was missing some basic things that nobody explains to beginners. here's what actually changed how i use it.


1. stop treating it like a search engine

the biggest mistake people make is asking claude one-line questions and expecting magic. claude isn't google. it doesn't just retrieve — it thinks. and the quality of its thinking depends almost entirely on the quality of your input.

compare these two:

bad: what's a good marketing strategy?

better: i run a small skincare brand targeting women aged 25-40 in india. 
we sell on instagram and our own website. our budget is tight — under ₹20k/month 
for ads. what are 3 specific things i should focus on in the next 30 days?
Enter fullscreen mode Exit fullscreen mode

the second one gets you something you can actually use on monday morning. the first one gets you a wikipedia page.

the rule: give claude your situation, your constraints, and what "good" looks like for you. it can't read your mind, but it's very good at working with context.


2. use the "role + task + format" structure

this is the structure that unlocked everything for me. when you give claude three things — a role to play, a task to do, and a format to respond in — the output quality jumps noticeably.

role: act as a senior HR manager who has hired hundreds of people

task: review this job description i wrote for a marketing coordinator role 
and tell me what's weak, what's missing, and what would put off good candidates

format: give me a numbered list of issues, then a revised version of the JD

[paste your JD here]
Enter fullscreen mode Exit fullscreen mode

you're not just asking for feedback. you're telling claude who to be when giving that feedback. a senior HR manager thinks differently than a general AI assistant.

this works in almost any domain — legal review, financial planning, email drafting, coding. pick the right "role" and you get thinking that's calibrated to that domain.


3. ask it to think before it answers

claude has a tendency (like most AI) to jump straight to an answer. sometimes that answer is shallow. there's a simple fix:

before you answer, think through this step by step. consider at least 3 different 
angles before giving me your recommendation.
Enter fullscreen mode Exit fullscreen mode

or:

what are the weakest parts of the argument you just made?
Enter fullscreen mode Exit fullscreen mode

that second one is particularly useful. ask claude to challenge its own output and it will often surface things it glossed over the first time. i use this whenever i'm about to act on something important — a business decision, a contract review, a financial projection.


4. use it for first drafts, not final drafts

people either expect claude to produce publication-ready work on the first try, or they use it for such small tasks that they're underutilizing it completely.

the right mental model: claude is your first-draft machine. your job is to edit.

here's how i write emails now:

write a short email to a client who paid late (3 weeks). 
the invoice was for ₹45,000. i want to be firm but not aggressive — 
we still want to work with them. keep it under 150 words.
Enter fullscreen mode Exit fullscreen mode

that takes me 20 seconds. i get back something that's 80% of the way there. i spend 3 minutes making it sound like me and fixing anything that's off. total time: under 5 minutes. old way: 15-20 minutes of staring at a blank screen.

the same applies to blog posts, proposals, SOPs, presentation outlines, cold messages — anything where starting is the hard part.


5. have conversations, not one-off prompts

most people write one prompt, read the response, and start a new chat for their next question. this is like hiring a consultant, having one call with them, and then calling a different consultant for every follow-up.

claude gets better as a conversation continues. it builds on context. it remembers what you've said. it refines its understanding of what you're trying to do.

try this instead: when you're working on something, keep one conversation open for that entire project.

[start of project]
i'm building a pitch deck for a B2B SaaS product that helps restaurants 
manage inventory. target audience is restaurant owners, not tech people. 
i'll be asking you questions throughout the next hour as i build this.

[later in same chat]
okay what should slide 3 look like? i want to explain the problem without 
using any technical language.
Enter fullscreen mode Exit fullscreen mode

by slide 8, claude knows your product, your audience, your tone, and your constraints. you don't have to re-explain anything.


6. the "documents in, intelligence out" pattern

this one is underused and genuinely impressive. you can paste a document into claude — a contract, a report, a competitor's pricing page, a job offer — and ask it to analyze, summarize, compare, or flag things.

here is a freelance contract i was sent. i'm a graphic designer.
[paste contract]

flag any clauses that:
1. limit my ability to use this work in my portfolio
2. could make me liable for things outside my control
3. are unusual compared to standard freelance contracts

explain each one in plain language, not legal language.
Enter fullscreen mode Exit fullscreen mode

i've used this to review vendor agreements, summarize 60-page government reports, compare two job offers side-by-side, and pull key data out of dense financial documents. it's not a lawyer. it's not an accountant. but it's a very good first pass that tells you what to ask the actual professional.


the honest truth about where people get stuck

these techniques sound simple, but applying them consistently across different situations — writing, legal, finance, healthcare, marketing — takes practice. and most tutorials online are either too technical (written by developers) or too vague ("just write better prompts!").

i spent about three months figuring all of this out through trial and error. i compiled everything — including 114 more prompt codes across 12 specific use cases — into a 40+ page PDF guide built specifically for non-technical people.

it covers beginner through full automation, with 8 industry playbooks for marketing, legal, healthcare, finance, education, real estate, consulting, and e-commerce. if you're in any of those fields and want to actually get good at claude, it's at https://clskills.in/guide — starts at $19.

if you're in india, use code INDIA99 at checkout.


the techniques above will make you noticeably better starting today. the rest is just reps.

by samarth bhamare — clskills.in

Top comments (0)