home / skills / jeremylongshore / claude-code-plugins-plus-skills / gamma-multi-env-setup

This skill configures Gamma across development, staging, and production with environment isolation and secret management for reliable multi-environment

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill gamma-multi-env-setup

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.1 KB
---
name: gamma-multi-env-setup
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".
allowed-tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Gamma Multi-Environment Setup

## Overview
Configure Gamma across development, staging, and production environments with proper isolation and secrets management.

## 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: Environment Configuration Structure
```typescript
// config/gamma.config.ts
interface GammaConfig {
  apiKey: string;
  baseUrl: string;
  timeout: number;
  retries: number;
  debug: boolean;
}

type Environment = 'development' | 'staging' | 'production';

const configs: Record<Environment, Partial<GammaConfig>> = {
  development: {
    baseUrl: 'https://api.gamma.app/v1',
    timeout: 60000,
    retries: 1,
    debug: true,
  },
  staging: {
    baseUrl: 'https://api.gamma.app/v1',
    timeout: 45000,
    retries: 2,
    debug: true,
  },
  production: {
    baseUrl: 'https://api.gamma.app/v1',
    timeout: 30000,
    retries: 3,
    debug: false,
  },
};

export function getConfig(): GammaConfig {
  const env = (process.env.NODE_ENV || 'development') as Environment;
  const envConfig = configs[env];

  return {
    apiKey: process.env.GAMMA_API_KEY!,
    ...envConfig,
  } as GammaConfig;
}
```

### Step 2: Environment-Specific API Keys
```bash
# .env.development
GAMMA_API_KEY=gamma_dev_xxx...
GAMMA_MOCK=false
NODE_ENV=development

# .env.staging
GAMMA_API_KEY=gamma_staging_xxx...
GAMMA_MOCK=false
NODE_ENV=staging

# .env.production
GAMMA_API_KEY=gamma_prod_xxx...
GAMMA_MOCK=false
NODE_ENV=production
```

### Step 3: Secret Management Integration
```typescript
// lib/secrets.ts
import { SecretsManager } from '@aws-sdk/client-secrets-manager';

const secretsManager = new SecretsManager({ region: 'us-east-1' });

interface SecretCache {
  value: string;
  expiresAt: number;
}

const cache: Map<string, SecretCache> = new Map();
const CACHE_TTL = 300000; // 5 minutes

export async function getSecret(name: string): Promise<string> {
  const cached = cache.get(name);
  if (cached && cached.expiresAt > Date.now()) {
    return cached.value;
  }

  const env = process.env.NODE_ENV || 'development';
  const secretName = `gamma/${env}/${name}`;

  const response = await secretsManager.getSecretValue({
    SecretId: secretName,
  });

  const value = response.SecretString!;
  cache.set(name, { value, expiresAt: Date.now() + CACHE_TTL });

  return value;
}

// Usage
const apiKey = await getSecret('api-key');
```

### Step 4: Client Factory
```typescript
// lib/gamma-factory.ts
import { GammaClient } from '@gamma/sdk';
import { getConfig } from '../config/gamma.config';
import { getSecret } from './secrets';

let clients: Map<string, GammaClient> = new Map();

export async function getGammaClient(): Promise<GammaClient> {
  const env = process.env.NODE_ENV || 'development';

  if (clients.has(env)) {
    return clients.get(env)!;
  }

  const config = getConfig();

  // In production, fetch from secret manager
  const apiKey = env === 'production'
    ? await getSecret('api-key')
    : config.apiKey;

  const client = new GammaClient({
    apiKey,
    baseUrl: config.baseUrl,
    timeout: config.timeout,
    retries: config.retries,
    debug: config.debug,
  });

  clients.set(env, client);
  return client;
}
```

