feat: implement 'install all' with robust editor management system - …

ARCHITECTURE.md

@@ -13,7 +13,8 @@ vibe-rules/
 │   ├── commands/          # CLI command action handlers (Added)
 │   │   └── install.ts     # Action handler for the 'install' command (Added)
 │   ├── index.ts           # Main exports
-│   ├── types.ts           # Type definitions (Updated: RuleType.UNIFIED)
+│   ├── types.ts           # Type definitions (Updated: RuleType.UNIFIED, explicit editor lists, clean type validation)
+│   ├── genericTypeUtilities.ts # Reusable TypeScript utility types for validation (Added)
 │   ├── schemas.ts         # Zod schema definitions
 │   ├── llms/              # Rule definitions for package export
 │   │   ├── index.ts       # Public rule export (intentionally empty)
@@ -88,8 +89,11 @@ It handles parsing of command-line arguments, options, and delegates the executi
   - Determines the target file path based on editor type, options (`-g, --global`, `-t, --target`), and context.
   - Uses the appropriate `RuleProvider` to format and apply the rule (`appendFormattedRule`).
   - Suggests similar rule names if the requested rule is not found.
-- `install <editor> [packageName] [options]`
+- `install <editor> [packageName] [options]` (Updated)
   - Defines the CLI options and arguments for the install command.
+  - Now supports `all` as a special editor argument to install rules to all supported editors at once.
+  - **New behavior:** When `<editor>` is `all`, installs rules to all supported editors (cursor, windsurf, claude-code, codex, clinerules, zed, unified) simultaneously.
+  - Includes guardrail preventing use of `--target` option with `all` since each editor has different file structures.
   - Delegates the action to `installCommandAction` from `src/commands/install.ts`.
 
 ### src/commands/install.ts (Added)
@@ -98,12 +102,18 @@ Contains the action handler for the `vibe-rules install` command.
 
 #### Functions
 
-- `installCommandAction(editor: string, packageName: string | undefined, options: { global?: boolean; target?: string; debug?: boolean }): Promise<void>` (Exported)
+- `installCommandAction(editor: string, packageName: string | undefined, options: { global?: boolean; target?: string; debug?: boolean }): Promise<void>` (Exported, Updated)
   - Main handler for the `install` command.
-  - If `packageName` is provided, it calls `installSinglePackage` for that specific package.
-  - If `packageName` is not provided, it reads `package.json`, gets all dependencies and devDependencies, and calls `installSinglePackage` for each.
-  - Uses `getRuleProvider` to get the appropriate provider for the editor.
-  - Handles overall error reporting for the command.
+  - **New functionality:** Supports `editor` argument of `"all"` to install rules to all supported editors at once.
+  - **Multi-editor processing:** When `editor` is `"all"`, uses the explicit `ALL_SUPPORTED_EDITORS` array from `types.ts` for robust editor management.
+  - **Runtime validation:** Calls `validateAllSupportedEditorsHaveProviders()` to ensure all editors have working providers before processing.
+  - **Guardrails:** Prevents use of `--target` option with `"all"` since each editor has different file structures.
+  - **Enhanced logging:** Provides detailed progress output and summary when processing multiple editors.
+  - If `packageName` is provided, it calls `installSinglePackage` for that specific package for each editor.
+  - If `packageName` is not provided, it reads `package.json`, gets all dependencies and devDependencies, and calls `installSinglePackage` for each dependency for each editor.
+  - Uses `getRuleProvider` to get the appropriate provider for each editor.
+  - **Installation Summary:** When processing multiple editors, provides a comprehensive summary showing success/failure status and rule counts for each editor.
+  - Handles overall error reporting for the command with graceful degradation for individual editor failures.
 - `installSinglePackage(pkgName: string, editorType: RuleType, provider: RuleProvider, installOptions: { global?: boolean; target?: string; debug?: boolean }): Promise<number>`
   - Installs rules from a single specified NPM package.
   - Dynamically imports `<pkgName>/llms` using `importModuleFromCwd`.
