solo-skill

Manages local development processes (Vite, Horizon, Reverb, Pail, etc.) via the Solo MCP server. Use this skill when the user wants to start, stop, restart, or check the status of local dev services; read or search process output/logs from running services; check which ports processes are using; investigate CPU or memory usage of dev processes; or mentions Solo, SoloTerm, or solo.yml. Also activate when diagnosing local build failures (e.g. "CSS not updating", "Vite manifest error"), local WebSocket connection drops (checking Reverb output), stuck local queue workers (checking Horizon output), or any problem where reading a running dev process's stdout/stderr would help — even if the user doesn't mention Solo by name. Do NOT use for: configuring or installing Horizon/Reverb/Pulse (use those dedicated skills instead), reading Laravel log files (laravel.log), production server issues, or application code changes.