From cc-configs
Install levx's Claude Code config files to `~/.claude` interactively.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cc-configs:installThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Install levx's Claude Code config files to `~/.claude` interactively.
Install levx's Claude Code config files to ~/.claude interactively.
When invoked, execute the steps below immediately. Do not summarize.
The plugin root is available as ${CLAUDE_PLUGIN_ROOT}. Verify the install script exists:
ls "${CLAUDE_PLUGIN_ROOT}/scripts/install.sh"
If missing, tell the user:
scripts/install.sh not found in plugin root.
Please reinstall the plugin: claude plugin install cc-configs@levx
And stop.
Use AskUserQuestion (multiSelect: true):
Question: "어떤 컴포넌트를 설치할까요?"
Options:
claude) — default selectedrules) — default selectedhooks) — default selectedsettings) — default selectedStore selected values as COMPONENTS (comma-joined, e.g. claude,rules).
If no components selected, tell user "Nothing selected. Exiting." and stop.
If hooks is in COMPONENTS, use AskUserQuestion (multiSelect: true):
Question: "어떤 훅을 설치할까요?"
Options:
auto-allow) — default selectedgit-guard) — default selectedrtk-rewrite)Store selected values as HOOKS (comma-joined). If none selected, remove hooks from COMPONENTS.
Construct the command from user selections and run it:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/install.sh" \
--components=<COMPONENTS> \
--hooks=<HOOKS>
Example (CLAUDE.md + rules + hooks with auto-allow and git-guard):
bash "${CLAUDE_PLUGIN_ROOT}/scripts/install.sh" \
--components=claude,rules,hooks \
--hooks=auto-allow,git-guard
If hooks is not in COMPONENTS, omit the --hooks flag entirely.
Display the install script output to the user.
If rtk-rewrite was selected and rtk is not in PATH, remind:
RTK 미설치: cargo install rtk 로 설치하세요.
https://github.com/rtk-ai/rtk
Tell user to restart Claude Code for CLAUDE.md and hooks changes to take effect.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
npx claudepluginhub levx-me/cc-configs --plugin cc-configs