@dedesfr/prompter 0.8.20 → 0.8.21

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # CHANGELOG
 
+## [0.8.21] - 2026-05-08
+
+### 🔄 Changed
+- **project-orchestrator Skill**: Refined Caddy web server setup guidance for better multi-project support
+  - Changed from per-project embedded Caddy to standalone host-level Caddy recommendation
+  - Standalone Caddy owns ports 80/443 globally and terminates TLS for all domains
+  - Each project now exposes only internal ports (e.g., 3001, 3002) instead of forwarding 80/443
+  - Prevents port conflicts when users add more projects over time
+  - Updated plan summary and recommended next steps with proper Caddyfile routing examples
+
 ## [0.8.20] - 2026-05-08
 
 ### 🔄 Changed

package/dist/cli/index.js

@@ -16,7 +16,7 @@ const program = new Command();
 program
     .name('prompter')
     .description('Enhance prompts directly in your AI coding workflow')
-    .version('0.8.20');
+    .version('0.8.21');
 program
     .command('init')
     .description('Initialize Prompter in your project')

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@dedesfr/prompter",
-    "version": "0.8.20",
+    "version": "0.8.21",
     "description": "Enhance prompts directly in your AI coding workflow",
     "type": "module",
     "main": "dist/index.js",

package/skills/project-orchestrator/SKILL.md

@@ -303,9 +303,28 @@ When Docker is used and a web server or reverse proxy is needed (e.g., for Larav
 - **Always use Caddy** as the web server and reverse proxy -- do NOT use or recommend Nginx or Apache.
 - Caddy automatically handles HTTPS (via Let's Encrypt or ZeroSSL) in production with zero extra configuration.
 - For local development, Caddy serves HTTP by default -- no certificate setup needed.
-- Add a `Caddyfile` at the project root and a `caddy` service in `docker-compose.yml`.
 - Mention Caddy in the final plan summary under the Docker/web server row and in the recommended next steps.
 
+**Always use a standalone host-level Caddy** -- do NOT embed Caddy inside a project's `docker-compose.yml`. Even for a single project today, users commonly add more projects later, and a per-project Caddy would conflict on ports 80/443.
+
+The correct setup:
+
+1. **One standalone Caddy on the host** (installed directly or in its own `docker-compose.yml` folder) owns ports 80/443 and terminates TLS for all domains.
+2. **Each project exposes only an internal port** (e.g., `3001`, `3002`) -- no `ports: - "80:80"` in their `docker-compose.yml`.
+3. The host Caddyfile routes by domain:
+
+```caddy
+project-a.com {
+    reverse_proxy localhost:3001
+}
+
+project-b.com {
+    reverse_proxy localhost:3002
+}
+```
+
+Include this setup in the final plan summary and recommended next steps.
+
 ### Laravel + Docker Guidelines
 
 When the user chooses a Laravel stack (Bundle 3, 4, or 5) with Docker:

package/src/cli/index.ts

@@ -18,7 +18,7 @@ const program = new Command();
 program
   .name('prompter')
   .description('Enhance prompts directly in your AI coding workflow')
-  .version('0.8.20');
+  .version('0.8.21');
 
 program
   .command('init')