@@ -148,6 +158,36 @@ Defines the core types and interfaces used throughout the application.
   - `UNIFIED`: "unified" - For the unified `.rules` file convention (Added)
   - `CUSTOM`: "custom" - For custom implementations
 
+#### `ALL_SUPPORTED_EDITORS` (Added)
+
+- **Explicit array of editors included in "install all" functionality**
+- **Critical for maintenance**: When adding a new editor to `RuleType`, developers **MUST** consciously decide whether to include it here
+- Contains: `[CURSOR, WINDSURF, CLAUDE_CODE, CODEX, CLINERULES, ZED, UNIFIED]`
+- **Purpose**: Ensures new editors are intentionally included or excluded from "all" operations
+
+#### `EXCLUDED_FROM_ALL_EDITORS` (Added)
+
+- **Explicit array of editors excluded from "install all" functionality**
+- Contains excluded editors with documentation of why:
+  - `ROO`: Alias for CLINERULES, avoid duplication
+  - `CUSTOM`: Custom implementations, not standardized
+- **Purpose**: Makes exclusions explicit and documented
+
+#### TypeScript Compile-Time Validation (Added)
+
+- **Automated enforcement**: Clean generic utility types ensure all `RuleType` values are accounted for
+- **Implementation**: Uses `AssertAreEqual` from `src/genericTypeUtilities.ts` to validate that the union of `ALL_SUPPORTED_EDITORS` and `EXCLUDED_FROM_ALL_EDITORS` exactly equals all `RuleType` values
+- **Compile-time safety**: Adding a new editor without updating the lists will show clear TypeScript errors
+- **Error guidance**: TypeScript errors indicate which editors are missing and need to be addressed
+- **Clean code**: Uses reusable generic utility types instead of complex inline type checking
+
+#### `validateAllSupportedEditorsHaveProviders()` (Added)
+
+- **Runtime validation helper** that ensures all editors in `ALL_SUPPORTED_EDITORS` have working providers
+- Returns `{ valid: boolean; missing: RuleType[] }`
+- **Usage**: Called during "install all" to detect configuration issues
+- **Purpose**: Prevents runtime failures by validating provider availability upfront
+
 #### `RuleProvider`
 
 - Interface that providers must implement
@@ -168,6 +208,26 @@ Defines the core types and interfaces used throughout the application.
   - `alwaysApply?`: boolean - Cursor-specific metadata.
   - `globs?`: string | string[] - Cursor-specific metadata.
 
+### src/genericTypeUtilities.ts (Added)
+
+Provides reusable TypeScript utility types for compile-time validation and type assertions.
+
+#### Generic Utility Types
+
+- `AssertIsEmpty<T>`: Ensures a type is empty (`never`). Returns `true` if empty, otherwise returns an error object with details.
+- `AssertAreEqual<T, U>`: Ensures two types are exactly equal. Returns `true` if equal, otherwise returns an error object showing the differences.
+- `Intersection<T, U>`: Gets the intersection of two types using `T & U`.
+- `Union<T, U>`: Gets the union of two types using `T | U`.
+- `ArrayIntersection<T, U>`: Gets overlapping values between two readonly arrays as union types using `Extract`.
+- `ArrayUnion<T, U>`: Combines two readonly arrays into a single union type.
+
+#### Purpose
+
+- **Reusability**: These utilities can be used throughout the codebase for type validation
+- **Clear error messages**: Assertion types provide helpful error details when validation fails
+- **Compile-time safety**: Catches type issues during development rather than runtime
+- **Clean code**: Eliminates complex inline type checking in favor of readable assertions
+
 ### src/schemas.ts (Added)
 
 Defines Zod schemas for validating rule configurations.

README.md

