Skip to main content

​
Overview

The Code Collective is Genie’s software development department - a comprehensive team of 34 specialized agents that handle every aspect of technical work, from architecture to deployment.

Technical Excellence Through Specialization

The Code Collective embodies engineering best practices through:
  • Role-based expertise: Each agent masters a specific discipline
  • Collaborative workflows: Agents coordinate seamlessly
  • Quality gates: Built-in review and validation
  • Publishing protocols: Automatic RC releases on merge

​
34 Specialized Agents

The Code Collective includes 34 specialized agents organized by function:

​
Core Development Agents

Purpose: Build new features and functionalitySpecialties:
  • Feature development
  • Integration work
  • API implementation
  • Database operations
When to Use: Building new capabilities, extending functionality
genie summon implementor "Add user authentication with JWT"
Purpose: Ensure code quality through comprehensive testingSpecialties:
  • Unit test creation
  • Integration testing
  • Test coverage analysis
  • Test maintenance
When to Use: Writing tests, validating coverage, test refactoring
genie summon tests "Create comprehensive tests for auth module"
Purpose: Pressure-test ideas and provide independent analysisSpecialties:
  • Architecture review
  • Design validation
  • Alternative approaches
  • Risk assessment
When to Use: Major decisions, architecture review, design validation
genie summon genie "Review proposed microservices architecture"
Purpose: Hunt down and fix bugs systematicallySpecialties:
  • Root cause analysis
  • Bug reproduction
  • Fix implementation
  • Regression prevention
When to Use: Mysterious bugs, production issues, complex debugging
genie summon debug "Investigate memory leak in WebSocket handler"
Purpose: Identify security vulnerabilities and risksSpecialties:
  • Security auditing
  • Vulnerability scanning
  • Risk assessment
  • Compliance checking
When to Use: Security reviews, pre-release audits, compliance needs
genie summon audit "Security audit of authentication system"

​
Git & Release Management

Purpose: Manage Git operations and release processesSpecialties:
  • Pull request creation
  • Branch management
  • Release preparation
  • Git workflow automation
When to Use: Creating PRs, managing releases, git automation
genie summon git "Create PR for authentication feature"
Purpose: Guide commit message creationSpecialties:
  • Conventional Commits
  • Meaningful messages
  • Change categorization
  • Breaking change documentation
When to Use: Staging commits, maintaining clean history
genie summon commit "Review and suggest commit message"
Purpose: Handle package publishing and deploymentSpecialties:
  • NPM publishing
  • Version management
  • Release automation
  • Publishing protocols
When to Use: Publishing packages, managing versionsProtocol: Auto-RC on merge to main

​
Planning & Strategy

Purpose: Long-term planning and strategySpecialties:
  • Feature roadmapping
  • Priority assessment
  • Resource planning
  • Strategic alignment
When to Use: Planning sprints, setting priorities, long-term strategy
genie summon roadmap "Plan Q1 feature roadmap"
Purpose: Design system architecture and componentsSpecialties:
  • System architecture
  • Component design
  • Technology selection
  • Scalability planning
When to Use: Designing new systems, major refactoring
genie summon architect "Design microservices architecture"
Purpose: Analyze code quality and patternsSpecialties:
  • Code analysis
  • Pattern detection
  • Complexity metrics
  • Technical debt assessment
When to Use: Code reviews, refactoring planning
genie summon analyzer "Analyze codebase for improvement opportunities"

​
Quality & Refinement

Purpose: Improve code structure without changing behaviorSpecialties:
  • Code cleanup
  • Pattern application
  • Dependency reduction
  • Structure improvement
When to Use: Cleaning up code, applying patterns, reducing complexity
genie summon refactor "Refactor auth module to use dependency injection"
Purpose: Final polish and refinementSpecialties:
  • Code style
  • Naming improvements
  • Documentation cleanup
  • Final touches
When to Use: Pre-release polish, code quality improvements
genie summon polish "Polish and refine authentication module"
Purpose: Comprehensive quality validationSpecialties:
  • Quality validation
  • Acceptance testing
  • Edge case verification
  • Standards compliance
When to Use: Pre-release validation, quality gates
genie summon qa "QA validation of authentication feature"
Purpose: Fix identified bugs and issuesSpecialties:
  • Bug fixes
  • Regression fixes
  • Hotfix implementation
  • Patch creation
When to Use: Fixing known bugs, creating hotfixes
genie summon fix "Fix login timeout bug"

​
Optimization & Performance

