Work / Independent project
In development
Swarm Commander
A toolkit for more consistent AI-assisted development across Codex, Claude, and Kiro, starting with shared project instructions, reusable skills, and repeatable setup.
My role: Workflow design, shared instruction system, and setup tooling.
Project notes · September 2026
This is an independent work in progress, not a completed client engagement or a product available to purchase. Planned capabilities are described separately below.
Purpose
Switching coding tools can mean repeating project rules, maintaining duplicate instructions, and losing context between implementation and review.
Approach
Keep shared steering documents and skills in one repository, link them into each tool's expected locations, and define clear handoffs between development roles.
Current stage
Shared steering, seven technology skills, and tested setup/update scripts are implemented. The orchestration engine is still planned.
What Swarm Commander is
Swarm Commander is an in-development toolkit for keeping AI-assisted software work consistent across coding tools. The goal is to carry the same engineering rules, project context, and reusable guidance between Codex, Claude, and Kiro.
The longer-term direction is a structured workflow from requirements and design through implementation, independent review, and testing, with explicit handoffs between those stages.
Implemented today
- Shared steering documents and tool-specific entry points for common engineering guidance.
- Seven reusable technology skills covering Angular, Java Spring, Java JDBC, JavaScript, TypeScript, React, and Next.js.
- Symlink-based setup so supported instruction and skill locations point back to the source repositories.
- Update scripts and tests for repeatable setup, link checks, and preserving existing local files when conflicts are found.
- Role definitions and a handoff format as a foundation for future workflow automation.
Still planned
A running orchestration engine, provider-execution adapters, and automatic coordination of the complete development workflow are future work. The current toolkit does not claim to run an autonomous team of agents or provide an IDE extension.
This is an independent engineering project, not a finished commercial product. Its value today is the shared instructions and setup tooling; broader automation remains in development.
Tech stack
Have a similar project in mind?
Tell me what you're trying to build or improve. We can start with a conversation about the scope and a useful first step.
Discuss your project