deployment

Configure production deployment targets and run/build commands for web apps, APIs, bots, and static frontends.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill deployment-naopensedoit2-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor/tree/main/.local/skills/deployment
Command: npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill deployment-naopensedoit2-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of configuring how a project should run in production and ensuring it is properly prepared for publishing so it becomes live and accessible.

Core Features & Use Cases

  • Deployment configuration: Sets production deployment target and defines run/build/public directory inputs to match the project type.
  • Target selection guidance: Helps choose between autoscale, vm, scheduled, and static hosting based on runtime needs and statefulness.
  • Publish readiness workflow: Encourages validating that the app works before triggering the actual publish action.

Quick Start

Configure deployment for your web app by choosing an autoscale target and then suggest publishing after you confirm the app builds and runs successfully.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I configure production deployment settings for a web app?

Production deployment settings are configured by selecting an autoscale target and defining run commands to match the project type. This ensures the web app runs correctly once published and is accessible live.

What is the best way to choose between autoscale, vm, and static hosting for my project?

Choosing between autoscale, vm, scheduled, and static hosting depends on runtime needs and statefulness. Static hosting requires a build plus publicDir, while autoscale, vm, and scheduled targets require specific run commands for stateful workloads.

Can I deploy background jobs and cron-like tasks to an autoscale target?

Background jobs and cron-like tasks are deployed to a scheduled target rather than autoscale. The deployment configuration aligns run commands with the selected target to ensure these tasks execute correctly in production.

Do I need a build command and publicDir for static frontend deployment?

Static frontend deployment requires a build command and publicDir configuration. This ensures the project is properly prepared for publishing by aligning the hosting configuration with the static target.

Why does my app need to build and run successfully before triggering a publish action?

Your app needs to build and run successfully before publishing to ensure publish readiness. The workflow encourages validating app functionality so it runs correctly once the production deployment configuration is live.