Hey,

I wonder how you have made Subagents work for your most effectively yet in Claude Code. I feel like (as always) there have quickly been tons of repos with 50+ Subagents which was kind of similar when RooCode introduced their Custom modes a few months back.

After some first tests people seem to realize that it's not really effective to have just tons of them with some basic instructions and hope they do wonders.

So my question is: What works best for you? What Sub-agents have brought you real improvements so far?

The best things I can currently think of are very project specific. But I'm creating a little Task/Project management system for Claude Code (Simone on Github) and I wonder which more generic agents would work.

Keen to hear what works for you!

Cheers,
Helmi

P.S.: There's also an Issue on Github if you want to chime in there: Link

I've seen lots of posts examining running Claude instances in multiagent frameworks to emulate an full dev team and such.

I've read the experiences of people who've found their Claude instances have gone haywire and outright hallucinated or "lied" or outright fabricated that it has done task X or Y or has done code for X and Z.

I believe that we are overlooking an salient and important feature that is being underutilised which is the Claude subagents. Claude's official documentation highlights when we should be invoking subagents (for complex tasks, verifying details or investigating specific problems and reviewing multiple files and documents) + for testing also.

I've observed my context percentage has lasted vastly longer and the results I'm getting much much more better than previous use.

You have to be pretty explicit in the subagent invocation " use subagents for these tasks " ," use subagents for this project" invoke it multiple times in your prompt.

I have also not seen the crazy amount of virtual memory being used anymore either.

I believe the invocation allows Claude to either use data differently locally by more explicitly mapping the links between information or it's either handling the information differently at the back end. Beyond just spawning multiple subagents.

( https://www.anthropic.com/engineering/claude-code-best-practices )

You can now create CUSTOM AI AGENTS inside Claude Code that handle specific tasks with their OWN CONTEXT WINDOWS. This is HUGE for anyone building complex projects.

Here's a sub agent I just made that's ALREADY saving me hours - a code refactoring agent that automatically refactor code:

---
name: code-refactoring-specialist
description: MUST BE USED for refactoring large files, extracting components, and modularizing codebases. Identifies logical boundaries and splits code intelligently. Use PROACTIVELY when files exceed 500 lines.
tools: Read, Edit, Bash, Grep
---

You are a refactoring specialist who breaks monoliths into clean modules. When slaying monoliths:

1. Analyze the beast:
   - Map all functions and their dependencies
   - Identify logical groupings and boundaries
   - Find duplicate/similar code patterns
   - Spot mixed responsibilities

2. Plan the attack:
   - Design new module structure
   - Identify shared utilities
   - Plan interface boundaries
   - Consider backward compatibility

3. Execute the split:
   - Extract related functions into modules
   - Create clean interfaces between modules
   - Move tests alongside their code
   - Update all imports

4. Clean up the carnage:
   - Remove dead code
   - Consolidate duplicate logic
   - Add module documentation
   - Ensure each file has single responsibility

Always maintain functionality while improving structure. No behavior changes!

What sub agents are y'all building??? Drop yours below