deploy-production
Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. [GENERATED BY MOTIF — review and customize]
Best use case
deploy-production is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. [GENERATED BY MOTIF — review and customize]
Teams using deploy-production should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deploy-production/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deploy-production Compares
| Feature / Agent | deploy-production | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. [GENERATED BY MOTIF — review and customize]
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deploy Production Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. ## When to Use - User says 'deploy', 'push to production', or 'ship it' - After a session-wrapup when deployment is requested - Don't skip when: even if 'nothing changed' -- verify deployment state ## Instructions 1. cd to project root directory 2. Ensure all changes are committed and pushed to remote 3. Deploy server to Fly.io: `fly deploy --local-only` 4. Deploy client from client/ subdirectory to Vercel: `cd client && vercel --prod` 5. Verify both deployments succeeded by checking output 6. If either deployment fails, read error output and troubleshoot before retrying ## Best Practices - Always commit and push before deploying - Deploy server before client to avoid version mismatches - Check deployment logs for warnings even if deploy 'succeeds' ## Common Pitfalls | Problem | Solution | |---|---| | Deploying from wrong directory | Always cd to project root first | | Forgetting the --local-only flag for Fly.io | Always use --local-only to avoid remote builder issues | ## Key Constraints - Always deploy from project root - Use --local-only flag for Fly.io deployments - Deploy server before client