100 Claude Tips Packed Into One Image

{
“title”: “100 Claude Tips: From Setup to Mastery”,
“Text1”: “

You know that moment when you’ve got 12 tabs open, three half-watched YouTube tutorials on Claude, and you still can’t figure out which model to pick for what? I’ve been there. So when I stumbled onto this compact 100-tip cheat sheet posted by this LinkedIn creator, I genuinely got excited. The original poster took everything a normal person would need to go from beginner to competent Claude user and crammed it into a single scrollable image.

No 45-minute videos. No fluff. Just ten clean sections with ten tips each. I’ll walk through the full breakdown the author put together, step by step, with the reasoning behind each move so you can actually apply it today.

Step 1: Get the Cowork Setup right (Tips 1 to 10)

The creator starts with the foundation, and honestly, this is where most people already fumble.

1. Download the desktop app, not the browser version.
2. Create one folder on your PC called COWORK.
3. Inside it, make four subfolders: About me, Project, Template, Output.
4. Grab an anti-AI-style reference file to kill that robotic tone.
5. Pull together a short About me document so Claude knows who it’s working with.

Why this matters: Claude works best when it has persistent context. A clean folder system means you’re feeding it the same high-quality reference material every time instead of pasting random snippets into chat.

Step 2: Pick the right model for the job (Tips 11 to 20)

This is the part I think most users get wrong. The original poster lays it out simply:

• Opus 4.6 with Extended Thinking: complex reasoning, strategy, deep work.
• Sonnet: quick edits and everyday tasks.
• Haiku: fast scanning through files.

The line that stopped me scrolling: a bad prompt on Opus will always lose to a great prompt on Haiku. The model matters less than how you talk to it.

Step 3: Fix your prompting (Tips 21 to 30)

The expert’s rule here is refreshingly blunt. Stop writing wall-of-text prompts.

1. Attach files instead of describing everything inline. Files beat prompts.
2. One task per prompt. Not five stacked into one message.
3. Add the phrase “Does NOT sound like” to kill the default AI voice.
4. Give Claude the task, not the method. Let it figure out the approach.

That last one changed how I think about delegating to AI. You’re hiring a capable assistant, not micromanaging a robot.

Step 4: Use the AskUserQuestion tool (Tips 31 to 40)

This is the tip I had never seen packaged this clearly before.

• Start your first prompt on any new task with \”Start with AskUserQuestion.\”
• Claude builds you a clickable form with the right discovery questions.
• You click through answers instead of typing essays.
• If the direction feels off, just say so. Claude rebuilds the form.

It flips the dynamic. Claude interviews you, not the other way around.

Step 5: Connect your tools (Tips 41 to 50)

The creator points out that Connectors are sitting right there, free on every plan, and most people never turn them on.

1. Go to Settings, then Connectors, then Browse, then click Add.
2. Connect Slack, Google Drive, Notion, Gmail. Over 50 tools supported.
3. Claude reads your actual files. No more copy-paste loops.

Step 6: Install Plugins that match your role (Tips 51 to 60)

Inside Cowork, the author walks through the plugin system.

• Navigate to Cowork, then Customize, then Browse, then Install.
• Pick packs for your role: Marketing, Legal, Sales, Data.
• Type / in chat to trigger any plugin command instantly.
• Customize each plugin to match your company voice.

Step 7: Run Claude inside Excel (Tips 61 to 70)

This section genuinely surprised me. The original poster recommends installing Claude by Anthropic from the Microsoft Marketplace.

1. Claude reads every tab in your workbook.
2. It explains formulas in plain English.
3. Drop a PDF in and it extracts tables for you.
4. No macros. Claude highlights exactly what it touches.

Step 8: Projects and Teams (Tips 71 to 80)

The advice here is operational and sharp.

• Create one Project per deliverable, not per client.
• Upload one great example so Claude matches the standard.
• Convert one teammate first. Then scale to the whole team.
• Use a 15-minute demo to show, not tell.

Step 9: Use Artifacts well (Tips 81 to 90)

Artifacts are the visual outputs Claude can build inside the chat window.

1. Charts, dashboards, and trackers live directly in the conversation.
2. They work automatically inside Cowork.
3. Preview before exporting. Edit live. Then copy.
4. Share with non-Claude users as HTML files.

Step 10: Advanced Mastery (Tips 91 to 100)

The author closes with the principles that separate power users from dabblers.

• Keep reference files under 200 lines. Shorter beats longer.
• 80% of your About me file should describe what you’re NOT.
• Always review outputs, especially anything financial.
• Claude handles 80% of the busywork. You handle the strategic 20%.

That last point is the whole philosophy in one line. Claude isn’t here to replace your judgment. It’s here to clear the runway so your judgment can actually land.

I was genuinely impressed by how much this contributor packed into one image without watering anything down. If you’ve been avoiding Claude because every tutorial felt too long or too abstract, this is the shortcut. Go check the full LinkedIn post to see the original infographic and follow the mind behind it for more breakdowns like this.

”
}