Skill
Community

gamma-multi-env-setup

Install
1
Install the plugin
$
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin gamma-pack

Want just this skill?

Then install: npx claudepluginhub u/[userId]/[slug]

Description

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".

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBash(aws:*)Bash(gcloud:*)Bash(vault:*)
Supporting Assets
View in Repository
references/implementation.md
Skill Content

Gamma Multi-Environment Setup

Contents

Overview

Configure Gamma across development, staging, and production environments with proper isolation, secrets management, and environment guards.

Prerequisites

  • Separate Gamma 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 Environment Configuration

Define per-environment settings (timeout, retries, debug mode) in a typed configuration object. Use NODE_ENV to select the active config.

Step 2: Configure Per-Environment API Keys

Store separate API keys in .env.development, .env.staging, and .env.production files. Never commit keys to version control.

Step 3: Integrate Secret Management

For production, use AWS Secrets Manager or Vault to fetch keys at runtime with caching (5-minute TTL recommended).

Step 4: Build a Client Factory

Create a singleton factory that returns environment-aware Gamma clients. Production clients should fetch keys from secret manager; dev/staging can use env vars.

Step 5: Add Environment Guards

Implement requireProduction() and blockProduction() guards to prevent destructive operations in the wrong environment.

Step 6: Configure CI/CD

Set up GitHub Actions (or equivalent) with separate deployment jobs per environment, each using environment-specific secrets.

See detailed implementation for advanced patterns.

Output

  • Environment-specific configuration files
  • Secret management integration
  • Client factory with environment detection
  • CI/CD pipeline with environment isolation

Error Handling

IssueCauseSolution
Wrong API key usedEnv var mismatchVerify NODE_ENV matches key prefix
Secret fetch failsIAM permissionsCheck secrets manager access policy
Production data in devNo env guardAdd blockProduction() guards

Examples

Environment Checklist

CheckDevStagingProd
Separate API keyYesYesYes
Debug loggingOnOnOff
Mock mode availableYesYesNo
Secret managerNoYesYes
Rate limit tierLowMediumHigh

Resources

Stats
Stars1669
Forks210
Last CommitMar 11, 2026

Similar Skills