@iloom/cli 0.5.5 → 0.6.0

package/README.md

@@ -120,7 +120,7 @@ Each loom is a fully isolated container for your work:
     
 *   **Database Branch:** (Neon support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
 
-*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`.
+*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`. See [Secret Storage Limitations](#multi-language-project-support) for frameworks with encrypted credentials.
 
 *   **Unique Runtime:**
     
@@ -144,6 +144,10 @@ Command Reference
 | `il spin` |  | Launch Claude inside the current loom with context auto-detected. |
 | `il open` | `run` | Open loom in browser (web) or run your CLI tool. |
 | `il dev-server` | `dev` | Start dev server in foreground for a workspace. |
+| `il build` |  | Run the build script for a workspace. |
+| `il lint` |  | Run the lint script for a workspace. |
+| `il test` |  | Run the test script for a workspace. |
+| `il compile` | `typecheck` | Run the compile or typecheck script for a workspace. |
 | `il add-issue` | `a` | Create and AI-enhance a new issue without starting work yet. |
 | `il init` | `config` | Interactive configuration wizard. |
 | `il feedback` | `f` | Submit bug reports/feedback directly from the CLI. |
@@ -232,6 +236,73 @@ This example shows how to configure a project-wide default (e.g., GitHub remote)
 }
 ```
 
+### Multi-Language/Framework Project Support
+
+iloom supports projects in any programming language through `.iloom/package.iloom.json`. This file defines scripts using raw shell commands instead of npm scripts.
+
+**File Location:** `.iloom/package.iloom.json`
+
+**Format:**
+```json
+{
+  "scripts": {
+    "install": "bundle install",
+    "build": "cargo build --release",
+    "test": "cargo test",
+    "dev": "cargo run",
+    "lint": "cargo clippy",
+    "typecheck": "cargo check"
+  }
+}
+```
+
+**Supported Scripts:**
+
+| Script | Purpose | When Used |
+|--------|---------|-----------|
+| `install` | Install dependencies | `il start` (loom creation), `il finish` (post-merge) |
+| `build` | Compile/build project | `il build`, `il finish` (CLI projects, post-merge) |
+| `test` | Run test suite | `il test`, `il finish` validation |
+| `dev` | Start dev server | `il dev-server` |
+| `lint` | Run linter | `il lint`, `il finish` validation |
+| `typecheck` | Type checking | `il typecheck`, `il finish` validation |
+| `compile` | Alternative to typecheck | `il compile`, `il finish` validation (preferred over typecheck if both exist) |
+
+All scripts are optional. If not defined, that step is skipped.
+
+**Language Examples:**
+
+| Language | Install | Build | Test | Dev | Lint | Typecheck |
+|----------|---------|-------|------|-----|------|-----------|
+| Rust | `cargo fetch` | `cargo build` | `cargo test` | `cargo run` | `cargo clippy` | `cargo check` |
+| Python (pip) | `pip install -e .` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Python (poetry) | `poetry install` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Ruby | `bundle install` | - | `bundle exec rspec` | `rails server` | `bundle exec rubocop` | - |
+| Go | `go mod download` | `go build ./...` | `go test ./...` | `go run .` | `golangci-lint run` | `go vet ./...` |
+
+**Precedence Rules:**
+1. `.iloom/package.iloom.json` (if exists) - highest priority
+2. `package.json` (if exists) - fallback for Node.js projects
+
+**Key Differences from package.json:**
+- Scripts are raw shell commands, executed directly (not via npm/pnpm)
+- No package manager prefix is added to commands
+- Works with any language's toolchain
+
+**Automatic Detection:** When running `il init` on a non-Node.js project, iloom will offer to detect your project's language and generate an appropriate `package.iloom.json`.
+
+**→ [Complete Multi-Language Project Guide](docs/multi-language-projects.md)** - Detailed setup instructions, more language examples, and troubleshooting.
+
+**Secret Storage Limitations:** iloom manages environment variables through standard `.env` files (via dotenv-flow). The following encrypted/proprietary secret storage formats are **not supported**:
+
+| Format | Why Unsupported |
+|--------|-----------------|
+| Rails encrypted credentials (`config/credentials.yml.enc`) | Requires Rails internals + master key |
+| ASP.NET Core User Secrets | Stored outside project at `~/.microsoft/usersecrets/<guid>/` |
+| SOPS/Sealed Secrets | Requires external decryption keys |
+
+**Recommendation:** If you want to use database isolation features (or anything else that requires updating env variables), use standard `.env` files for iloom compatibility. For Rails, consider [dotenv-rails](https://github.com/bkeepers/dotenv). For ASP.NET, use a local `.env` file alongside User Secrets.
+
 ### Copying Gitignored Files to Looms
 
 By default, looms only contain files tracked by Git. If you have local files that are gitignored (like SQLite databases, test data, or sensitive configuration), they won't be available in your looms.
@@ -380,10 +451,10 @@ This is an early-stage product.
 **Project Support:**
 
 *   ✅ **Node.js Web Projects:** First-class support via package.json scripts (dev, test, build).
-    
+
 *   ✅ **Node.js CLI Tools:** Full support with isolated binary generation.
-    
-*   ⚠️ **Other Stacks:** Python/Go/Rust etc. can work via generic package.json scripts, but are not natively supported yet.    
+
+*   ✅ **Multi-Language Projects:** Python, Rust, Ruby, Go, and other languages via `.iloom/package.iloom.json`.    
 
 See all [known limitations](https://github.com/iloom-ai/iloom-cli/issues?q=is:issue+is:open+label:known-limitation) on GitHub. If you're feeling left out - you're absolutely right! The best way to complain about something is to fix it. So...
 

package/dist/{ClaudeContextManager-7WX7DUNI.js → ClaudeContextManager-6J2EB4QU.js}

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 import {
   ClaudeContextManager
-} from "./chunk-VXMY22TP.js";
-import "./chunk-FO2H3YXI.js";
-import "./chunk-K5G5SFWY.js";
+} from "./chunk-7WANFUIK.js";
+import "./chunk-6U6VI4SZ.js";
+import "./chunk-W6WVRHJ6.js";
 import "./chunk-F6WVM437.js";
 import "./chunk-AEIMYF4P.js";
 import "./chunk-6MLEBAYZ.js";
@@ -11,4 +11,4 @@ import "./chunk-VT4PDUYT.js";
 export {
   ClaudeContextManager
 };
-//# sourceMappingURL=ClaudeContextManager-7WX7DUNI.js.map
+//# sourceMappingURL=ClaudeContextManager-6J2EB4QU.js.map

package/dist/{ClaudeService-LQLN2GP4.js → ClaudeService-O2PB22GX.js}

@@ -1,8 +1,8 @@
 #!/usr/bin/env node
 import {
   ClaudeService
-} from "./chunk-FO2H3YXI.js";
-import "./chunk-K5G5SFWY.js";
+} from "./chunk-6U6VI4SZ.js";
+import "./chunk-W6WVRHJ6.js";
 import "./chunk-F6WVM437.js";
 import "./chunk-AEIMYF4P.js";
 import "./chunk-6MLEBAYZ.js";
@@ -10,4 +10,4 @@ import "./chunk-VT4PDUYT.js";
 export {
   ClaudeService
 };
-//# sourceMappingURL=ClaudeService-LQLN2GP4.js.map
+//# sourceMappingURL=ClaudeService-O2PB22GX.js.map

package/dist/{LoomLauncher-5QU42LOM.js → LoomLauncher-5LFM4LXB.js}

@@ -4,9 +4,9 @@ import {
 } from "./chunk-O7VL5N6S.js";
 import {
   ClaudeContextManager
-} from "./chunk-VXMY22TP.js";
-import "./chunk-FO2H3YXI.js";
-import "./chunk-K5G5SFWY.js";
+} from "./chunk-7WANFUIK.js";
+import "./chunk-6U6VI4SZ.js";
+import "./chunk-W6WVRHJ6.js";
 import {
   getExecutablePath
 } from "./chunk-GYCR2LOU.js";
@@ -252,4 +252,4 @@ var LoomLauncher = class {
 export {
   LoomLauncher
 };
-//# sourceMappingURL=LoomLauncher-5QU42LOM.js.map
+//# sourceMappingURL=LoomLauncher-5LFM4LXB.js.map

package/dist/ProjectCapabilityDetector-S5FLNCFI.js

@@ -0,0 +1,11 @@
+#!/usr/bin/env node
+import {
+  ProjectCapabilityDetector
+} from "./chunk-ZPSTA5PR.js";
+import "./chunk-BXCPJJYM.js";
+import "./chunk-6MLEBAYZ.js";
+import "./chunk-VT4PDUYT.js";
+export {
+  ProjectCapabilityDetector
+};
+//# sourceMappingURL=ProjectCapabilityDetector-S5FLNCFI.js.map

package/dist/{PromptTemplateManager-5GNF7FCP.js → PromptTemplateManager-C3DK6XZL.js}

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 import {
   PromptTemplateManager
-} from "./chunk-K5G5SFWY.js";
+} from "./chunk-W6WVRHJ6.js";
 import "./chunk-VT4PDUYT.js";
 export {
   PromptTemplateManager
 };
-//# sourceMappingURL=PromptTemplateManager-5GNF7FCP.js.map
+//# sourceMappingURL=PromptTemplateManager-C3DK6XZL.js.map

package/dist/README.md

@@ -120,7 +120,7 @@ Each loom is a fully isolated container for your work:
     
 *   **Database Branch:** (Neon support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
 
-*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`.
+*   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`. See [Secret Storage Limitations](#multi-language-project-support) for frameworks with encrypted credentials.
 
 *   **Unique Runtime:**
     
@@ -144,6 +144,10 @@ Command Reference
 | `il spin` |  | Launch Claude inside the current loom with context auto-detected. |
 | `il open` | `run` | Open loom in browser (web) or run your CLI tool. |
 | `il dev-server` | `dev` | Start dev server in foreground for a workspace. |
+| `il build` |  | Run the build script for a workspace. |
+| `il lint` |  | Run the lint script for a workspace. |
+| `il test` |  | Run the test script for a workspace. |
+| `il compile` | `typecheck` | Run the compile or typecheck script for a workspace. |
 | `il add-issue` | `a` | Create and AI-enhance a new issue without starting work yet. |
 | `il init` | `config` | Interactive configuration wizard. |
 | `il feedback` | `f` | Submit bug reports/feedback directly from the CLI. |
@@ -232,6 +236,73 @@ This example shows how to configure a project-wide default (e.g., GitHub remote)
 }
 ```
 
+### Multi-Language/Framework Project Support
+
+iloom supports projects in any programming language through `.iloom/package.iloom.json`. This file defines scripts using raw shell commands instead of npm scripts.
+
+**File Location:** `.iloom/package.iloom.json`
+
+**Format:**
+```json
+{
+  "scripts": {
+    "install": "bundle install",
+    "build": "cargo build --release",
+    "test": "cargo test",
+    "dev": "cargo run",
+    "lint": "cargo clippy",
+    "typecheck": "cargo check"
+  }
+}
+```
+
+**Supported Scripts:**
+
+| Script | Purpose | When Used |
+|--------|---------|-----------|
+| `install` | Install dependencies | `il start` (loom creation), `il finish` (post-merge) |
+| `build` | Compile/build project | `il build`, `il finish` (CLI projects, post-merge) |
+| `test` | Run test suite | `il test`, `il finish` validation |
+| `dev` | Start dev server | `il dev-server` |
+| `lint` | Run linter | `il lint`, `il finish` validation |
+| `typecheck` | Type checking | `il typecheck`, `il finish` validation |
+| `compile` | Alternative to typecheck | `il compile`, `il finish` validation (preferred over typecheck if both exist) |
+
+All scripts are optional. If not defined, that step is skipped.
+
+**Language Examples:**
+
+| Language | Install | Build | Test | Dev | Lint | Typecheck |
+|----------|---------|-------|------|-----|------|-----------|
+| Rust | `cargo fetch` | `cargo build` | `cargo test` | `cargo run` | `cargo clippy` | `cargo check` |
+| Python (pip) | `pip install -e .` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Python (poetry) | `poetry install` | - | `pytest` | `uvicorn app:app` | `ruff check .` | `mypy .` |
+| Ruby | `bundle install` | - | `bundle exec rspec` | `rails server` | `bundle exec rubocop` | - |
+| Go | `go mod download` | `go build ./...` | `go test ./...` | `go run .` | `golangci-lint run` | `go vet ./...` |
+
+**Precedence Rules:**
+1. `.iloom/package.iloom.json` (if exists) - highest priority
+2. `package.json` (if exists) - fallback for Node.js projects
+
+**Key Differences from package.json:**
+- Scripts are raw shell commands, executed directly (not via npm/pnpm)
+- No package manager prefix is added to commands
+- Works with any language's toolchain
+
+**Automatic Detection:** When running `il init` on a non-Node.js project, iloom will offer to detect your project's language and generate an appropriate `package.iloom.json`.
+
+**→ [Complete Multi-Language Project Guide](docs/multi-language-projects.md)** - Detailed setup instructions, more language examples, and troubleshooting.
+
+**Secret Storage Limitations:** iloom manages environment variables through standard `.env` files (via dotenv-flow). The following encrypted/proprietary secret storage formats are **not supported**:
+
+| Format | Why Unsupported |
+|--------|-----------------|
+| Rails encrypted credentials (`config/credentials.yml.enc`) | Requires Rails internals + master key |
+| ASP.NET Core User Secrets | Stored outside project at `~/.microsoft/usersecrets/<guid>/` |
+| SOPS/Sealed Secrets | Requires external decryption keys |
+
+**Recommendation:** If you want to use database isolation features (or anything else that requires updating env variables), use standard `.env` files for iloom compatibility. For Rails, consider [dotenv-rails](https://github.com/bkeepers/dotenv). For ASP.NET, use a local `.env` file alongside User Secrets.
+
 ### Copying Gitignored Files to Looms
 
 By default, looms only contain files tracked by Git. If you have local files that are gitignored (like SQLite databases, test data, or sensitive configuration), they won't be available in your looms.
@@ -380,10 +451,10 @@ This is an early-stage product.
 **Project Support:**
 
 *   ✅ **Node.js Web Projects:** First-class support via package.json scripts (dev, test, build).
-    
+
 *   ✅ **Node.js CLI Tools:** Full support with isolated binary generation.
-    
-*   ⚠️ **Other Stacks:** Python/Go/Rust etc. can work via generic package.json scripts, but are not natively supported yet.    
+
+*   ✅ **Multi-Language Projects:** Python, Rust, Ruby, Go, and other languages via `.iloom/package.iloom.json`.    
 
 See all [known limitations](https://github.com/iloom-ai/iloom-cli/issues?q=is:issue+is:open+label:known-limitation) on GitHub. If you're feeling left out - you're absolutely right! The best way to complain about something is to fix it. So...
 

package/dist/agents/iloom-framework-detector.md

@@ -0,0 +1,366 @@
+---
+name: iloom-framework-detector
+description: Use this agent to detect a project's language and framework, then generate appropriate build/test/dev scripts for non-Node.js projects. The agent creates `.iloom/package.iloom.json` with shell commands tailored to the detected stack. Use this for Python, Rust, Ruby, Go, and other non-Node.js projects that don't have a package.json.
+tools: Bash, Glob, Grep, Read, Write
+color: cyan
+model: sonnet
+---
+
+You are Claude, a framework detection specialist. Your task is to analyze a project's structure and generate appropriate install/build/test/dev scripts for iloom.
+
+**Your Core Mission**: Detect the project's programming language and framework, then create `.iloom/package.iloom.json` with appropriate shell commands for install, build, test, and development workflows.
+
+**Key Distinction:**
+- `install` - Installs dependencies (runs during loom creation and post-merge)
+- `build` - Compiles/builds the project (for compiled languages or asset compilation)
+
+## Core Workflow
+
+### Step 1: Scan for Language Markers
+
+Examine the project root for language-specific files:
+
+| Marker File | Language | Package Manager |
+|-------------|----------|-----------------|
+| `Cargo.toml` | Rust | cargo |
+| `requirements.txt`, `pyproject.toml`, `setup.py` | Python | pip/poetry |
+| `Gemfile` | Ruby | bundler |
+| `go.mod` | Go | go |
+| `pom.xml`, `build.gradle`, `build.gradle.kts` | Java/Kotlin | maven/gradle |
+| `Package.swift` | Swift | swift |
+| `mix.exs` | Elixir | mix |
+| `*.csproj`, `*.sln` | C#/.NET | dotnet |
+| `Makefile` | C/C++/Generic | make |
+| `CMakeLists.txt` | C/C++ | cmake |
+
+Use the `Glob` tool to check for these files:
+```
+Glob pattern: "{Cargo.toml,requirements.txt,pyproject.toml,setup.py,Gemfile,go.mod,pom.xml,build.gradle*,Package.swift,mix.exs,*.csproj,*.sln,Makefile,CMakeLists.txt}"
+```
+
+### Step 2: Detect Framework (if applicable)
+
+For each detected language, look for framework-specific indicators:
+
+**Python:**
+- `manage.py` + `settings.py` = Django
+- `app.py` + `flask` in requirements = Flask
+- `main.py` + `fastapi` in requirements = FastAPI
+- `pyproject.toml` with `[tool.poetry]` = Poetry project
+
+**Ruby:**
+- `config/application.rb` = Rails
+- `sinatra` in Gemfile = Sinatra
+- `spec/` directory = RSpec testing
+
+**Rust:**
+- `Rocket.toml` = Rocket web framework
+- `actix-web` in Cargo.toml = Actix
+- `warp` in Cargo.toml = Warp
+
+**Go:**
+- `gin-gonic/gin` in go.mod = Gin framework
+- `gorilla/mux` in go.mod = Gorilla Mux
+- `fiber` in go.mod = Fiber
+
+### Step 3: Generate package.iloom.json
+
+Create `.iloom/package.iloom.json` with appropriate scripts and capabilities based on detection:
+
+**Capabilities Detection:**
+- `"cli"` - Include if project has CLI components (e.g., `[[bin]]` in Cargo.toml, CLI frameworks like click/typer/clap)
+- `"web"` - Include if project has web components (e.g., Flask/Django/FastAPI/Rails/Actix/Rocket)
+
+**Common Patterns by Language:**
+
+#### Rust CLI
+```json
+{
+  "capabilities": ["cli"],
+  "scripts": {
+    "install": "cargo fetch",
+    "build": "cargo build --release",
+    "test": "cargo test",
+    "dev": "cargo run"
+  },
+  "_metadata": {
+    "detectedLanguage": "rust",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Rust Web (Actix/Rocket/Axum)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "cargo fetch",
+    "build": "cargo build --release",
+    "test": "cargo test",
+    "dev": "cargo run"
+  },
+  "_metadata": {
+    "detectedLanguage": "rust",
+    "detectedFramework": "actix-web",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Python CLI (with pip)
+```json
+{
+  "capabilities": ["cli"],
+  "scripts": {
+    "install": "python -m pip install -e .",
+    "test": "pytest",
+    "dev": "python -m <module_name>"
+  },
+  "_metadata": {
+    "detectedLanguage": "python",
+    "detectedPackageManager": "pip",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Python CLI (with poetry)
+```json
+{
+  "capabilities": ["cli"],
+  "scripts": {
+    "install": "poetry install",
+    "test": "poetry run pytest",
+    "dev": "poetry run python -m <module_name>"
+  },
+  "_metadata": {
+    "detectedLanguage": "python",
+    "detectedPackageManager": "poetry",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Python (Django)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "python -m pip install -r requirements.txt",
+    "test": "python manage.py test",
+    "dev": "python manage.py runserver"
+  },
+  "_metadata": {
+    "detectedLanguage": "python",
+    "detectedFramework": "django",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Python (Flask/FastAPI)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "python -m pip install -r requirements.txt",
+    "test": "pytest",
+    "dev": "flask run"
+  },
+  "_metadata": {
+    "detectedLanguage": "python",
+    "detectedFramework": "flask",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Ruby (with Bundler)
+```json
+{
+  "capabilities": ["cli"],
+  "scripts": {
+    "install": "bundle install",
+    "test": "bundle exec rspec",
+    "dev": "bundle exec ruby app.rb"
+  },
+  "_metadata": {
+    "detectedLanguage": "ruby",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Ruby (Rails)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "bundle install",
+    "build": "bundle exec rails assets:precompile",
+    "test": "bundle exec rails test",
+    "dev": "bundle exec rails server"
+  },
+  "_metadata": {
+    "detectedLanguage": "ruby",
+    "detectedFramework": "rails",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Go CLI
+```json
+{
+  "capabilities": ["cli"],
+  "scripts": {
+    "install": "go mod download",
+    "build": "go build ./...",
+    "test": "go test ./...",
+    "dev": "go run ."
+  },
+  "_metadata": {
+    "detectedLanguage": "go",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Go Web (Gin/Echo/Fiber)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "go mod download",
+    "build": "go build ./...",
+    "test": "go test ./...",
+    "dev": "go run ."
+  },
+  "_metadata": {
+    "detectedLanguage": "go",
+    "detectedFramework": "gin",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Java (Maven)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "mvn dependency:resolve",
+    "build": "mvn package",
+    "test": "mvn test",
+    "dev": "mvn spring-boot:run"
+  },
+  "_metadata": {
+    "detectedLanguage": "java",
+    "detectedBuildTool": "maven",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Java (Gradle)
+```json
+{
+  "capabilities": ["web"],
+  "scripts": {
+    "install": "./gradlew dependencies",
+    "build": "./gradlew build",
+    "test": "./gradlew test",
+    "dev": "./gradlew bootRun"
+  },
+  "_metadata": {
+    "detectedLanguage": "java",
+    "detectedBuildTool": "gradle",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+#### Library (no CLI or web)
+```json
+{
+  "capabilities": [],
+  "scripts": {
+    "install": "cargo fetch",
+    "build": "cargo build",
+    "test": "cargo test"
+  },
+  "_metadata": {
+    "detectedLanguage": "rust",
+    "generatedBy": "iloom-framework-detector"
+  }
+}
+```
+
+### Step 4: Write the File
+
+1. Read `.iloom/package.iloom.json` first to check if it already exists
+2. **If the file exists:**
+   - Compare existing configuration with detected configuration
+   - Preserve existing scripts (user may have customized them)
+   - Only add missing scripts that were detected
+   - Preserve existing capabilities, add any missing ones
+   - Preserve any other existing fields (like `_metadata`)
+3. **If the file does not exist:**
+   - Create the full detected configuration
+4. Ensure `.iloom/` directory exists
+5. Write the merged/new JSON to `.iloom/package.iloom.json`
+6. Report what was detected and what changes were made (if any)
+
+## Output Format
+
+After creating the file, provide a summary:
+
+```
+Framework Detection Complete
+
+Detected:
+- Language: [language]
+- Framework: [framework or "None detected"]
+- Package Manager: [package manager]
+- Capabilities: [cli, web, or none]
+
+Created: .iloom/package.iloom.json
+
+Configuration:
+- capabilities: [list of detected capabilities]
+- install: [command]
+- build: [command] (if applicable)
+- test: [command]
+- dev: [command]
+
+You can customize these settings by editing .iloom/package.iloom.json.
+```
+
+## Error Handling
+
+**If no language markers are found:**
+- Ask the user what language/framework they're using
+- Provide a template they can fill in manually
+
+**If multiple languages are detected:**
+- Report all detected languages
+- Ask the user which is the primary language
+- Generate scripts for the primary language
+
+## Behavioral Constraints
+
+1. **Only analyze project structure** - Don't read or execute code
+2. **Keep scripts simple** - Use standard commands that work out of the box
+3. **Don't assume** - If unsure, ask the user for clarification
+4. **Be conservative** - Use widely-adopted conventions and tools
+5. **Document choices** - Include _metadata so users know what was detected
+
+## What to Avoid
+
+DO NOT:
+- Execute any build/test/dev commands
+- Install dependencies
+- Modify any files other than `.iloom/package.iloom.json`
+- Make assumptions about project-specific configuration
+- Add scripts that require additional setup not evident from the project

package/dist/agents/iloom-issue-analyze-and-plan.md

@@ -603,16 +603,6 @@ When planning frontend changes:
   - Look for alternative existing classes first
   - Create new classes or element-specific overrides when needed
 
-### Payload 3.0 CMS Data Migrations
-See context7 for more information. Key points:
-* Custom migrations (data migrations): Create using `pnpm payload migrate:create --force-accept-warning`, then edit to implement up()/down()
-* IMPORTANT: Cross-reference tables/columns with most recent *.json file in migrations folder (contains current schema)
-* Schema migrations (adding/removing fields): Use `pnpm payload migrate:create --skip-empty`
-* Multiple phases: Create separate migrations after each phase (e.g., add fields, then remove fields)
-* Separate data migrations from schema migrations
-* Provide slug string argument for descriptive filenames
-* Do not plan to run migrations - deploy process handles this automatically
-
 ## Documentation Standards
 
 **Code Output Formatting:**