skills.rest
ColdBox
ColdBoxOFFICIAL
Explore all skills by this author →
Website𝕏@coldboxGitHub

coldbox-module-development

Create reusable ColdBox modules with routes, handlers, services, and configuration.

1|Updated Apr 10, 2026
Search Tags:#forgebox#module-development#coldbox#wirebox#boxlang#moduleconfig
One-click install
npx skills add https://github.com/ColdBox/skills --skill coldbox-module-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coldbox-module-development
Source: https://github.com/ColdBox/skills/tree/main/coldbox/module-development
Command: npx skills add https://github.com/ColdBox/skills --skill coldbox-module-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ColdBox module development can be error-prone without a clear blueprint. This skill provides a complete structure for building reusable modules with ModuleConfig.cfc, box.json metadata, routing, interceptors, and WireBox bindings to ensure isolation and portability across projects.

Core Features & Use Cases

  • Modular architecture: self-contained modules with their own routes, handlers, services, and configuration.
  • ForgeBox packaging and deployment: ready-to-publish ForgeBox-ready modules.
  • Module inception and dependency management: safe composition of modules across projects.

Quick Start

Create a new module folder with ModuleConfig.cfc, a Router, and a box.json, then package and publish to ForgeBox.

Frequently Asked Questions about coldbox-module-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a reusable ColdBox module with isolated routes and handlers?▼

To create a reusable ColdBox module, build a self-contained folder with a ModuleConfig.cfc, dedicated Router, handlers, and services. This structure ensures module isolation and easy deployment across ColdBox projects.

What do I need to package a ColdBox module for ForgeBox deployment?▼

Packaging a ColdBox module for ForgeBox requires a box.json metadata file alongside your ModuleConfig.cfc. This combination provides the necessary deployment blueprint for publishing ready-to-install modules.

How does WireBox binding work within ColdBox module development?▼

WireBox bindings in ColdBox module development allow modules to manage dependency injection independently. Configuring WireBox within ModuleConfig.cfc ensures self-contained services and safe composition across different projects.

Can I use ColdBox modules with BoxLang and CFML compatibility?▼

Yes, ColdBox modules conform to BoxLang CFML compatibility standards. Building modules with ModuleConfig.cfc and interceptors ensures they function correctly within BoxLang environments.

When do I need interceptors in a ColdBox module?▼

You need interceptors in a ColdBox module when requiring event-driven architecture within self-contained routes. Configuring interceptors inside ModuleConfig.cfc allows modules to hook into application events cleanly.

Why use modular architecture for multi-module ColdBox applications?▼

Modular architecture provides self-contained isolation for multi-module ColdBox applications, preventing handler conflicts. Using ModuleConfig.cfc and independent routers ensures safe composition and portability across projects.

Related Skills

Explore More Software Engineering Skills→
ortus-docsortus-docs
16

boxlang-runtime-commandbox

Configure server.json and manage BoxLang services in a Java servlet container.

Official
Advanced
ColdBoxColdBox

coldbox-testing-integration

Run ColdBox integration tests with real handlers, services, and databases.

Official
Intermediate
ColdBoxColdBox

wirebox-di

Automate dependency injection configuration for CFML and BoxLang applications.

Official
Advanced
ColdBoxColdBox

coldbox-decorators

Extend ColdBox controllers and request contexts with CFML decorator components.

Official
Intermediate