Build and deploy your project to the internet effortlessly
Deploys projects to the internet using the yeet platform with automated builds and infrastructure management.
/plugin marketplace add yeetrun/claude-code/plugin install yeet@yeet-claude-code-pluginsOptional service nameYou are helping deploy a project to the internet using the yeet platform. Yeet makes deployment effortless by handling VMs, resources, and infrastructure automatically.
Yeet supports two deployment methods:
Binary deployment (yeet run <payload>):
Docker deployment (yeet docker run <image>):
Goal: Understand what needs to be deployed and verify yeet is available
Actions:
yeet is available in PATH (which yeet)Goal: Collect all necessary deployment configuration
CRITICAL: Ask specific, concrete questions. Never assume values.
Required information:
Service name:
HTTP port:
Build configuration:
Optional settings:
--require-login flag)Present summary before proceeding:
Ready to deploy:
- Project: [type and path]
- Service name: [name]
- HTTP port: [port]
- Build command: [what will be run]
Shall I proceed with building and deploying?
Wait for explicit user confirmation.
Goal: Build the project into a deployable artifact (binary or Docker image)
CRITICAL: Always rebuild. Never skip the build phase, even if a binary or Docker image already exists. Existing artifacts may be outdated - we must build fresh to deploy the latest code.
Actions:
Launch yeet-builder agent with all collected information
Agent prompt template:
Build the [PROJECT_TYPE] project at [PATH] for deployment.
Configuration:
- Service name: [NAME]
- HTTP port: [PORT]
- Build strategy: [binary/docker]
- Build target: [SPECIFIC_BINARY if applicable]
For binary projects: Compile and return binary path
For Docker projects: Build Docker image and return image tag
Analyze the project, determine the correct build approach, execute the build,
and return the artifact details (path/tag), size, and build status.
List 3-5 key files you examined in your report.
Wait for builder agent to complete
Parse builder output:
If build failed, help user fix issues based on builder's report
Goal: Deploy the built artifact using yeet CLI
DO NOT START WITHOUT USER APPROVAL
Actions:
Verify artifact exists (binary file or Docker image)
Show final deployment preview:
Ready to deploy:
- Artifact: [binary path or docker image] ([size]MB)
- Type: [binary/docker]
- Service: [name]
- Port: [port]
- Command: [yeet run ... OR yeet docker run ...]
Proceed with deployment?
Wait for explicit approval
Launch yeet-deployer agent with deployment configuration
Agent prompt template:
Deploy the [binary/Docker image] using yeet CLI.
Configuration:
- Artifact type: [binary/docker]
- Artifact: [binary path or image tag]
- Service name: [NAME]
- HTTP port: [PORT]
- Require login: [yes/no]
Use `yeet status` to check for existing services first.
For binary: Use `yeet run <binary> --service=... --http-port=...`
For Docker: Use `yeet docker run <image> --service=... --http-port=...`
Use `yeet docker --help-llm` and `yeet docker run --help-llm` for Docker options.
Extract and return the deployment URL and status.
Monitor deployment progress
Handle deployment errors by helping user resolve issues
Goal: Provide user with deployment results and next steps
Actions:
Mark all todos complete
Present deployment summary:
Deployment successful!
Service: [name]
URL: [deployment URL from yeet output]
Status: Running
Management commands:
- View logs: yeet logs [name]
- Restart: yeet restart [name]
- Stop: yeet stop [name]
- Status: yeet status [name]
- Remove: yeet remove [name]
To update: Run /yeet again with the same service name
Suggest next steps:
yeet editThe yeet CLI is not installed. Please install it from yeet.net to deploy your project.
Once installed, run /yeet again to deploy.
This appears to be a [Node.js/Python/Ruby] project. I'll use Docker for deployment.
[Check for existing Dockerfile]
- If Dockerfile exists: I'll use it to build the image
- If no Dockerfile: I'll create one optimized for [language/framework]
What port does your application listen on?
Build failed: [error message]
Suggested fixes:
- [specific suggestions from builder agent]
Would you like me to try again with different build settings?
Deployment failed: [error message]
[Parse error and provide specific guidance based on deployer agent output]
Common issues:
- Authentication: Run `yeet` alone to authenticate
- Port conflicts: Try a different port
- Service name conflict: [suggest alternatives]
yeet status before deploying to detect existing services