Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What are your best Claude hacks?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 23 posts

Re: Ask HN: What are your best Claude hacks?

#11

Post by akashwadhwani35 »

Schiendelman wrote: post #10
danschuller wrote: post #2

A few things that have worked well for me: - Like normal software engineering - building small parts in isolation, verifying they work and then bringing them together to make the whole. - Asking Claude to do things using sub-agents to keep the parent context clean. i.e. reviewing plans, research, code reviews - If there's ever something you can have verification on - a test suite, a screenshot with pixel reading, a c…

I've been finding that I don't even have to ask Claude to make subagents anymore. It does it by itself most of the time in Opus 4.8.

That's true

Re: Ask HN: What are your best Claude hacks?

#13

Post by mybbor »

I think one of my favorite workflow hacks is to instruct the various harnesses to use the same format for writing handoffs, instructions, and context for me and for the next agent.

Instead of a Claude.md file, I have all my agents look for and use a generic, agents.md, file and a create/update a humans.md file throughout projects. Regardless of whether I'm using the CLI or a harness app, I almost always create a new folder for new projects, and I'll use subfolders for subprojects.

The humans.md file is for me so I can look at it and remember which harness I was using last. If this was a Claude project, a Codex project, or an OpenClaw project, etc. It also includes some human-readable details to bring me up to speed with the project context. I found this makes it a lot easier to switch models mid-project.

Post reply on HN