coldbox-app-layouts

Select and scaffold ColdBox application layouts using flat, boxlang, or modern skeletons.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ColdBox/skills --skill coldbox-app-layouts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coldbox-app-layouts
Source: https://github.com/ColdBox/skills/tree/main/coldbox/app-layouts
Command: npx skills add https://github.com/ColdBox/skills --skill coldbox-app-layouts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers choose, scaffold, and migrate ColdBox application layouts so projects have the correct directory separation, engine compatibility, and deployment posture for their needs.

Core Features & Use Cases

  • Provides clear comparisons between flat, boxlang, and modern skeletons and their tradeoffs for compatibility, security, and frontend tooling.
  • Documents directory maps, scaffold commands, server.json alias requirements, and testing mapping expectations for each layout.
  • Guides migrations between layouts with step-by-step moves of handlers, config, assets, and test adjustments for real-world project upgrades.

Quick Start

Run the ColdBox CLI to scaffold a new app using your preferred skeleton, for example: box coldbox create app name=myApp skeleton=boxlang.

Frequently Asked Questions about coldbox-app-layouts

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

FAQPage Schema
What is the difference between flat, boxlang, and modern ColdBox app layouts?

ColdBox app layouts differ in directory separation, engine compatibility, and frontend tooling support. Flat offers simple structure, boxlang targets BoxLang engine compatibility, and modern provides web-root separation for enhanced security and deployment posture.

How do I scaffold a new ColdBox application using a specific skeleton?

To scaffold a ColdBox application, run the ColdBox CLI command with your preferred skeleton, such as `box coldbox create app name=myApp skeleton=boxlang`. This generates the project structure with correct directory mapping and server.json aliasing.

How do I migrate a ColdBox project between different layouts?

Migrating between ColdBox layouts involves step-by-step moves of handlers, config, and assets, followed by test mapping adjustments. This ensures the project upgrade maintains correct directory separation and engine compatibility.

Does ColdBox layout scaffolding require web-root separation and testing mapping?

Yes, ColdBox layout scaffolding satisfies web-root separation for security and requires testing mapping adjustments. The modern skeleton specifically provides web-root separation, while all layouts establish testing mapping expectations.

What's the best way to structure ColdBox project files for engine compatibility?

The best way to structure ColdBox project files is selecting the boxlang skeleton for BoxLang engine compatibility or the modern skeleton for web-root separation. Use the CLI scaffold commands to generate the correct directory maps and server.json aliasing.

When should I not use the modern ColdBox skeleton for my project?

You should avoid the modern ColdBox skeleton if your project requires simple flat structure without web-root separation, or if you need specific BoxLang engine compatibility features best served by the boxlang skeleton layout.