env-variables

Official

Safely manage env vars across your monorepo.

Authorhyperjumptech
Version1.0.0
Installs0

System Documentation

What problem does it solve?

Add, update, or manage environment variables in this Next.js monorepo using T3 Env and env-to-t3. Use when the user asks to add an env variable, update env.example, generate env types, work with @hermes/env or @mediapulse/env, or configure per-app environment variables.

Core Features & Use Cases

  • Update the correct env.example (or env.*.example) under packages/hermes/env/ or packages/mediapulse/env/. Add a comment explaining the purpose and where to obtain the value. Add env-to-t3 annotations after the value. Example: ACME_API_TOKEN=your-token-here #required
  • Regenerate the typed env object after changes.
  • Import from @hermes/env or @mediapulse/env instead of reading process.env directly.
  • Share .env for local development by using dev-bootstrap.sh to merge examples and symlink apps to the correct domain.

Quick Start

Regenerate the typed env object after updating env examples and import it from @hermes/env or @mediapulse/env.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: env-variables
Download link: https://github.com/hyperjumptech/mediapulse/archive/main.zip#env-variables

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.