Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From transformers
Guided introduction to Transformers multi-agent orchestration system — explains specialist agents, orchestrators, and workflow patterns for building, testing, and debugging software.
npx claudepluginhub shankarkakumani/transformers --plugin transformersHow this skill is triggered — by the user, by Claude, or both
Slash command
/transformers:onboardingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transformers is multi-agent orchestration for serious software development. You get a team of named specialist agents, coordinated by two orchestrators. Not a chatbot. Not a single assistant. A team.
Routes Optimus Prime invocations to skill commands for building features, fixing bugs, debugging, refactoring, researching, explaining, brainstorming, reporting, committing, and creating PRs.
Delivers orchestration patterns, hook events, and self-correction loops for AI coding agents (Claude Code, Cursor, etc.) to optimize prompt discipline and reduce correction cycles.
Orchestrates Codex agents for code implementation, file modifications, codebase research, security audits, testing, and multi-step execution workflows.
Share bugs, ideas, or general feedback.
Transformers is multi-agent orchestration for serious software development. You get a team of named specialist agents, coordinated by two orchestrators. Not a chatbot. Not a single assistant. A team.
Run /transformers:init. It creates a project context file and loads your stack and structure. That's it. Start working.
Optimus Prime — leader of the Autobots. Builder. Say optimus, build X or optimus, bugfix Y. He decomposes the work, delegates to specialists, manages approval gates, and delivers. He never writes code directly — he coordinates the team that does.
Megatron — leader of the Decepticons. Tester. Say megatron, test X. He deploys specialist testers from multiple angles simultaneously. He finds what breaks before it reaches production.
Build a feature:
optimus, build [feature description]
Full lifecycle: gather requirements, research, plan, build, review, test. Two human approval gates before any code is written.
Fix a bug:
optimus, bugfix [description]
Gather, investigate, plan, fix, verify.
Quick task — call a specialist directly:
ironhide, add a rate-limited endpoint for /api/export
bumblebee, fix the alignment on the dashboard header
ratchet, write a migration to add soft deletes to orders
Test an area:
megatron, test the checkout flow
megatron, security audit the auth module
Git work:
gitmaster, review this PR
gitmaster, set up worktrees for the auth refactor
Debug a crash:
/transformers:debug [error message or description]
Research before building:
/transformers:research [topic or question]
Transformers gets smarter per project. After each session, agents write decision rules to memory — what patterns work, what to avoid, project-specific workarounds. An index of long-term memory is loaded on every command.
After a few sessions, agents know your project. They'll know which directories to look in, which patterns you use, which gotchas exist. You don't have to re-explain.
Structured, multi-phase development work. Building features with proper planning and approval gates. Fixing bugs systematically. Running multi-angle test campaigns. Code review with a specialist reviewer.
If you're making a quick edit to one file, you don't need orchestration. If you're building something real — new feature, complex fix, comprehensive tests — this is the tool. The orchestrators decompose the work so you don't have to.