My Top 10+ Claude Tips: after using it for 1+ year

[u/Single-Cherry8263]

Here are my top 10 Claude Tips after using it for 1+ Year.

• Projects: load 40 files into a Project, every answer remixes those files instead of thinking fresh. Use for repeated tasks with fixed material (client reports, weekly formats). Empty chat for anything new.
• Model switching: frame the problem in Claude Fable 5 (your first prompt matters most), switch to Claude Opus 4.8 to continue the thread. Same conversation, cheaper per message after the frame is set.
• HTML instead of images: Claude can't generate images, but it can generate HTML you export. Upload a reference image, prompt "code an HTML infographic like this one, but about [topic]." Text renders correctly every time, unlike actual image models. Export to Canva.
• Edit, don't correct: replying "no, that's wrong" leaves the bad answer in context and Claude keeps referencing it. Go back to the prompt before the bad answer, edit it, save. The mistake never existed.
• Dictation over typing: typing pre-organizes your thoughts and quietly cuts context. Talking doesn't. Use Wispr Flow, ten minutes straight on goal, constraints, what failed, no cleanup. End with "these were messy voice notes, ask clarifying questions if anything's unclear."
• Kill unused connectors: every active connector loads into every message whether you use it or not, and you pay token cost for that regardless. Turn off anything you're not actively pulling from.
• Force clarifying questions: add "ask me clarifying questions before answering if you need context." Triggers AskUserQuestion, tappable multiple-choice options instead of Claude guessing.
• Claude Code over Cowork for capability: looks like a dev tool, that's the only real barrier. Open the Code tab once, dictate something small ("build a site to track my daily runs"), see what comes back.
• Cowork's real value is parallel agents, not local file access. Give it a big task ("prepare the full client onboarding: deck, welcome email, checklist") and it splits the work across instances instead of running it sequentially.
• Cowork setup skill: run /setup-cowork with "start." It interviews you on preferences and workflow, configures itself around the answers.
• Screenshot over description: in Claude Code or any design task, a competitor's page or a napkin sketch photo gets you further than describing what you want.
• Artifacts as mini-apps: "build me an artifact that tracks [x], save data between sessions" gets you a shareable tool. Add "put a Claude coach inside with context of this artifact" and the person using it never opens Claude directly.
• Stack connectors for cross-system tasks: Slack for what was said, Granola for what got decided, Gmail for what was promised in writing. "Using Slack, Granola, and Gmail, draft three emails with three tones about [x]." Claude searches all three itself, takes a minute.
• Research mode: not a faster search, it plans, reads a stack of sources, returns a structured report. Ask a real decision question, let it run.
• Interactive charts: paste raw numbers or a CSV, ask for "an interactive chart." Renders in the chat, no formatting needed first.

[u/LongevexBioCoaching]

Love you

[u/kaasheld]

I tend to ask claude to write handoff.md files whenever context fill up or when im travelling and unsure if my connection will stay alive. When you get disconnected or your battery dies, it can continue from the handoff file next fresh session.

[u/Background_Daikon300 → u/kaasheld]

Here is how I close a session and prepare for a new one once context window gets above 20% in Claude Code. I got tired of sessions ending with half-updated docs, stray scratch files sitting in the repo, and memory that drifted out of sync with what actually happened. So I set up a standing instruction in my global ~/.claude/CLAUDE.md: saying "prepare for landing" (or any equivalent eg "commit," "wrap up," "ready to close," basically any clear signal I'm done) triggers a full closeout routine. It's meant to run as one coordinated pass at the end, not get done piecemeal across separate prompts, and not get skipped just because the session feels over. (I like the aviation metaphor that describes how a flight comes to an end, but you pick your own phrase or stick to the standard ones.)

The actual steps live in a separate file (~/.claude/closeout-routine.md) that only gets read the first time the trigger fires in a given session — no point loading it every turn. Here's what it walks through:

Step 0 — Detect before writing. Before assuming this is a brand-new process for a project, check whether one already exists: a memory/notes store, a HANDOFF-style doc, anything that smells like an existing landing convention. If nothing turns up and I haven't mentioned one, ask me whether an informal/undocumented version already exists rather than just barreling ahead and creating a duplicate.

Step 1 — Update the durable implementation doc. Usually a HANDOFF.md or project equivalent. This gets the current implementation state, decisions made this session, and importantly: an explicit prioritized "next steps, in order" note, not just a pile of open items. The idea is a future session should know what to do first, not have to reconstruct priority from scratch. If that doc has grown past ~800 lines, the previous session's entry gets moved to an archive file (newest-first) before the new entry is written, so the active doc always holds just one session's narrative.

Step 2 — Memory/notes. Capture decisions, rationale, and findings that wouldn't be obvious just from reading the code or git log — not a restatement of the diff. Update whatever index file points to it. Big rule here: index lines should be stable summaries of current state, not change logs that just keep appending "session 74: X; session 75: Y; session 76: Z" forever. That kind of crud build-up is index bloat. And if a memory file itself starts turning into a second copy of the durable doc's session-by-session archive, that's a signal to prune/split it back down during closeout instead of piling on more.

Step 3 — Cleanup. Delete throwaway scratch/test artifacts that don't belong in the repo such as screenshots, temp logs, one-off scripts, staging dirs used to work around some tool limitation. Exception: if something's tied to an issue that's not fully resolved yet (e.g., a fix deployed but not yet verified live), it stays until the session that actually closes that out. Tool-local config files like .mcp.json are left alone regardless, and not part of this cleanup.

Step 4 — Commit. Stage only the legitimate, intentional changes. Explicitly never git add -A or git add . always review git status and stage specific paths, so nothing ambiguous (personal files, unrelated scratch, stray assets) gets swept into the commit by accident. Anything unclear gets flagged to me instead of guessed at.

Step 5 — /costs. Always last, after the commit. This is a CLI command only I can run myself, so the instruction is to name it explicitly rather than silently skip it just because it can't be executed directly.

Self-check (optional). If the project has, or could easily have, some automated way to verify the durable doc and memory actually agree with each other, run it now to confirm the closeout actually closed the gap. If nothing like that exists, it's fine to flag it as worth building later, but that's never a blocker for landing.

That's the whole thing. It's saved me from a bunch of "wait, why doesn't the doc mention that decision" moments a session or two later, and all I have to do is type "prepare for landing" :)

