Power Setup Invoker

Bootstrap complete development and deployment environments with a single command invocation.

When to Use This Command

Run this command when you need to:

• Initialize a new project with CI/CD pipelines, linting, testing, and deployment configuration
• Set up a development environment with all required tooling, services, and dependencies
• Onboard a new team member by configuring their local environment to match team standards

Consider alternatives when:

• You only need to install a single tool or dependency, not a full environment setup
• The project already has a working setup and you need to modify specific configurations

Quick Start

Configuration

Copy
name: power-setup-invoker
type: command
category: deployment

Example Invocation

Copy
claude command:run power-setup-invoker --stack fullstack --framework nextjs

Example Output

Project Setup: fullstack (Next.js)

Environment Detection:
  OS: macOS 14.2 (arm64)
  Node: v20.11.0
  Package Manager: pnpm 8.15.1

Setup Progress:
  [+] Project structure created (src/, tests/, docs/)
  [+] Dependencies installed (142 packages)
  [+] TypeScript configured (tsconfig.json)
  [+] ESLint + Prettier configured
  [+] Jest testing framework initialized
  [+] Git hooks installed (husky + lint-staged)
  [+] CI/CD pipeline created (.github/workflows/ci.yml)
  [+] Docker development environment configured
  [+] Environment template created (.env.example)
  [+] VS Code workspace settings generated

Setup complete. Run `pnpm dev` to start development server.

Core Concepts

Environment Setup Overview

Aspect	Details
Runtime Detection	Identifies OS, architecture, and installed toolchain versions
Dependency Management	Installs packages, configures lock files, sets up workspaces
Code Quality	ESLint, Prettier, TypeScript strict mode, and editor config
Git Workflow	Husky hooks, lint-staged, commit message validation
CI/CD Pipeline	GitHub Actions or GitLab CI with test, lint, and deploy stages

Setup Orchestration Workflow

  Invoke Setup
       |
       v
  +-----------------+
  | Detect Platform |---> OS, arch, toolchain
  +-----------------+
       |
       v
  +-----------------+
  | Install Runtime |---> Node, Python, Go, etc.
  +-----------------+
       |
       v
  +-----------------+
  | Scaffold Project|---> Directories, configs, templates
  +-----------------+
       |
       v
  +-----------------+
  | Quality Tooling |---> Linter, formatter, type checker
  +-----------------+
       |
       v
  +-----------------+
  | CI/CD + Hooks   |---> Pipelines, git hooks, pre-commit
  +-----------------+
       |
       v
  +-----------------+
  | Validate Setup  |---> Run build + test to confirm
  +-----------------+

Configuration

Parameter	Type	Default	Description
stack	string	frontend	Project type: frontend, backend, fullstack, api, library
framework	string	auto-detect	Framework to scaffold: nextjs, express, fastapi, django
package_manager	string	auto-detect	Package manager: npm, pnpm, yarn, pip, cargo
ci_provider	string	github	CI/CD provider: github, gitlab, bitbucket, circleci
docker	boolean	true	Include Docker development environment configuration

Best Practices

1. Detect Before Installing - Always check what is already installed on the system before attempting installation. Overwriting existing configurations or downgrading tools causes frustration and breaks working setups.

2. Use Environment Templates - Generate .env.example files with all required variables and sensible defaults. Never generate .env files with real credentials; let developers fill in their own secrets.

3. Validate the Setup at the End - Run a build and test cycle as the final step to confirm everything works. A setup that reports success but produces build errors on first use destroys trust in the tool.

4. Make Setup Idempotent - Running the setup command twice should not break anything. Check for existing files and configurations before overwriting, and skip steps that are already complete.

5. Document What Was Created - Print a summary of all files generated, tools installed, and next steps. Developers need to understand what the setup did so they can maintain and customize it.

Common Issues

1. Permission Denied During Installation - Global package installations require elevated permissions on some systems. Use local installations (npx, project-local bins) instead of global installs to avoid sudo requirements.

2. Version Conflicts With Existing Tools - The setup installs a Node version that conflicts with the developer's nvm configuration. Respect existing version managers and generate .nvmrc or .tool-versions files instead of overriding system installations.

3. CI Pipeline Fails on First Run - The generated workflow references secrets or environment variables that have not been configured in the CI provider. Include a checklist of required repository secrets in the setup summary.