selective-install

What problem does it solve?

SpecPowers modules vary by project and platform so installations can become bloated, inconsistent, or out of sync when teams manually copy files. Selective install enforces profile-based installation, per-module choices, and lifecycle commands so you always know what is installed and can detect or repair drift before it causes bugs.

Core Features & Use Cases

• Profile-driven installs let you pick core, developer, security, or full presets per platform and then add or exclude specific modules by running node scripts/install.js with the desired platform, profile, and module flags.
• Lifecycle commands expose list for visibility, doctor for state drift detection, repair for reinstalling corrupted or missing modules, and uninstall for conservative cleanup while keeping the state file as the single source of truth.
• Platform adapters and iron laws guarantee each install targets a single platform adapter such as Claude Code, Cursor, Gemini CLI, Kiro IDE, Codex, or OpenCode, enforce dependency chains, and keep repair and uninstall behavior predictable even when modules are excluded or modified.

Quick Start

Ask the selective install skill to install the developer profile for the kiro-ide platform and add the rules-typescript module.