configure-ecc

原文涵盖的主题

• Configure ECC
• Route by the current harness
• Claude Code: run the full conversational wizard
• 1. Inventory without changing anything
• 2. Collect exactly two choices
• 3. Preview and confirm once
• 4. Apply the explicit choices
• 5. Verify, then render the welcome

Run a conversational wizard inside the current harness. Inventory first, collect only supported choices, preview, confirm once, apply non-interactively, verify, and show the welcome only after success. Never clone ECC into a temporary directory or copy plugin components by hand. For a human-operated terminal, the canonical entry points are ecc setup and npx ecc-universal setup. Inside a harness, use the explicit non-interactive commands below instead. In Claude Code, use the full scope-and-hook wizard below. In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or map ECC's four Claude hook profiles onto Codex. In Kimi, install the project surface under ./.kimi-code. Kimi does not provide ECC's Claude lifecycle-hook profiles. If the harness is uncertain, state the detected evidence and ask which harness to configure before running a mutating command. This skill is a post-install reconfiguration path. It cannot intercept or replace a provider's built-in first-install UI. Run both commands and summarize the installed ECC scope, enabled state, and marketplace source: Treat a single existing ecc@ecc installation as a reconfiguration. Do not interpret Claude's provid

这里只展示节选，请以完整原文和当前要求为准。