What are the steps to reproduce this issue?
- Create a new ColdBox app using the flat skeleton:
coldbox create app name=myApp skeleton=flat
- Open the generated
readme.md in the project root
- Search for references to
lib/
What happens?
The generated readme.md contains multiple references to a lib/ directory that doesn't exist in the flat skeleton. The flat skeleton installs coldbox and testbox directly into the webroot, not into a lib/ subfolder.
Incorrect references appear in these places:
### Key Directories
...
- **`lib/`** - Third-party frameworks installed by CommandBox
```bash
box install
...
This command reads `box.json` and installs:
- **ColdBox** framework to `lib/coldbox/`
- **TestBox** testing framework to `lib/testbox/`
├── 📂 lib/ # Framework libraries
│ ├── coldbox/ # ColdBox framework
│ └── testbox/ # TestBox testing framework
Any logs, error output, etc?
This caused Gemini 2.5 to give wrong advice when asked about the project structure:
It seems there's a slight misunderstanding regarding the exact location of the coldbox framework files within your project. According to the readme.md file in your project, the ColdBox framework is installed into the lib/coldbox/ directory, not directly in the project root.
What versions are you using?
Operating System: Windows 11 Pro 25H2
Package Version: 8.12.0+30
What are the steps to reproduce this issue?
coldbox create app name=myApp skeleton=flatreadme.mdin the project rootlib/What happens?
The generated
readme.mdcontains multiple references to alib/directory that doesn't exist in the flat skeleton. The flat skeleton installscoldboxandtestboxdirectly into the webroot, not into alib/subfolder.Incorrect references appear in these places:
Any logs, error output, etc?
This caused Gemini 2.5 to give wrong advice when asked about the project structure:
What versions are you using?
Operating System: Windows 11 Pro 25H2
Package Version: 8.12.0+30