setup-deploy

Detect hosting platforms and write deployment blueprints to CLAUDE.md.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/256javy/safia --skill setup-deploy-256javy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/256javy/safia/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/256javy/safia --skill setup-deploy-256javy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure deployment settings for projects by automatically detecting hosting platforms and writing a deployment blueprint to CLAUDE.md so future deploys are automatic.

Core Features & Use Cases

  • Platform detection across Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom environments.
  • Auto-generation of a deployment blueprint including production URL, health check endpoints, and required deploy commands, persisted to CLAUDE.md for repeatable deployments.
  • Use case: standardize multi-environment deployments so a single change applies across all environments.

Quick Start

Run the setup-deploy workflow to detect your platform and generate a persistent CLAUDE.md deployment blueprint.

Frequently Asked Questions about setup-deploy

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

FAQPage Schema
How do I automate deployment setup across multiple hosting platforms?

Automate deployment setup by automatically detecting hosting platforms like Fly.io, Render, Vercel, Netlify, Heroku, or GitHub Actions, then generating a deployment blueprint with production URLs, health check endpoints, and deploy commands.

How do I persist deployment configurations so future deploys are automatic?

Persist deployment configurations by writing the generated deployment blueprint directly into CLAUDE.md, which stores production URLs, health check endpoints, and required deploy commands for consistent, repeatable future deployments.

Does the deployment blueprint support custom hosting environments or only standard platforms?

The deployment blueprint supports both standard hosting platforms like Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom environments, detecting the platform automatically to configure appropriate deploy commands and health check endpoints.

How do I standardize multi-environment deployments so a single change applies everywhere?

Standardize multi-environment deployments by generating a persistent CLAUDE.md deployment blueprint that captures production URLs, health check endpoints, and deploy commands, ensuring configuration changes apply consistently across all environments.

Can I update deployment settings automatically when hosting configurations change?

Deployment settings update automatically when changes occur by detecting the hosting platform and rewriting the CLAUDE.md deployment blueprint, keeping production URLs, health check endpoints, and deploy commands current for automated future deploys.

What's the best way to configure health check endpoints and production URLs for automated deploys?

Configure health check endpoints and production URLs by running a platform detection workflow that identifies your hosting environment and writes a complete deployment blueprint to CLAUDE.md, enabling consistent, automated future deploys.