feat: interactive use command support

Author: lucatume

README.md

@@ -175,18 +175,47 @@ Before you can do anything productive with `slic`, you need to tell it which
 project you wish to use and then you can initialize the project, run tests, and
 execute other commands to your heart's content!
 
-Assuming you have a plugin called `the-events-calendar` in the plugins directory
-where you ran `slic here`, you can tell `slic` you want to take actions on that
-plugin using the following command:
+The `slic use` command offers two ways to select your target:
+
+#### Interactive Mode (No Arguments)
+
+When you run `slic use` without any arguments, it opens an interactive Terminal User Interface (TUI) that lets you browse and select from available targets:
 
 ```bash
-slic use the-events-calendar
+slic use
 ```
 
-> For more information on this command, run `slic help use`.
+This launches an interactive menu with these features:
+- **Browse targets**: Navigate through all available plugins/themes with arrow keys (↑↓)
+- **Fuzzy search**: Type to filter targets instantly (case-insensitive substring matching)
+- **Current target indicator**: See which target is currently active (marked with ✓)
+- **Scroll indicators**: Visual cues when there are more items above/below the visible window
+- **Keyboard controls**:
+  - `↑↓` Arrow keys to navigate
+  - Type to filter/search
+  - `Enter` to select
+  - `ESC` or `Ctrl+C` to cancel
+- **Cross-platform**: Works on Windows, macOS, and Linux
+
+The interactive mode is especially helpful when:
+- You're not sure of the exact target name
+- You want to see all available options at once
+- You need to quickly switch between targets
 
 ![slic use](docs/images/slic-use.gif)
 
+#### Direct Mode (With Target Name)
+
+If you already know which target you want, you can specify it directly:
+
+```bash
+slic use the-events-calendar
+```
+
+This immediately switches to the specified target without showing the interactive menu.
+
+> For more information on this command, run `slic help use`.
+
 ### Initialize your project
 
 With your desired plugin containing directory set, you will need to initialize plugins so that they are prepped and ready

changelog.md

@@ -8,10 +8,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 - Breaking Change - The `slic here` command will now create a new stack for the current path instead of changing the context of the previously only stack to the path.
-- Breaking Change - The `XDK` configuration variable (`slic` by default) is now used as **root** for each stack IDE key. An `XDK` of `slic` will create stack IDE keys like `slic_<stack_hash>` and not just `slic` as it was before. 
+- Breaking Change - The `XDK` configuration variable (`slic` by default) is now used as **root** for each stack IDE key. An `XDK` of `slic` will create stack IDE keys like `slic_<stack_hash>` and not just `slic` as it was before.
 
 ### Added
 - Multi-path support with a 1:1 mapping between stacks and paths.
+- Interactive Terminal User Interface (TUI) for the `slic use` command. Running `slic use` without arguments now opens an interactive selection menu with fuzzy search and current selection indicator.
 - Git worktree multi-stack support for concurrent development workflows
 - New `slic worktree` command with subcommands:
   - `slic worktree add <branch>` - Create a new git worktree with dedicated stack

slic.md

@@ -63,7 +63,18 @@ slic run wpunit
 ```
 
 Since the command might potentially run on any of the plugins maintained by the Products team, you'll need to tell the `slic` command what plugin you're currently working on with the `use` sub-command.
-You can change the plugin you want to run tests on by using the `slic use` command again at any moment. If you want, now to run Event Tickets tests, you could just use:
+
+### Interactive Target Selection
+
+The `slic use` command now provides an interactive Terminal User Interface (TUI) when called without arguments:
+
+```bash
+slic use
+```
+
+This opens an interactive menu that allows you to browse all available targets, see the current one, and select a new one.
+
+You can also directly specify a target to skip the interactive menu:
 
 ```bash
 slic use event-tickets

src/commands/use.php

@@ -10,10 +10,15 @@
 
 	USAGE:
 
-		<yellow>{$cli_name} {$subcommand} <target>[/<subdir>]</yellow>
+		<yellow>{$cli_name} {$subcommand} [<target>[/<subdir>]]</yellow>
+
+		When called without a target argument, displays an interactive selection menu.
 
 	EXAMPLES:
 
+	<light_cyan>{$cli_name} {$subcommand}</light_cyan>
+	Open interactive target selection menu.
+
 	<light_cyan>{$cli_name} {$subcommand} the-events-calendar</light_cyan>
 	Set the use target to the-events-calendar.
 
@@ -28,6 +33,38 @@
 $sub_args = args( [ 'target' ], $args( '...' ), 0 );
 $target   = $sub_args( 'target', false );
 
+// If no target provided, show TUI
+if ( $target === false ) {
+	// Get all valid targets
+	$valid_targets = get_valid_targets( true ); // true = return as array
+
+	if ( empty( $valid_targets ) ) {
+		echo colorize( "<red>No valid targets found. Run 'slic here' first.</red>\n" );
+		return 1;
+	}
+
+	// Get current target (don't require it - may not be set yet)
+	$current_target = null;
+	$using          = getenv( 'SLIC_CURRENT_PROJECT' );
+	$using_subdir   = getenv( 'SLIC_CURRENT_PROJECT_SUBDIR' );
+	if ( ! empty( $using ) ) {
+		$current_target = $using . ( $using_subdir ? '/' . $using_subdir : '' );
+	}
+
+	// Show TUI
+	require_once __DIR__ . '/../tui.php';
+	$target = tui_select(
+		$valid_targets,
+		$current_target,
+		'Select target (type to filter, ↑↓ to navigate, Enter to select, ESC to cancel):'
+	);
+
+	// If user cancelled, exit gracefully
+	if ( $target === null ) {
+		return 0;
+	}
+}
+
 // Determine which stack to use
 $stack_id = slic_current_stack_or_fail( "Cannot switch target without an active stack." );