### Step 5: Environment Guards
```typescript
// lib/env-guards.ts
export function requireProduction(): void {
  if (process.env.NODE_ENV !== 'production') {
    throw new Error('This operation requires production environment');
  }
}

export function blockProduction(): void {
  if (process.env.NODE_ENV === 'production') {
    throw new Error('This operation is blocked in production');
  }
}

// Usage
async function deleteAllPresentations() {
  blockProduction(); // Safety guard

  const gamma = await getGammaClient();
  const presentations = await gamma.presentations.list();

  for (const p of presentations) {
    await gamma.presentations.delete(p.id);
  }
}

async function runMigration() {
  requireProduction(); // Ensure correct environment

  // Migration logic
}
```

### Step 6: CI/CD Environment Configuration
```yaml
# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches:
      - develop    # → staging
      - main       # → production

jobs:
  deploy-staging:
    if: github.ref == 'refs/heads/develop'
    runs-on: ubuntu-latest
    environment: staging
    steps:
      - uses: actions/checkout@v4
      - name: Deploy to Staging
        env:
          GAMMA_API_KEY: ${{ secrets.GAMMA_API_KEY_STAGING }}
          NODE_ENV: staging
        run: |
          npm ci
          npm run build
          npm run deploy:staging

  deploy-production:
    if: github.ref == 'refs/heads/main'
    runs-on: ubuntu-latest
    environment: production
    steps:
      - uses: actions/checkout@v4
      - name: Deploy to Production
        env:
          GAMMA_API_KEY: ${{ secrets.GAMMA_API_KEY_PRODUCTION }}
          NODE_ENV: production
        run: |
          npm ci
          npm run build
          npm run deploy:production
```

## Environment Checklist

| 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 |
| Error reporting | Console | Sentry | Sentry |

## Resources
- [Gamma Environments Guide](https://gamma.app/docs/environments)
- [12-Factor App Config](https://12factor.net/config)

## Next Steps
Proceed to `gamma-observability` for monitoring setup.

Overview

This skill configures Gamma across development, staging, and production environments with clear isolation, per-environment API keys, and CI/CD integration. It provides patterns for environment detection, secret retrieval, client construction, and safety guards to prevent dangerous operations in production.

How this skill works

It defines an environment-aware configuration structure and selects settings based on NODE_ENV. Secrets are fetched from a secret manager (with caching) for sensitive production credentials while non-production uses env files or CI variables. A client factory builds and caches Gamma clients per environment, and guard helpers enforce environment-specific restrictions for risky operations.

When to use it

  • Setting up Gamma for multi-environment deployments (dev/staging/prod).
  • Implementing environment-specific API keys and secrets management.
  • Integrating Gamma config into CI/CD pipelines and Git branch workflows.
  • Adding runtime guards to prevent production accidents.
  • Standardizing timeouts, retries, and debug modes by environment.

Best practices

  • Use separate Gamma API keys per environment and store production keys in a secrets manager (Vault, AWS Secrets Manager).
  • Keep NODE_ENV canonical values (development, staging, production) and derive config from it. Use CI to inject environment variables for deployments.
  • Cache secrets with a short TTL to reduce calls to secret stores while allowing rotation. Avoid hardcoding secrets in repos or images.
  • Centralize client creation in a factory to reuse clients and ensure consistent settings (timeout, retries, baseUrl).
  • Add explicit environment guards for destructive or high-risk operations to prevent accidental runs in production.

Example use cases

  • Local development: .env.development with debug enabled and a dev API key for quick iteration.
  • Staging deployment: CI job uses GAMMA_API_KEY_STAGING and NODE_ENV=staging to validate changes before production.
  • Production rollout: CI injects GAMMA_API_KEY_PRODUCTION; secrets manager supplies keys at runtime with caching.
  • Admin tooling: blockProduction() prevents mass-deletion scripts from running against production presentations.
  • Migrations: requireProduction() guarantees migration scripts run only in the intended environment.

FAQ

How should I store Gamma API keys for production?

Store production API keys in a secrets manager (AWS Secrets Manager, Vault) and fetch them at runtime; avoid embedding keys in code or images.

Can I use the same client instance across environments?

No—create and cache separate clients keyed by environment to ensure each environment uses its own credentials and settings.