← All tips
FREECLAUDE.md instruction

Parallel Agents prompt

Neo ZinoBy Neo Zino - builder of ClockedCode1 min readJun 16, 2026
INSTALL PROMPTPASTE INTO CLAUDE CODE
Add the following instruction to my global CLAUDE.md (the user-level file,
e.g. ~/.claude/CLAUDE.md - create the file if it doesn't exist).

Safety first: read my current global CLAUDE.md before changing anything. If it
already contains this instruction, or an equivalent rule about parallel tool
calls and subagent delegation, tell me what you found, change nothing, and
stop. If it clashes with or contradicts any instruction I already have, don't
append either - point out the clash, explain the trade-off, and ask me how I
want to handle it. Never remove or rewrite my existing content - only append.

Append this section exactly:

## Parallel Agents
Distinguish two kinds of parallelism. Parallel tool calls (multiple
Read/Grep/Bash in one message) are cheap - do them whenever the calls are
independent. This should be the default. Spawning subagents or agent teams is
heavier - only worth it when each agent has substantial, independent work.
Don't manufacture parallelism for small tasks, and don't spawn an agent to
re-read files already loaded in the current session.

When you're done, show me the section you added and confirm where it lives.

By default Claude Code tends to work one step at a time: read a file, then the next, then the next - slowly grinding through your task while the conversation fills up with everything it touched.

This instruction teaches it to think about parallelism. Independent reads and searches get batched into one step (cheap, instant), and genuinely separate chunks of work get handed to subagents that run at the same time and report back - so the main chat stays focused on the result, not the grind.

The rule also stops Claude from overdoing it: it won't spin up a team for a small task, or re-read files that are already loaded. The speed of a team, the focus of one.

Free tools

Config generator

Hooks Preset Generator

Pick the automations you want, and get a validated Claude Code hooks block for settings.json, grouped and merged the same way the official examples are.

Try tool
Config generator

Permissions Generator

Pick a safe starting mode and your OS, and get a validated allow/deny permissions block for settings.json in under a minute.

Try tool
Config generator

Output Style Generator

Pick a persona and a tone, and get a valid output-style file with correct frontmatter, ready to save and switch to.

Try tool
Config generator

Subagent Generator

Describe the job in plain English, pick a specialty, and get a complete subagent file ready to save.

Try tool
Config generator

MCP Config Generator

Pick the MCP servers you use and get the exact claude mcp add commands or a ready .mcp.json block, scoped and copy-pasteable.

Try tool
Config generator

Slash Command Generator

Answer 7 quick questions and get a custom Claude Code slash command with valid frontmatter, ready to drop into .claude/commands/.

Try tool
Config generator

Statusline Generator

Toggle the segments you want, watch the exact statusline render live, then copy the tested script and settings.json block.

Try tool
Config generator

settings.json Generator

Pick permission rules, hook presets, env vars, and a model override one step at a time, then copy or download the finished settings.json.

Try tool
Config generator

CLAUDE.md Generator

Answer 7 quick questions, get a tuned CLAUDE.md for your project in 30 seconds.

Try tool
Template library

Claude Code Templates

A curated library of copy-paste Claude Code templates: subagents, hooks, slash commands, settings, and CLAUDE.md starters, each one explained and pulled from a setup that gets used every day.

Try tool
Token scanner

UsageCut

Scan your Claude Code setup in 30 seconds and see exactly what is burning your tokens - bloated context, heavy MCP servers, and settings quietly draining your usage limits.

Try tool

About ClockedCode

What is ClockedCode?

A dashboard with the full curated stack - MCP servers, skills, hooks, settings, subagents, and a tuned global CLAUDE.md - plus a generator that compiles your selections into one master prompt you paste straight into Claude Code.

Who is it for?

Anyone who already uses Claude Code. You check a few boxes and paste a prompt - no scripting, no config spelunking, no terminal gymnastics required.

Which tools are in the stack?

A hand-picked set across three jobs - tools for writing better code, tools for connecting your tools, and tools for checking your work. Every one is something I actually run day to day - curated, never padded to hit a number.

One-time really means forever?

Forever. One payment unlocks lifetime access, and updates ship to you free as the ecosystem changes. No renewal, no surprise upsell.