What does stack mean?
An application stack is the combination of everything needed to run the app: runtime, dependencies, database, environment configuration, reverse proxy or web server, process management, SSL, and deployment routine.
What can the agent do?
- Check the operating system, runtime, and available tools.
- Install required dependencies after approval.
- Create or configure a database and migrations.
- Set up a web server or reverse proxy.
- Configure a process manager, container, or service.
- Build the app, start it, and test that it responds.
- Create a simple runbook for future deployments.
Safe order of work
- Inspect the server and project requirements without changing anything.
- Create a plan: dependencies, database, web server, environment variables, and verification.
- Get approval before installation, database changes, firewall changes, and production deployment.
- Install and configure one piece at a time.
- Build and start the application.
- Verify the live URL, service status, and any health checks.
- Document commands, locations, and the future deployment routine without storing secrets.
Good prompt
"Set up this app on a new VPS. Start by inspecting the environment and writing a plan before installing anything. Do not print secrets. Ask for approval before database creation, firewall changes, or production deployment. When the app runs, verify the live URL and write a short runbook."
Important: the agent can do a lot of technical work, but the customer should still control access, domain, DNS, backups, security, and production approval.
More stack setup prompts
- "Inspect the server and tell me which runtime, database, and webserver components are already installed."
- "Install dependencies only after showing me the exact plan and asking for approval."
- "Configure the database and run migrations, but create a backup or rollback plan first."
- "Set up the reverse proxy and TLS for this domain, then verify the public URL."
- "Create a runbook with start, stop, deploy, backup, and health-check commands."
What should be documented afterward?
- How the app is started, stopped, and deployed.
- Which services are running.
- How database migrations and backups work.
- How to verify that the app is healthy.
- Which steps require manual approval.