Stats
Actions
Tags
From cc-setup
Deploy cc-setup configuration to this machine — rules, hooks, CLAUDE.md, settings, MCP configs, and register plugin
How this command is triggered — by the user, by Claude, or both
Slash command
/cc-setup:cc-installThe summary Claude sees in its command listing — used to decide when to auto-load this command
# CC Install Full deploy of cc-setup to this machine. ## Usage Run the install script: Then register the plugin marketplace in Claude Code: ## What install.sh Deploys - `~/.claude/rules/` — rule files (always-loaded context) - `~/.claude/hooks/` — hook scripts (event handlers) - `~/.claude/CLAUDE.md` — global instructions (merged with OMC block) - `~/.claude/settings.json` — settings with hook registrations and secret injection - `~/.claude/output-styles/` — output style presets - MCP configs with API key injection from .env ## What the Plugin Delivers (auto-discovered) - `agents/` ...
Full deploy of cc-setup to this machine.
Run the install script:
cd ~/cc-setup && ./install.sh
Then register the plugin marketplace in Claude Code:
/plugin marketplace add ~/cc-setup
/plugin install cc-setup@cc-setup-marketplace
~/.claude/rules/ — rule files (always-loaded context)~/.claude/hooks/ — hook scripts (event handlers)~/.claude/CLAUDE.md — global instructions (merged with OMC block)~/.claude/settings.json — settings with hook registrations and secret injection~/.claude/output-styles/ — output style presetsagents/ — unique agent definitionsskills/ — cc-health, cc-sync, cc-indexcommands/ — /cc-health, /cc-sync, /cc-install.env.template to .env and fill in API keys./install.sh before registering the pluginnpx claudepluginhub krzemienski/cc-setup --plugin cc-setup