Help us improve
Share bugs, ideas, or general feedback.
From claude-initializer
Orchestrate full project setup by running init, knowledge sync, permissions, and guardrails
npx claudepluginhub qazuor/claude-code-plugins --plugin claude-initializerHow this command is triggered — by the user, by Claude, or both
Slash command
/claude-initializer:setup-projectThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /setup-project ## Purpose One-command project setup that orchestrates all initialization steps in the correct order. Runs init-project, knowledge-sync, permission-sync, and guardrails initialization so a project is fully configured in a single pass. ## Process You are the setup orchestrator for the claude-initializer plugin. Your job is to run all setup steps in sequence, skipping steps that are already done, and presenting a final summary. ## Step 1: Check Prerequisites Check if `.claude/` directory already exists: - If `.claude/` exists AND `.claude/CLAUDE.md` exists: project is ...
/setupRuns interactive setup wizard: installs plugin files from GitHub, creates .env config, analyzes tech stack, generates PROJECT.md, configures hooks.
/setupInitializes Claude Code projects in Plugin or Clone mode, configures hooks globally or per-project, creates settings files/directories and cleans old configs. Supports --hooks, --global, --project, --verify flags.
/setupChecks Claude Code setup status with bash script, installs missing required plugins (dogma, gsd) via user confirmation, and guides project files/directories setup.
/dev-setupInitializes Claude Code infrastructure in a project directory, creating AI skills, hooks, settings, MASTER_PLAN.md template, and CLAUDE.md guidance. Supports path and --minimal flag.
/setup-projectScaffolds a new open-source project with community health files (README, CONTRIBUTING, LICENSE, CODE_OF_CONDUCT, SECURITY, CITATION.cff), GitHub issue/PR templates, and language-specific .gitignore. Prompts for project details like name, description, license, and primary language.
Share bugs, ideas, or general feedback.
One-command project setup that orchestrates all initialization steps in the correct order. Runs init-project, knowledge-sync, permission-sync, and guardrails initialization so a project is fully configured in a single pass.
You are the setup orchestrator for the claude-initializer plugin. Your job is to run all setup steps in sequence, skipping steps that are already done, and presenting a final summary.
Check if .claude/ directory already exists:
.claude/ exists AND .claude/CLAUDE.md exists: project is already initialized.claude/ does not exist: project needs initializationPROJECT SETUP
=============
Project: <directory name>
Location: <project root>
Checking prerequisites...
.claude/ directory: [exists/missing]
CLAUDE.md: [exists/missing]
tasks/index.json: [exists/missing]
guardrails.md: [exists/missing]
settings.local.json: [exists/missing]
If .claude/ does not exist or CLAUDE.md is missing:
Step 1/5: Initializing project...
Execute /init-project to create the base configuration.
If already initialized:
Step 1/5: Project already initialized. Skipping.
Step 2/5: Syncing knowledge components...
Execute /knowledge-sync install --detect to analyze the project and install relevant components.
If knowledge-sync is not available (plugin not installed):
Step 2/5: knowledge-sync plugin not available. Skipping.
Install the knowledge-sync plugin for automatic component detection.
Step 3/5: Syncing permissions...
Execute /sync-permissions to apply base permissions to the project.
If permission-sync is not available:
Step 3/5: permission-sync plugin not available. Skipping.
Install the permission-sync plugin for automatic permission management.
Step 4/5: Initializing guardrails...
Check if .claude/guardrails.md already exists:
The guardrails template is located at the task-master plugin's templates directory. Read the template from guardrails-template.md in the task-master plugin and write it to .claude/guardrails.md in the project.
Guardrails initialized with 4 seed signs.
Review and customize at .claude/guardrails.md
If guardrails already exist:
Step 4/5: Guardrails already configured (N signs). Skipping.
If task-master plugin is not available:
Step 4/5: task-master plugin not available. Skipping guardrails.
Install the task-master plugin for guardrails and task management.
SETUP COMPLETE
==============
[x] Project initialized (.claude/ directory, CLAUDE.md)
[x] Knowledge components installed (N components)
[x] Permissions synced (N rules)
[x] Guardrails initialized (4 signs)
[ ] Tasks - no specs yet
Next steps:
1. Review .claude/CLAUDE.md and customize for your project
2. Review .claude/guardrails.md and add project-specific constraints
3. Use /spec to create your first specification
4. Use /auto-loop to start autonomous task processing
Show which steps were executed vs skipped:
Steps executed: 3/5
Steps skipped: 2/5 (already configured)
jq for JSON processing. NEVER use Python or Node.js.[ -f "$FILE" ] && jq '.' "$FILE"mkdir -p and check existence with [ -d "$DIR" ]2>/dev/null or || true when files/dirs might not exist.