@@ -99,7 +99,7 @@ vibe-rules load my-rule-name cursor -t ./my-project/.cursor-rules/custom-rule.md
 Arguments:
 
 - `<name>`: The name of the rule saved in the local store (`~/.vibe-rules/rules/`).
-- `<editor>`: The target editor/tool type. Supported: `cursor`, `windsurf`, `claude-code`, `codex`, `clinerules`, `roo`.
+- `<editor>`: The target editor/tool type. Supported: `cursor`, `windsurf`, `claude-code`, `codex`, `clinerules`, `roo`, `unified`, `zed`, `all`.
 
 Options:
 
@@ -119,6 +119,12 @@ We anticipate more NPM packages will begin exporting standardized AI configurati
 Install rules _directly from NPM packages_ into an editor's configuration. `vibe-rules` automatically scans your project's dependencies or a specified package for compatible rule exports.
 
 ```bash
+# Install rules from ALL dependencies for ALL supported editors
+vibe-rules install all
+
+# Install rules from a specific package for ALL supported editors
+vibe-rules install all my-rule-package
+
 # Most common: Install rules from ALL dependencies/devDependencies for Cursor
 # Scans package.json, finds packages with 'llms' export, applies rules.
 vibe-rules install cursor
@@ -138,13 +144,16 @@ Add the `--debug` global option to any `vibe-rules` command to enable detailed d
 
 Arguments:
 
-- `<editor>`: The target editor/tool type (mandatory). Supported: `cursor`, `windsurf`, `claude-code`, `codex`, `clinerules`, `roo`.
+- `<editor>`: The target editor/tool type (mandatory). Supported: `cursor`, `windsurf`, `claude-code`, `codex`, `clinerules`, `roo`, `unified`, `zed`, `all`.
 - `[packageName]` (Optional): The specific NPM package name to install rules from. If omitted, `vibe-rules` scans all dependencies and devDependencies in your project's `package.json`.
 
 Options:
 
 - `-g, --global`: Apply to the editor's global configuration path (if supported).
-- `-t, --target <path>`: Specify a custom target file path or directory.
+- `-t, --target <path>`: Specify a custom target file path or directory. **Note:** Cannot be used with `all` editor option since each editor has different file structures.
+
+**Special Editor Option:**
+- `all`: Installs rules to ALL supported editors at once. This is perfect for setting up your entire development environment from a single command. When using `all`, rules are installed to each editor's default location using their respective formats.
 
 **How `install` finds rules:**
 
@@ -198,6 +207,24 @@ bun link
 # Now you can use 'vibe-rules' command locally
 ```
 
+### Adding Support for New Editors
+
+`vibe-rules` uses a robust system to ensure new editors are properly handled. When adding support for a new editor:
+
+1. **Add the editor to `RuleType`** in `src/types.ts`
+2. **Create a provider** implementing the `RuleProvider` interface in `src/providers/`
+3. **Update the provider factory** in `src/providers/index.ts`
+4. **Make a conscious decision** about "install all" behavior by adding the new editor to either:
+   - `ALL_SUPPORTED_EDITORS` (included in `vibe-rules install all`)
+   - `EXCLUDED_FROM_ALL_EDITORS` (excluded with documented reason)
+
+**TypeScript will enforce this workflow** - the build will fail with clear error messages if you forget to update the explicit editor lists. This ensures:
+- All editors are consciously included or excluded from "all" operations  
+- New editors don't accidentally break existing functionality
+- The reasoning for exclusions is documented
+
+See `ARCHITECTURE.md` for detailed information about the editor management system and provider interfaces.
+
 ## License
 
 MIT

src/cli.ts

@@ -242,7 +242,7 @@ program
   )
   .argument(
     "<editor>",
-    "Target editor type (cursor, windsurf, claude-code, codex, clinerules, roo)"
+    "Target editor type (cursor, windsurf, claude-code, codex, clinerules, roo, unified, zed, all)"
   )
   .argument("[packageName]", "Optional NPM package name to install rules from")
   .option(