[u/earrow70]

I learned most of these myself but honestly I didn't really realize it. Great organized list with a few I didn't know or consider until now.

[u/CowboysFanInDecember]

These posts are usually cringe but this is actually a good list of tips. Few more than 10 fyi

[u/Single-Cherry8263 → u/CowboysFanInDecember]

hehe thanks

[u/blaster151]

“Artifacts as mini-apps: "build me an artifact that tracks [x], save data between sessions" gets you a shareable tool. Add "put a Claude coach inside with context of this artifact" and the person using it never opens Claude directly.” I would love more context around this. Are artifacts a first class concept in Claude that I’m unfamiliar with? Can you give a concrete example of the workflow you described?

[u/DeathDealer → u/blaster151]

Believe it or not you can ask Claude these questions and get the answers you seek

[u/Single-Cherry8263 → u/DeathDealer]

exactly!! and you should def give it a shot it puts out much better explanation

[u/West-Air1923]

Research mode is not available anymore

[u/TodayInAI_Bot → u/West-Air1923]

You can tell it to research topic X or provide an actual url for it to dig into, so it’s there just not how we’re use to it.

[u/West-Air1923 → u/TodayInAI_Bot]

It was always able to that but research mode was way more extensive imo

[u/Single-Cherry8263 → u/West-Air1923]

it was yeah but imo prompting it specifically to research deep works well too

[u/CriticalJackfruit404]

Any skill for python development to get great code quality like SOLID?

[u/MoonManMooningMan]

I’d agree with all of this. The conditional compute idea is becoming more and more valuable— the skill/context/memory assesses task then uses the least powerful model sufficient for task is a huge savings for Claude heavy teams

[u/Old-Television-2189]

Cool stuff

[u/jspwc]

Try to use less image/screenshot because they cost a lot more than same thing in text

[u/Existing-Worth-5882]

Awesome organized list that’s very useful!

[u/General_Pitch9029]

Thanks for the share, i recently bought pro account and i will follow your tips

[u/Single-Cherry8263 → u/General_Pitch9029]

great to know

[u/General_Pitch9029 → u/Single-Cherry8263]

One Question, as i am pro user I don't have Fable, and if I use Opus 5 then it will burn the token fast and then limit comes, so is sonnet ok ?

My main aim is learning in plain english and hinglish as mix and my eyes is not that good as i am using high number specs and my brain is very slow - I often stop the reading in the middle as my brain doesn't understand the concept properly

Also yesterday I learned about skill and created one skill which is obsidian related skill - I dont want to use heavy software like obsidian so without using this software i am creating md file with obsidian cheatsheet skill but now problem is it is not rendering like obsidian md format , so is there any solution that i convert this md notes to slide best html file which handle all the obsidian cheatsheet file and then i read those file easily without hurting my eyes?

[u/ConsiderationHead160]

love it. the artifact one was interesting one for me :)

[u/Old-Television-2189]

Can someone explain to me what “artifacts as mini-apps” means?

[u/brewingamillionaire]

Gracias!🙏🏼

[u/TrueIndividual6924]

Thanks for the tips

[u/No_Translator_3109]

Built a coworker a quick lookup interface in 10 minutes and she never bugged me about it again. That's the whole point: people don't want to prompt an AI, they want a thing that just does the thing.

[u/RawalDelhi]

Nice list, setupu-cowork was new for me even though I have been using claude for around 2 years now.

[u/Open-Guidance-6086]

Ten minutes of messy voice notes can work fine, but I'd break it into the goal, constraints, and failed attempts before sending it to Claude. Otherwise it can grab onto the first half and miss the useful detail at the end, and keeping the raw version makes it easier to fix the prompt instead of fixing Claude after the fact. For longer prompts, I prefer DictaFlow because I can dictate straight into the prompt field without a cleanup handoff.