Claude Code guides
Practical, no-fluff guides to getting more out of Claude Code: hooks, desktop notifications, and running several sessions at once. Written and published by the team behind Blooby, the desktop app that gives every Claude Code session its own mascot. Free to read, no sign-up.
Claude Code plugins: how they are really built
A plugin bundles skills, agents, hooks and MCP servers into one folder. Here is the structure, the manifest, and what 295 published plugins really ship.
WorkflowClaude Code skills: what makes one actually fire
A skill is a folder with a SKILL.md in it. Twenty frontmatter fields exist, one decides whether Claude ever loads yours. Here is what matters, measured.
ConfigClaude Code statusline: the data your script gets
Claude Code runs your statusline script with a JSON payload on stdin. Here is every field it carries, which ones can be missing, and the one that quietly goes stale.
ConfigClaude Code in WSL: what breaks and why
Running Claude Code inside WSL on a Windows machine splits your config, your history and your networking in two. Here is every seam, measured on a real setup.
HooksYour Claude Code hook is not firing: a checklist
Hooks fail quietly. Work through these eight checks in order, from the settings file Claude Code is actually reading to the exit code your command returns, and you will find it.
HooksClaude Code hooks on Windows: which shell actually runs them
A hook that works on your machine and does nothing on your colleague's is usually not your script. Claude Code picks Git Bash or PowerShell depending on what is installed, and the two disagree about your command line.
WorkflowWhat Claude Code knows about its own sessions
Claude Code keeps a small registry of every session it starts, with the pid, the working directory and the current status. It is undocumented, it is easy to read, and it lies unless you check one thing first.
WorkflowClaude Code with git worktrees
Git worktrees are the cleanest way to run several Claude Code agents on one repo at once, each on its own branch and folder, never stepping on each other.
HooksWhat every Claude Code hook event means
A reference for each Claude Code hook event (SessionStart, PreToolUse, PostToolUse, Notification, Stop, SubagentStop, PreCompact and more), with when it fires and what to use it for.
HooksClaude Code hooks: the complete guide
What Claude Code hooks are, every lifecycle event they fire on, how to configure them in settings.json, and practical examples you can copy.
NotificationsHow to get notified when Claude Code needs you (or finishes)
Stop tabbing back to check on Claude Code. Use the Notification and Stop hooks to get a desktop alert the moment a run needs your input or completes.
HooksGate tool calls with the Claude Code PreToolUse hook
The PreToolUse hook runs before Claude Code executes a tool, so it can inspect, log or block the call. Here is how to match tools and use it safely.
ConfigYour Claude Code settings.json, explained
Where Claude Code reads settings from, and the two keys that matter most day to day: permissions (what the agent may do on its own) and hooks (what runs on each event).
NotificationsSend Claude Code alerts to Slack or Discord
Wire a Claude Code hook to a Slack or Discord webhook so a run finishing, or needing you, pings a channel. Copy-paste curl examples included.
NotificationsPlay a sound when Claude Code finishes
A one-line Claude Code hook that plays a sound the moment a run finishes, on macOS, Linux and Windows, so you can look away and still know when it is done.
HooksThe Claude Code Stop hook, explained
The Stop hook fires when Claude Code finishes a turn. Here is exactly when it runs, what it receives, and copy-paste examples to log, notify or chain the next step.
WorkflowUnderstanding Claude Code subagents (the Task tool)
What subagents are in Claude Code, how the Task tool spawns them to work in parallel, and how the SubagentStop hook lets you track them finishing.
WorkflowClaude Code tips to work faster
Practical Claude Code tips: widen permissions for safe actions, run agents in parallel with worktrees, wire hooks for awareness, and stop babysitting the terminal.
WorkflowRunning multiple Claude Code sessions without losing track
Run several Claude Code agents in parallel with git worktrees and clear conventions, and keep tabs on which session needs you at any moment.