deploy-and-env

Configure deployment types and environment variables for T3 Turbo projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/leonardoacosta/central-claude --skill deploy-and-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-and-env
Source: https://github.com/leonardoacosta/central-claude/tree/main/skills/deploy-and-env
Command: npx skills add https://github.com/leonardoacosta/central-claude --skill deploy-and-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, auditable way to configure deployment pipelines and environment variables across Vercel, git-hook/homelab, and Docker-based projects while clarifying background vs foreground execution and notification behavior to prevent runaway tasks and secret leakage.

Core Features & Use Cases

  • Deployment type guidance: Distinguishes Vercel auto-builds from git-hook deployments and documents how each project category should be triggered and monitored.
  • Env var lifecycle: Describes Terraform-managed Vercel variables, local .env/.env.local patterns, and which values must remain machine-only versus deployed.
  • Background execution & notifications: Defines default background behavior, when to use --foreground, and safe notification routing via nexus-agent to avoid notification loops.
  • Use Case: Configure a T3 Turbo service to sync production secrets from Terraform, run CI-safe deploys on Vercel, and ensure local-only secrets remain out of CI while preserving TTS notification safety.

Quick Start

Ask the agent to configure deployment and environment variable management for your project, including Vercel terraform sync, .env inclusion rules, and background execution defaults.

Frequently Asked Questions about deploy-and-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage environment variables for Vercel deployments in a T3 Turbo project?

Manage Vercel environment variables in a T3 Turbo project by syncing production secrets through Terraform and applying specific .env/.env.local inclusion rules to keep local-only secrets out of CI pipelines.

What is the difference between Vercel auto-builds and git-hook deployments for homelab services?

Vercel auto-builds are triggered and monitored through the platform's CI system, whereas git-hook deployments rely on custom homelab triggers, requiring distinct configuration for Docker services and local execution.

How do I prevent runaway tasks during background execution and CI deploys?

Prevent runaway tasks by defining default background execution behavior and using the --foreground flag when necessary, while routing safe notifications through nexus-agent to avoid notification loops.

Can I use Terraform to synchronize environment variables across dev and prod environments?

Yes, Terraform manages Vercel variables across dev and prod environments, ensuring synchronized environment variable configuration during CI, local development, and deployment workflows.

What is the best way to keep local-only secrets out of CI pipelines?

Keep local-only secrets out of CI by enforcing strict .env/.env.local patterns that distinguish machine-only values from deployed variables, preventing secret leakage during builds and deployments.

Why does my notification routing create loops during background deployments?

Notification routing creates loops when safe routing through nexus-agent is not configured properly; defining default background behavior and explicit notification paths prevents these loops during deployments.