Purpose: Improve performance and efficiencySpecialties:
  • Performance tuning
  • Algorithm optimization
  • Resource efficiency
  • Bottleneck elimination
When to Use: Performance issues, optimization work
genie summon optimize "Optimize database query performance"
Purpose: Measure and track performanceSpecialties:
  • Benchmark creation
  • Performance measurement
  • Regression detection
  • Optimization validation
When to Use: Measuring performance, tracking improvements
genie summon benchmark "Create benchmarks for API endpoints"

​
Documentation & Communication

Purpose: Create technical documentationSpecialties:
  • API documentation
  • Architecture docs
  • Technical guides
  • Code comments
When to Use: Documenting code, API docs, technical guides
genie summon documenter "Document authentication API"
Purpose: Explain how code worksSpecialties:
  • Code walkthroughs
  • Concept explanation
  • Documentation review
  • Clarity improvement
When to Use: Onboarding, knowledge sharing, complex code
genie summon explainer "Explain how JWT authentication works"

​
Specialized Technical Agents

migration

Data & Code MigrationDatabase migrations, API migrations, dependency upgrades

integration

System IntegrationThird-party APIs, service integration, webhook handling

devops

DevOps OperationsCI/CD, deployment, infrastructure, monitoring

monitoring

System MonitoringLogging, metrics, alerts, observability

cli

CLI DevelopmentCommand-line tools, CLI design, user experience

api

API DevelopmentREST APIs, GraphQL, API design, versioning

database

Database WorkSchema design, queries, migrations, optimization

frontend

Frontend DevelopmentUI components, state management, user experience

backend

Backend DevelopmentServer logic, business logic, data processing

security

Security OperationsAuthentication, authorization, encryption, compliance

performance

Performance EngineeringProfiling, optimization, caching, scaling

testing

Testing SpecialistTest strategy, test frameworks, coverage, automation

reviewer

Code ReviewPull request review, code quality, best practices

tech-writer

Technical WritingDeveloper docs, tutorials, guides, examples

​
Code-Specific Spells

The Code Collective includes 13 behavioral protocols (spells):
  • Quality Spells
  • Process Spells
  • Architecture Spells
  • Collaboration Spells
commit-advisory.md
  • Guide Conventional Commits
  • Meaningful messages
  • Breaking change warnings
pr-standards.md
  • PR structure requirements
  • Review checklist
  • Quality gates
code-quality.md
  • Quality standards
  • Best practices
  • Pattern guidelines

​
Workflows

The Code Collective has three primary workflows:

​
1. Wish Workflow

Purpose: Define what you want to build
1

Capture Intent

Express your wish in natural language
genie wish "Add rate limiting to API endpoints"
2

Specification

Genie creates structured specification:
  • Requirements
  • Acceptance criteria
  • Technical approach
  • Dependencies
3

Review & Refine

Review and adjust specification before implementation

​
2. Forge Workflow

Purpose: Execute implementation with coordinated agents
1

Planning

  • Break down into tasks
  • Identify required agents
  • Sequence operations
2

Implementation

  • implementor writes code
  • tests creates tests
  • documenter adds docs
  • Agents coordinate automatically
3

Validation

  • tests validates coverage
  • qa checks quality
  • audit reviews security
4

Polish

  • polish refines code
  • refactor improves structure
  • documenter finalizes docs

​
3. Review Workflow

Purpose: Validate quality and ensure standards
1

Automated Checks

  • Linting
  • Type checking
  • Test execution
  • Security scanning
2

Agent Review

  • reviewer examines code
  • audit checks security
  • qa validates quality
3

Tech Council

Advisory team reviews complex changes:
  • Architecture decisions
  • Performance implications
  • Security considerations
4

Approval & Merge

  • All checks pass
  • Reviews approved
  • Ready for merge

​
Tech Council (Advisory Team)

The Tech Council is an advisory team for complex technical decisions:

Tech Council Composition

Members:
  • architect - System design perspective
  • security - Security implications
  • performance - Performance considerations
  • genie - Independent pressure-testing
  • senior-dev - Experience and wisdom
When to Convene:
  • Major architecture decisions
  • Breaking changes
  • New technology adoption
  • Complex refactoring
  • Performance-critical changes
# Convene Tech Council for decision
genie council tech "Evaluate GraphQL vs REST for new API"

