deploylisted

Multi-target deploy router for SkynetLabs with deploy gotchas baked in as hard rules. Detect the deploy target from the repo, route to the correct procedure, and BLOCK the wrong path before it ships. Targets in active use: - Vercel — React/Next sites (your-site-react, your-app) via `vercel` CLI / git push - Hostinger manual ZIP — example.com (Next.js standalone on Hostinger Node app). HARD RULE: deploys via manual ZIP archive upload, NOT GitHub auto-deploy, NOT Vercel. Warn + refuse if anyone routes it to GitHub push or Vercel. - WordPress theme/plugin — ZIP upload or Hostinger MCP deployWordpressTheme/Plugin - Static site — plain HTML/CSS via Hostinger MCP deployStaticWebsite Runs a pre-deploy gate (build passes, no exposed secrets, security review, git committed), executes the routed procedure, then verifies the URL is live and records the rollback path. Trigger when user says: "deploy", "ship to prod", "push live", "/deploy", "deploy my site", "deploy to vercel/hostinger", "upload the theme", "publish the
waseemnasir2k26/skynetlabs-all-claude-code · ★ 0 · Web & Frontend · score 68

Install: claude install-skill waseemnasir2k26/skynetlabs-all-claude-code

# deploy Route a repo to the RIGHT deploy target and enforce the gotcha so the wrong path never ships. This skill is opinionated on purpose — it's easy to lose time deploying a Hostinger Node app to the wrong target. The detection + hard rules below exist to stop that. ## When to use USE when the user wants to get a build live (any of: Vercel, Hostinger ZIP, WordPress theme/plugin, static site) and isn't sure of the procedure, OR when the target carries a gotcha (a Hostinger Node app like example.com). For the full versioned release flow (merge main → tests → VERSION bump → CHANGELOG → PR), run `/ship` FIRST, then `/deploy` the resulting build. `/deploy` is about the last mile (build → host), `/ship` is about the git release. ## Step 0 — Detect the target (run this first, always) ```bash cd <repo> # absolute repo path, e.g. ~/GITHUB/your-site-react git rev-parse --show-toplevel # confirm it's a repo git remote -v # capture origin (used for the Hostinger-app identity check) ls # top-level inventory ``` Detection order (FIRST match wins — the Hostinger-app override beats generic Vercel): | Signal (check in this order) | Target | | -------------------------------------------------------------------------------------------------------------------- | ----------------