Deployment and hosting guidance

Skill wfprieto/wcbs-build-kit/skills/deployment-and-hosting-guidance

Use when choosing, auditing, changing, deploying, migrating, or troubleshooting hosting, deployment environments, cloud tiers, preview/staging/production setup, persistent versus ephemeral workloads, infrastructure cost, rollback, scaling, or runtime placement.From its SKILL.md

Install

npx -y skills add wfprieto/wcbs-build-kit --skill deployment-and-hosting-guidance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.9 KB, as published. Nobody here has run it

Deployment And Hosting Guidance

Use this skill to route deployment and hosting decisions through APIVR.

Required Inputs

APIVR tier and applicable Elite Build Goals.
Application type, runtime, data/storage needs, traffic expectations, and deployment target if known.
Current hosting provider, environment layout, build/deploy commands, and rollback path.
Cost sensitivity and reliability target.

Routing Workflow

Read 40_knowledge/DEPLOYMENT_AND_HOSTING_GUIDANCE.md.
Classify workload shape:
- static/edge;
- server-rendered web app;
- API/service;
- background worker;
- scheduled job;
- event-driven function;
- database/storage dependent app;
- always-on realtime process.
Decide whether the workload needs persistent compute, ephemeral execution, managed platform hosting, container hosting, or dedicated infrastructure.
Identify environment requirements: local, preview, staging, production, rollback, secrets, logs, monitoring, and domain/DNS.
If any deployed route is called by a provider, scheduler, webhook, OAuth/Auth redirect, or external machine caller, load skills/external-integration-launch-gate/SKILL.md and require a route contract before release.
Record deployment evidence in the evidence ledger and completion report.

Decision Graph

flowchart TD
  A["Workload needs hosting or runtime choice"] --> B{"Static or content-only?"}
  B -- "Yes" --> C["Static hosting or edge CDN"]
  B -- "No" --> D{"Needs long-running process, sockets, or durable memory?"}
  D -- "Yes" --> E["Persistent service or container"]
  D -- "No" --> F{"Triggered by schedule or event?"}
  F -- "Schedule" --> G["Scheduled job platform"]
  F -- "Event/Webhook" --> H["Event-driven function or queue"]
  F -- "Request/response" --> I["Managed app/API hosting"]
  E --> J["Define rollback, logs, scaling, cost"]
  G --> J
  H --> J
  I --> J
  C --> J
  J --> K["Verify deployed behavior before PASS"]

Guardrails

Do not deploy without rollback or restoration planning for Standard and above.
Do not choose always-on infrastructure for work that can safely be event-driven or scheduled.
Do not choose ephemeral/serverless hosting for workloads that require durable in-memory state, long-running sockets, or local filesystem persistence.
Do not claim deployment success until the deployed URL or service behavior is verified.
Do not put provider-facing routes behind human login, route-group auth, middleware redirects, or deployment protection unless the provider has a documented machine bypass.
Treat production deployment, DNS, database migration, payment/auth changes, and destructive infrastructure changes as Comprehensive or Forensic when consequences warrant.

Worked Example

Scenario: A reporting dashboard also needs a nightly refresh.

Hosting route: dashboard on managed web hosting; nightly refresh as scheduled job, not always-on compute.
APIVR tier: Standard unless private data, revenue reporting, or production migration raises it.
Connected skills: scheduling-and-automation-routing, data-output-and-reporting, and test-driven-development for code changes.
Evidence: preview URL verified, scheduled job dry-run verified, logs visible, rollback path documented.
APIVR verdict: PASS only after deployed dashboard and refresh behavior are Verified.

Scenario: A Stripe webhook fails on a preview deployment.

Hosting route: provider-facing route on deployed app URL.
Connected skill: external-integration-launch-gate.
Evidence required: provider dashboard delivery to the exact deployed URL, no /login redirect, no deployment-protection block, valid signature handling, database/user-visible proof, app log, and provider event ID.
APIVR verdict: Blocked until the provider-to-deployed-app path is verified.

Closeout

Report hosting decision, tradeoffs, cost risk, rollback method, verification performed, remaining risk, and APIVR verdict.

Workflow

Confirm the deployment target, protect secrets and rollback, deploy the smallest approved change, then verify the live result through its real boundary.