vanzan01

Claude Code Sub Agent Collective β€” Development skill for Claude Code

Development community

🧠 Context Engineering Research - Not just another agent collection, but using research and context engineering to function as a collective.

How to install Claude Code Sub Agent Collective

This entry records only its repository, not the path inside it, so there is no exact command to give. Open vanzan01/claude-code-sub-agent-collective and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Sub Agent Collective does

🧠 Context Engineering Research - Not just another agent collection, but using research and context engineering to function as a collective. Hub-and-spoke coordination through Claude Code.

Alternatives in Development

  • OpenAI Codex CLI β€” (Rust implementation) 67.8k β˜…
  • Scientific Agent Skills β€” A set of ready to use Agent Skills for research, science, engineering, analysis, finance and writing 18.7k β˜…
  • Research Codebase β€” You are tasked with conducting comprehensive research across the codebase to answer user questions by spawning 10k β˜…

README

Claude Code Sub-Agent Collective

[![npm version](https://badge.fury.io/js/claude-code-collective.svg)](https://badge.fury.io/js/claude-code-collective) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

vanzan01%2Fclaude-code-sub-agent-collective | Trendshift

**Experimental NPX installer for TDD-focused AI agents**

This installs a collection of AI agents designed for Test-Driven Development and rapid prototyping. It's experimental, opinionated, and I built it to speed up my own MVP development work.

What this installs

npx claude-code-collective init

You get 30+ specialized agents that enforce TDD methodology and try to be smarter about using real documentation instead of guessing.

Why this exists

I got tired of:

  • AI giving me code without tests
  • Having to manually look up library documentation
  • Inconsistent development approaches across projects
  • Breaking down complex features manually

So I built agents that:

  1. Write tests first, always (RED β†’ GREEN β†’ REFACTOR)
  2. Use Context7 to pull real documentation
  3. Route work to specialists based on what needs doing
  4. Break down complex requests intelligently

What you get after installation

Core Implementation Agents (TDD-enforced)

  • @component-implementation-agent - UI components with tests and modern patterns
  • @feature-implementation-agent - Business logic with comprehensive testing
  • @infrastructure-implementation-agent - Build systems with testing setup
  • @testing-implementation-agent - Test suites that actually test things
  • @polish-implementation-agent - Performance optimization with preserved tests

Quality & Validation

  • @quality-agent - Code review and standards checking
  • @devops-agent