Went Through A List Of 27 Advanced Claude Tips. These Were The First 5 I Thought Were Actually Useful

I came across Ruben Hassid's big list of 27 Claude tips and decided to go through them from the perspective of a normal user rather than just saving another “AI tips” list.

The first five had a few ideas I hadn't really thought about this way.

1. Projects aren't automatically better than normal chats

If you're doing repeat work using the same documents, a Project makes obvious sense.

But if you're trying to brainstorm something genuinely fresh, having lots of old documents/instructions sitting in the Project can influence the direction.

I've started thinking about it as:

repeatable/context-heavy task = Project

fresh exploration = new chat

2. Use expensive intelligence where the task is actually difficult

One suggestion was to start a difficult problem using the strongest Claude model, let it understand/frame the job, then potentially switch to something cheaper for the easy follow-up work.

Example:

“Analyze this business and decide our strategy” is difficult.

“Turn that strategy into three email subject lines” probably isn't equally difficult.

I wouldn't assume this saves money/quality automatically, but it's an interesting thing to test.

3. Claude can be useful for graphics even without treating it like an image generator

This one was clever.

Give Claude an infographic/design as a reference and ask it to recreate the structure as HTML with your own content.

That gives you editable text and layout instead of hoping an image model gets every word right.

Could be useful for diagrams, cheat sheets and comparison cards.

4. Stop endlessly correcting a bad conversation

We've probably all done:

“That's wrong.”

“No, that's still wrong.”

“You misunderstood again.”

The tip was to sometimes go back and edit the original instruction instead.

If the problem started because your first prompt was vague, adding another five corrective messages might be worse than simply fixing the prompt that caused it.

That seems obvious once you hear it, but I rarely see people do it.

5. Voice might actually create better prompts

Not because voice is magically better.

Because when people type, they compress everything.

When people speak, they tend to explain all the messy context:

what happened
what they've tried
what they're worried about
what they don't want
what they're unsure of

Then you can tell Claude to ask questions before answering.

I want to test typed vs spoken context on the same task because I suspect this varies a lot by person.

Those were the first 5.

There are another 22 covering connectors, long chats, Cowork, Claude Code, artifacts, research and a bunch of other things.

I'll go through 6–10 next.

Curious which of these people here actually use already, especially the edit-the-original-prompt approach.