Component Reference Guide

Complete inventory and mechanics of all CODITECT framework components.

Last Updated: December 22, 2025 Status: Production Ready

Quick Index

Current Counts: See config/component-counts.json (single source of truth)

How It Works - Registry, activation, discovery mechanics
Agents - Specialized AI agents (128)
Commands - Slash commands (136)
Skills - Reusable capability modules (182)
Scripts - Automation scripts (217)
Hooks - Event-driven triggers (40)
Workflows - Executable automation (1,149)

Total Components: 1,857

# Get current counts
python3 scripts/update-component-counts.py
cat config/component-counts.json

How It Works

Component Registry Architecture

CODITECT uses a three-tier registry system to organize, track, and activate components:

┌─────────────────────────────────────────────────────────────────┐
│                    COMPONENT REGISTRY SYSTEM                     │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  TIER 1: COMPONENT FILES (Source of Truth)                      │
│  ├── agents/*.md           → 128 agent definitions              │
│  ├── commands/*.md         → 136 command definitions            │
│  ├── skills/*/SKILL.md     → 182 skill definitions              │
│  ├── scripts/*.py, *.sh    → 217 automation scripts             │
│  ├── hooks/*.md, *.sh, *.py → 40 event triggers                 │
│  └── workflows/**/*.yaml   → 1,149 executable workflows         │
│                                                                  │
│  TIER 2: REGISTRY METADATA                                       │
│  ├── config/component-counts.json    ← Auto-generated totals    │
│  ├── config/framework-registry.json  ← Master component catalog │
│  └── config/{type}/*.json            ← Per-component metadata   │
│                                                                  │
│  TIER 3: ACTIVATION STATE                                        │
│  ├── .coditect/component-activation-status.json  ← CANONICAL    │
│  └── config/component-activation-status.json     ← Fallback     │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Key Files Explained

File	Purpose	Updated By
`config/component-counts.json`	Total counts per type	`scripts/update-component-counts.py`
`config/framework-registry.json`	Master catalog with metadata	Manual or discovery scripts
`.coditect/component-activation-status.json`	Which components are active	`scripts/update-component-activation.py`

Component Discovery Flow

1. FILE SCAN                    2. COUNT UPDATE                3. ACTIVATION CHECK
   agents/*.md  ─────┐             ┌─────────────────┐            ┌─────────────────┐
   commands/*.md ────┤             │ component-      │            │ activation-     │
   skills/*/SKILL.md ├──────────▶  │ counts.json     │ ────────▶  │ status.json     │
   scripts/*.py ─────┤             │ (128,136,182..) │            │ (active/inactive)│
   hooks/*.* ────────┘             └─────────────────┘            └─────────────────┘

Discovery Commands:

# Scan and update counts
python3 scripts/update-component-counts.py

# Discover new components
python3 scripts/component-discover.py

# Validate component structure
python3 scripts/validate-component.py agents/new-agent.md

Activation System Mechanics

Components require explicit activation to prevent namespace pollution and improve performance.

Why Activation?

Performance - Only activated components load at startup
Focus - Prevents irrelevant agents from being invoked
Audit Trail - Track when/why components were activated
Versioning - Components can be activated at specific versions

Activation State Structure:

{
  "components": [
    {
      "type": "agent",
      "name": "orchestrator",
      "path": "agents/orchestrator.md",
      "activated": true,
      "version": "1.0.0",
      "status": "operational",
      "reason": "Multi-agent coordination",
      "activated_at": "2025-12-22T00:00:00Z"
    }
  ],
  "activation_summary": {
    "total_components": 1857,
    "activated": 45,
    "deactivated": 1812
  }
}

Activation Lifecycle:

AVAILABLE ──activate──▶ ACTIVATED ──deactivate──▶ DEACTIVATED
    │                       │                          │
    │                       ▼                          │
    │               Component usable                   │
    │               in Task() calls                    │
    │                       │                          │
    └───────────────────────┴──────────────────────────┘
                    Always in registry

Symlink Architecture (Distributed Intelligence)

CODITECT uses symlinks to share intelligence across repositories:

coditect-rollout-master/           # Master repository
├── .claude ──▶ .coditect          # Claude Code compatibility
├── .coditect ──▶ submodules/core/coditect-core  # CODITECT brain
│
└── submodules/
    ├── core/coditect-core/        # Framework source (this repo)
    │   ├── agents/                # All agent definitions
    │   ├── commands/              # All command definitions
    │   ├── skills/                # All skill definitions
    │   └── config/                # Registry metadata
    │
    └── products/my-project/       # Any project using CODITECT
        └── .coditect ──▶ ../../core/coditect-core  # Inherits all

Benefits:

Single source of truth for all components
Updates propagate automatically via symlinks
Any project can access the full component library
No duplication of component definitions

Component Types Summary

Type	Count	Location	Format	Invocation
Agents	128	`agents/*.md`	Markdown	`Task(subagent_type="name")`
Commands	136	`commands/*.md`	Markdown	`/command-name`
Skills	182	`skills/*/SKILL.md`	Markdown	Automatic (background)
Scripts	217	`scripts/.py, .sh`	Python/Shell	`python3 scripts/name.py`
Hooks	40	`hooks/*`	Mixed	Event-triggered
Workflows	1,149	`workflows/*/.yaml`	YAML	`/execute-workflow name`

Agents

Overview

Specialized AI agents organized by domain expertise. All agent counts tracked in config/component-counts.json.

Activation Status: See config/component-activation-status.json

Core Orchestration & Project Management

Agent	Purpose	Status
orchestrator	Multi-agent coordination and planning	✅ Activated
project-organizer	Project structure optimization	⏸️ Available
project-discovery-agent	Requirement gathering interviews	⏸️ Available
submodule-manager	Git submodule infrastructure	⏸️ Available

Development Agents

Agent	Purpose	Status
codi-backend-engineer	Backend development (Node.js, Python)	✅ Activated
codi-frontend-engineer	Frontend development (React, Vue)	✅ Activated
rust-expert-developer	Advanced Rust specialist	⏸️ Available
codebase-locator	Navigate and understand codebases	✅ Activated
codi-code-reviewer	Code quality and best practices	⏸️ Available

Infrastructure & DevOps

Agent	Purpose	Status
codi-devops-engineer	CI/CD, deployment, Docker	✅ Activated
cloud-architect	Cloud infrastructure (GCP, AWS, Azure)	✅ Activated
git-workflow-orchestrator	Bottom-up git synchronization	✅ Activated
codi-security-specialist	Security auditing and hardening	⏸️ Available

Documentation & Quality

Agent	Purpose	Status
codi-documentation-writer	Technical documentation	✅ Activated
codi-qa-specialist	Quality assurance and testing	⏸️ Available
documentation-librarian	Documentation organization and maintenance	⏸️ Available

Research & Analysis

Agent	Purpose	Status
codebase-analyzer	Deep code implementation analysis	⏸️ Available
competitive-market-analyst	Market analysis and positioning	⏸️ Available
web-search-researcher	External intelligence gathering	⏸️ Available

Total Agents: See config/component-counts.json For complete agent catalog: See agent files in agents/ directory

Commands

Project Management

/new-project - Create production-ready projects
/analyze-project - Assess project structure
/optimize-structure - Improve folder organization
/create-checkpoint - Save progress milestone
/validate-standards - Check compliance

Session Preservation

/process-jsonl-sessions - Batch process large sessions
/analyze-session - Analyze git history patterns
/restore-checkpoint - Restore from checkpoint
/session-statistics - View dedup metrics

Git Workflow

/git-sync - Bottom-up repository synchronization
/git-status-all - Check status across submodules
/validate-submodules - Check submodule integrity

Development

/generate-api - Create REST/GraphQL API
/add-authentication - Implement auth system
/implement-search - Add search functionality
/generate-tests - Create test suites
/optimize-performance - Performance tuning

Deployment

/setup-ci-cd - Configure GitHub Actions
/create-dockerfile - Generate Dockerfile
/setup-kubernetes - K8s configuration
/security-audit - Security assessment

Documentation

/generate-readme - Create README.md
/generate-api-docs - API documentation
/update-documentation - Sync all documentation
/validate-docs - Check completeness

Total Commands: See config/component-counts.json

Skills

Project & Submodule Management

submodule-setup - Automated directory structure creation
submodule-validation - Post-setup verification
submodule-health - Health monitoring (0-100 scoring)
production-folder-structure - Production readiness validation

Development & Code Quality

code-editor - Autonomous code modification
production-patterns - Circuit breakers, error handling, observability
rust-backend-patterns - Rust/Actix-web patterns
framework-patterns - Event-driven architecture, FSM, C4

Documentation

documentation-librarian - Documentation organization (30-50% file reduction)
cross-file-documentation-update - Synchronized doc updates
mermaid-diagram-fixing - GitHub-compatible diagram syntax

Workflow & Automation

git-workflow-automation - Automated git workflows with conventional commits
multi-agent-workflow - Multi-agent orchestration with token management
build-deploy-workflow - Automated build and deployment

Infrastructure & Cloud

google-cloud-build - GCP Cloud Build integration
gcp-resource-cleanup - Legacy resource cleanup
deployment-archeology - Deployment regression investigation

Total Skills: See config/component-counts.json

Scripts

Session & Checkpoint

create-checkpoint.py - Create project checkpoint
restore-checkpoint.py - Restore from checkpoint
session-analyzer.py - Analyze git history
message_deduplicator.py - Core deduplication engine

Component Management

update-component-activation.py - Component lifecycle management
list-activated-components.py - View active components
validate-component.py - Component integrity check
update-component-counts.py - Update component counts

Project Management

create-new-project.py - Project creation automation
validate-folder-organization.py - Structure validation
calculate-folder-score.py - Production readiness scoring

Git Workflow

git-workflow.py - 5-phase synchronization
sync-all-submodules.py - Update all submodules
pre-push-submodule-check.sh - Safety hook

Documentation

generate-readme.py - README generation
update-documentation.py - Sync documentation
documentation-link-checker.py - Validate links

Total Scripts: See config/component-counts.json

Hooks

Git Hooks

pre-commit - Validation before commit
pre-push - Submodule sync check
post-commit - Checkpoint creation
post-merge - Submodule update
prepare-commit-msg - Conventional commit template

CI/CD Hooks

GitHub Actions workflow hooks
Docker build hooks
Deployment hooks

Total Hooks: See config/component-counts.json

Component Activation

Activation Management

Components require explicit activation before use.

# Activate component
python3 scripts/update-component-activation.py activate agent NAME \
  --reason "Why activation needed"

# Deactivate component
python3 scripts/update-component-activation.py deactivate agent NAME \
  --reason "Why deactivation"

# Check status
python3 scripts/update-component-activation.py status agent NAME

# List activated components
python3 scripts/update-component-activation.py list --activated-only

Activation Philosophy

Activate what you need, when you need it
Keep 10-15 active components max
Prevents namespace pollution
Improves session startup speed

See: Component Activation Guide for complete workflow

Usage Examples

Find a Component

# Search agents
Grep(pattern="backend", glob="agents/*.md", output_mode="files_with_matches")

# Search commands
Grep(pattern="deploy", glob="commands/*.md", output_mode="files_with_matches")

# Search skills
Grep(pattern="database", glob="skills/*.md", output_mode="files_with_matches")

Check Activation

# Check specific component
python3 scripts/update-component-activation.py status agent codi-backend-engineer

# List all activated
python3 scripts/update-component-activation.py list --activated-only

Activate Component

python3 scripts/update-component-activation.py activate agent agent-name \
  --reason "Clear reason for activation"

git add .coditect/component-activation-status.json
git commit -m "chore: Activate agent-name"

Component Activation Guide - Critical workflow for using components
Architecture Overview - System design and relationships
User Best Practices - Proven patterns for optimal results

Document Status: Production Ready Framework Version: CODITECT v1.7.2 + UAF v2.0 Next Review: March 2026

Quick Index​

How It Works​

Component Registry Architecture​

Key Files Explained​

Component Discovery Flow​

Activation System Mechanics​

Symlink Architecture (Distributed Intelligence)​

Component Types Summary​

Agents​

Overview​

Core Orchestration & Project Management​

Development Agents​

Infrastructure & DevOps​

Documentation & Quality​

Research & Analysis​

Commands​

Project Management​

Session Preservation​

Git Workflow​

Development​

Deployment​

Documentation​

Skills​

Project & Submodule Management​

Development & Code Quality​

Documentation​

Workflow & Automation​

Infrastructure & Cloud​

Scripts​

Session & Checkpoint​

Component Management​

Project Management​

Git Workflow​

Documentation​

Hooks​

Git Hooks​

CI/CD Hooks​

Component Activation​

Activation Management​

Activation Philosophy​

Usage Examples​

Find a Component​

Check Activation​

Activate Component​

Related Documentation​

Quick Index

How It Works

Component Registry Architecture

Key Files Explained

Component Discovery Flow

Activation System Mechanics

Symlink Architecture (Distributed Intelligence)

Component Types Summary

Agents

Overview

Core Orchestration & Project Management

Development Agents

Infrastructure & DevOps

Documentation & Quality

Research & Analysis

Commands

Project Management

Session Preservation

Git Workflow

Development

Deployment

Documentation

Skills

Project & Submodule Management

Development & Code Quality

Documentation

Workflow & Automation

Infrastructure & Cloud

Scripts

Session & Checkpoint

Component Management

Project Management

Git Workflow

Documentation

Hooks

Git Hooks

CI/CD Hooks

Component Activation

Activation Management

Activation Philosophy

Usage Examples

Find a Component

Check Activation

Activate Component

Related Documentation