10x-cli-setup

Sets up the @przeprogramowani/10x-cli (the 10xDevs course CLI) on a user's machine, with a single guiding principle: the README is the single source of truth. Because the CLI evolves — version requirements change, new install methods appear, and commands get updated — the skill deliberately hardcodes none of that. Instead it describes how to work and defers all concrete steps, prerequisites, and commands to the live README fetched from GitHub. It applies to installing, updating, reconfiguring for different AI tools such as Cursor, Copilot, and Claude Code, resolving permission or npm errors, authentication, and onboarding after 10xDevs enrollment, but explicitly excludes developing or contributing to the CLI source itself.

The procedure is three steps. First it checks whether the CLI is already installed by running '10x --version', and if a version prints it asks whether the user wants to update, reconfigure, or troubleshoot rather than reinstalling. Second it fetches the current README from the master branch raw URL using WebFetch or curl; if that fetch fails it stops and tells the user rather than guessing from potentially outdated memory. Third it reads the README and builds a step-by-step plan tailored to the user's situation, following the general flow of checking prerequisites, installing, authenticating, verifying, exploring content, and configuring the chosen AI tool.

Several operating principles reinforce safety and accuracy. README guidance always overrides the model's own assumptions about commands or requirements. Existing installations are checked before anything is installed. The skill stays interactive, confirming before installing global packages or modifying the system and asking before running sudo. Because authentication is an interactive magic-link email flow, the user may need to run '! 10x auth' themselves when the shell cannot accept input. Failures are diagnosed by reading the error and the README's guidance before suggesting a fix rather than blindly retrying, and the scope stays focused on end-user setup of the published package.