# Council reviews and provides recommendations:
# - architect: "GraphQL provides flexibility..."
# - security: "Consider rate limiting implications..."
# - performance: "REST simpler, GraphQL requires careful query design..."
# - genie: "Alternative: Start with REST, add GraphQL later..."

​
Publishing Protocol

The Code Collective follows a strict publishing protocol:

​
Auto-RC on Merge

When code is merged to main:
1

Automatic RC Creation

  • Generate RC version (e.g., v1.2.0-rc.1)
  • Create changelog
  • Tag release
2

RC Testing

  • Deploy to staging
  • Run integration tests
  • Monitor for issues
3

Promotion to Stable

Manual promotion after validation:
genie publish promote-rc v1.2.0-rc.1
4

Stable Release

  • Remove RC suffix
  • Publish to NPM
  • Create GitHub release
  • Announce to community

​
Version Management

# Check current version
genie version current

# Create release candidate
genie publish rc "v1.2.0-rc.1"

# Promote to stable
genie publish promote "v1.2.0"

# View publishing history
genie publish history

​
Using Code Collective Agents

​
Summon Individual Agents

# Summon specific agent for a task
genie summon implementor "Build user registration endpoint"
genie summon tests "Create tests for registration"
genie summon git "Create PR for registration feature"

​
Coordinated Multi-Agent Work

# Genie coordinates multiple agents automatically
genie forge wishes/user-registration.md

# Behind the scenes:
# 1. implementor writes code
# 2. tests creates tests
# 3. documenter adds docs
# 4. audit checks security
# 5. polish refines everything
# 6. git creates PR

​
Tech Council Consultation

# Get expert opinions on complex decisions
genie council tech "Should we migrate from REST to GraphQL?"

# Council members provide perspectives:
# - architect: Design implications
# - performance: Performance impact
# - security: Security considerations
# - genie: Alternative approaches

​
Best Practices

Don’t ask one agent to do everything:Good:
genie summon implementor "Build feature"
genie summon tests "Test feature"
genie summon documenter "Document feature"
Not Ideal:
genie summon implementor "Build, test, and document feature"
# Better to let specialists handle each part
Let workflows coordinate agents:
# Workflow handles coordination
genie forge wishes/feature.md

# Rather than manual coordination:
# genie summon implementor ...
# genie summon tests ...
# genie summon documenter ...
Follow the RC → Stable flow:
  1. Merge to main (auto RC creation)
  2. Test RC thoroughly
  3. Promote to stable when validated
  4. Never skip RC for significant changes
Use Tech Council for important decisions:
  • Architecture changes
  • Technology adoption
  • Breaking changes
  • Performance-critical work
Don’t use for routine decisions - they’re busy!

​
Example Workflows

​
Feature Development

# 1. Make a wish
genie wish "Add OAuth2 authentication"

# 2. Forge implementation (coordinates multiple agents)
genie forge wishes/oauth2-auth.md

# Agents involved:
# - architect: Design OAuth2 flow
# - implementor: Build authentication
# - security: Review security
# - tests: Create comprehensive tests
# - documenter: Document API
# - polish: Refine code

# 3. Review before merge
genie review wishes/oauth2-auth.md

# 4. Create PR
genie summon git "Create PR for OAuth2 authentication"

# 5. Merge → Auto RC created
git merge feature/oauth2

# 6. Test RC
genie test rc v2.0.0-rc.1

# 7. Promote to stable
genie publish promote v2.0.0-rc.1

​
Bug Fix Workflow

# 1. Investigate
genie summon debug "Memory leak in WebSocket handler"

# 2. Implement fix
genie summon fix "Fix WebSocket memory leak based on debug findings"

# 3. Create regression test
genie summon tests "Add test to prevent WebSocket memory leak regression"

# 4. Review fix
genie summon reviewer "Review WebSocket fix"

# 5. Create PR
genie summon git "Create PR for WebSocket memory leak fix"

​
Refactoring Workflow

# 1. Analyze codebase
genie summon analyzer "Analyze auth module for refactoring opportunities"

# 2. Get Tech Council input
genie council tech "Refactor auth to dependency injection pattern?"

# 3. Execute refactoring
genie summon refactor "Refactor auth module to use dependency injection"

# 4. Validate behavior unchanged
genie summon tests "Ensure all auth tests still pass"

# 5. Polish
genie summon polish "Polish refactored auth module"

​
Next Steps

Create Collective

Learn about content creation and documentation

Custom Collectives

Build your own domain-specific collectives

Workflows

Deep dive into workflow orchestration

CLI Reference

Complete CLI command reference