vercel-multi-env-setup
Configure Vercel across development, staging, and production environments.Use when setting up multi-environment deployments, configuring per-environment secrets,or implementing environment-specific Vercel configurations.Trigger with phrases like "vercel environments", "vercel staging","vercel dev prod", "vercel environment setup", "vercel config by env".
When & Why to Use This Skill
This Claude skill automates the complex process of configuring Vercel across multiple deployment stages, including development, staging, and production. It streamlines environment-specific setups, manages secure secrets through external providers like Vault or AWS, and implements critical safeguards to ensure robust and consistent CI/CD workflows for modern web applications.
Use Cases
- Multi-Stage Deployment Setup: Quickly establish and synchronize separate Vercel environments for development, staging, and production to maintain a clean release pipeline.
- Secure Secrets Integration: Automate the mapping of sensitive API keys and credentials from secret management solutions (Vault, AWS Secrets Manager) to specific Vercel environment variables.
- Environment-Specific Configuration: Generate and manage tailored configuration files and detection logic to ensure applications behave correctly across different infrastructure contexts.
- Production Guardrail Implementation: Deploy automated safeguards and environment detection to prevent risky development operations from affecting production environments.
| name | vercel-multi-env-setup |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Vercel Multi Env Setup
Prerequisites
- Separate Vercel accounts or API keys per environment
- Secret management solution (Vault, AWS Secrets Manager, etc.)
- CI/CD pipeline with environment variables
- Environment detection in application
Instructions
Step 1: Create Config Structure
Set up the base and per-environment configuration files.
Step 2: Implement Environment Detection
Add logic to detect and load environment-specific config.
Step 3: Configure Secrets
Store API keys securely using your secret management solution.
Step 4: Add Environment Guards
Implement safeguards for production-only operations.
Output
- Multi-environment config structure
- Environment detection logic
- Secure secret management
- Production safeguards enabled
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.