deploy-production

Deploy server to Fly.io and client to Vercel in correct order.

19|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Bulugulu/motif-cli --skill deploy-production-bulugulu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-production
Source: https://github.com/Bulugulu/motif-cli/tree/main/examples/generated/skills/project/deploy-production
Command: npx skills add https://github.com/Bulugulu/motif-cli --skill deploy-production-bulugulu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes the deployment workflow for this project's infrastructure to prevent skipped steps and incorrect sequencing, reducing deployment failures and drift.

Core Features & Use Cases

  • Enforces a consistent, end-to-end deployment sequence for server (Fly.io) and client (Vercel) components.
  • Validates readiness and post-deploy results, surfacing errors for rapid triage after session wrapups or on demand.
  • Provides a repeatable workflow that teams can review, customize, and apply to similar projects.

Quick Start

Navigate to the project root and trigger the deployment workflow to deploy the server then the client in the correct order.

Frequently Asked Questions about deploy-production

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate production deployments to Fly.io and Vercel in the correct order?

Automating production deployments to Fly.io and Vercel requires enforcing a lock-step sequence that deploys the server first, then the client. This workflow standardizes the process to prevent skipped steps and incorrect sequencing during infrastructure updates.

What is the best way to prevent incorrect deployment sequencing for full-stack applications?

Preventing incorrect deployment sequencing involves applying a standardized, end-to-end workflow with guardrails. By enforcing a project-root execution context, the process runs server and client deployments in a controlled order, reducing failures and configuration drift.

Does this deployment workflow validate readiness and post-deploy results for Fly.io and Vercel?

Yes, validating deployment readiness and post-deploy results is a core function. The workflow surfaces errors for rapid triage after session wrapups or on-demand execution, ensuring both server and client components are verified after deployment.

How do I troubleshoot deployment errors when automating server and client releases?

Troubleshooting deployment errors is handled by built-in validation and error handling steps. After attempting server and client releases, the workflow validates deployment results and surfaces specific errors to enable rapid triage and resolution.

When do I need a lock-step deployment workflow for my project infrastructure?

A lock-step deployment workflow is needed when standardizing infrastructure updates to prevent skipped steps and reduce drift. It is applicable for projects requiring server deployment to Fly.io and client deployment to Vercel after session reviews.