Configure Gamma across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Gamma configurations. Trigger with phrases like "gamma environments", "gamma staging", "gamma dev prod", "gamma environment setup", "gamma config by env".
From gamma-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin gamma-packThis skill is limited to using the following tools:
references/implementation.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Configure Gamma across development, staging, and production environments with proper isolation, secrets management, and environment guards.
Define per-environment settings (timeout, retries, debug mode) in a typed configuration object. Use NODE_ENV to select the active config.
Store separate API keys in .env.development, .env.staging, and .env.production files. Never commit keys to version control.
For production, use AWS Secrets Manager or Vault to fetch keys at runtime with caching (5-minute TTL recommended).
Create a singleton factory that returns environment-aware Gamma clients. Production clients should fetch keys from secret manager; dev/staging can use env vars.
Implement requireProduction() and blockProduction() guards to prevent destructive operations in the wrong environment.
Set up GitHub Actions (or equivalent) with separate deployment jobs per environment, each using environment-specific secrets.
See detailed implementation for advanced patterns.
| Issue | Cause | Solution |
|---|---|---|
| Wrong API key used | Env var mismatch | Verify NODE_ENV matches key prefix |
| Secret fetch fails | IAM permissions | Check secrets manager access policy |
| Production data in dev | No env guard | Add blockProduction() guards |
| Check | Dev | Staging | Prod |
|---|---|---|---|
| Separate API key | Yes | Yes | Yes |
| Debug logging | On | On | Off |
| Mock mode available | Yes | Yes | No |
| Secret manager | No | Yes | Yes |
| Rate limit tier | Low | Medium | High |