Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/upcloud:setupThe summary Claude sees in its command listing — used to decide when to auto-load this command
# UpCloud Setup Provision infrastructure for project `$ARGUMENTS`. ## Steps 1. Read the `/upcloud:setup` skill at `.claude/skills/upcloud-setup/SKILL.md` 2. Follow the skill's workflow to provision: - Cloud Server (Docker + Caddy + Infisical) - Managed PostgreSQL (with extensions) - Object Storage (if needed) - Infisical secrets management 3. Generate `.deploy.json` config ## Example
Provision infrastructure for project $ARGUMENTS.
/upcloud:setup skill at .claude/skills/upcloud-setup/SKILL.md.deploy.json config/setup workbench
npx claudepluginhub emerging-tech-visma/et-upcloud/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.