deploy
Set up deployment infrastructure for the project following aishift patterns
When & Why to Use This Skill
This Claude skill automates the end-to-end setup of deployment infrastructure using standardized patterns. It intelligently detects project types—including Python, Golang, and React—to generate production-ready configurations, systemd services, and Caddy reverse proxy settings, significantly reducing the time and complexity of moving code from development to a live environment.
Use Cases
- Automated VPS Provisioning: Quickly set up a new virtual private server with all necessary systemd services, sudoers configurations, and Makefile targets for a fresh project.
- Multi-Environment Deployment: Seamlessly configure and manage separate staging and production environments with environment-specific parameters and infrastructure.
- Reverse Proxy Integration: Automatically generate Caddy configurations to handle SSL termination and traffic routing for web applications.
- Infrastructure Standardization: Enforce consistent deployment patterns across multiple team projects to ensure maintainability and reduce 'it works on my machine' issues.
- Legacy Project Upgrading: Update existing project deployment scripts and infrastructure to the latest versioned templates and security best practices.
| name | deploy |
|---|---|
| description | Set up deployment infrastructure for the project following aishift patterns |
Analyze the current project and set up comprehensive deployment infrastructure following aishift patterns.
Use the Task tool with subagent_type="deploy" to launch the specialized deployment agent.
Your task:
- Detect the project type (Python, Golang, React, or combination)
- Fetch deployment templates from vps-setup repository (versioned)
- Ask necessary configuration questions (target server, environments, etc.)
- Generate deploy/ directory with all required files
- Create systemd services, sudoers configs, and Makefile targets
- Add Caddy configuration if reverse proxy is needed
- Update project documentation with deployment instructions
If arguments are provided, use them as answers to configuration questions or as additional context.
Examples:
/deploy- Interactive setup with questions/deploy production vps.example.com- Set up for production environment on specified server/deploy staging production- Set up both staging and production environments/deploy upgrade- Upgrade existing deployment to newer vps-setup version
Always provide clear next steps after generating deployment files.