configure-ecc

You can set up ECC skills by running an interactive installer that prompts you to select user-level or project-level environments, validates target paths, and deploys the chosen configuration across your repositories.

User-level ECC installation applies skills and rules globally across your development environment, while project-level installation tailors the configuration and references specifically to the target repository structure you are working in.

Yes, you can optimize ECC skills to match your repository structure by selecting the optional optimization path during the interactive setup, which tailors installed files and references to your specific project layout.

Yes, you need access to the ECC root directory and target environment paths before configuring rules, as the installer requires these to clone repositories, validate references, and verify cross-dependencies during deployment.

Path validation fails during ECC rule installation when the target environment paths are inaccessible or incorrectly specified, preventing the installer from verifying reference integrity and deploying skills to the selected directories.