Deployment Configuration
Separates deployment concerns from app logic with a clear scope boundary. The numbered checklist ensures Bolt covers every deployment requirement methodically.
Prepare this project for production deployment:\n\n1. Environment variables:\n - Create a .env.example file listing all required env vars with placeholder values\n - Replace any hardcoded secrets, API URLs, or credentials with process.env references\n\n2. Build optimization:\n - Add production build script to package.json\n - Configure {{bundler}} for tree-shaking and code splitting\n - Set up static asset caching headers\n\n3. Docker (if applicable):\n - Create a multi-stage Dockerfile (build stage + production stage)\n - Add .dockerignore for node_modules, .env, and build artifacts\n\n4. Health check:\n - Add GET /api/health endpoint that returns { status: "ok", timestamp: Date.now() }\n\nDo not change any application logic or UI. Only add deployment infrastructure.Variables to customize
Why this prompt works
Separates deployment concerns from app logic with a clear scope boundary. The numbered checklist ensures Bolt covers every deployment requirement methodically.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Forcing the agent to plan before acting prevents premature execution and wasted steps. Explicit dependency mapping enables parallel execution and catches logical gaps early.
Tool Selection AgentThe ReAct pattern (Reason + Act) creates an explicit reasoning trace that improves tool selection accuracy. The error-handling rule prevents infinite retry loops.
Prompt CompressorExplicitly requiring all functional requirements to be preserved prevents the model from over-compressing and losing critical instructions.
Memory Management AgentExplicit memory read/write instructions create agents that improve over time. Categorization keeps memories organized, and the deduplication rule prevents context bloat.