Claude Clue #17: Don't Wait! Keep Moving While Claude Works Patience is a virtue when working with AI, but sometimes you don't actually have to wait.
Claude Clue #16: Stop Staring and Let Claude Ding You Small automations that fire at specific points in Claude's lifecycle. A simple example: playing a sound!
Claude Clue #15: Skills Are Just Files Your Model Can Find A skill is essentially a file that your model can access on demand to tailor its behavior for a specific task.
Claude Clue #14: Skills Focus, Hooks Enforce Skills are reusable prompts, hooks are code you can run to stop or alter the model's behavior.
Claude Clue #13: Know Your Limits (And Have a Backup Plan) Here's a fun way to start your work week: burning through 80% of your weekly Claude usage by Tuesday morning!
Claude Clue #12: Let Claude Spawn More Claudes Claude Code can spin up multiple Claudes to work in parallel, and it is genuinely one of those features that feels a bit like magic!
Claude Clue #11: What Hides Behind the '/' The `/` menu in Claude Code has quietly become a treasure chest.
Claude Clue #10: Give Your Codebase a Health Checkup Your codebase accumulates tech debt. It doesn't matter if humans wrote it, AI wrote it, or some messy combination of both.
Claude Clue #9: Let Your Models Fight Each Other One of the most useful things I've found is putting models in adversarial roles against each other!
Claude Clue #8: Train Your Model on Today, Not Yesterday Claude's training data has a cutoff date, which means the libraries it "remembers" are frozen in time—security flaws and all.