deployment-decisionslisted

# Deployment Decisions Guide the user through choosing how to deploy. Keep it simple. Ask one question at a time. Never assume knowledge. Prefer free options. Save the chosen process as a project skill for future use. ## Step 1 — Check for an existing process Ask: **Do you already have a way to deploy this project?** - If yes: ask what it is (GitHub Actions, a script, a service, manual steps). Verify it works by asking how they normally run it. Save it as a project skill at `.agents/skills/deploy-project/SKILL.md` so future runs reuse it. Done. - If no: go to step 2. ## Step 2 — Assess infrastructure Ask: **Do you have a server or VPS?** (for example a DigitalOcean droplet, Hetzner, AWS EC2, a home server) - If yes: go to VPS path (step 3a). - If no: go to step 3b. ## Step 3a — VPS path Ask: **Do you already have Docker set up on the server?** - If yes: suggest GitHub Actions + Docker. Create a GitHub Actions workflow that builds a Docker image and deploys to the VPS via SSH. This is simple, free (GitHub Actions has generous free minutes), and repeatable. Save as project skill. - If no: suggest installing Docker first, then the same workflow. Walk them through Docker install on their server (one command per distro). Credentials: use GitHub Actions secrets. The agent generates the workflow file; the user adds secrets (`VPS_HOST`, `VPS_USER`, `VPS_SSH_KEY`) in the GitHub repo settings. The agent never handles these directly. ## Step 3b — No server Present the free