skills.rest
lgerard314
lgerard314OFFICIAL
Explore all skills by this author →
GitHub

secrets-and-config-safety

Enforce secrets and environment-config discipline across Next.js, Node, and AWS deployments.

Updated Aug 27, 2026
Search Tags:#secrets#secrets-manager#env-vars#rotation#parameter-store#nextjs-security
One-click install
npx skills add https://github.com/lgerard314/global-plugin --skill secrets-and-config-safety
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-and-config-safety
Source: https://github.com/lgerard314/global-plugin/tree/main/plugin/skills/secrets-and-config-safety
Command: npx skills add https://github.com/lgerard314/global-plugin --skill secrets-and-config-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Keep secrets out of source, out of logs, and out of client bundles; ensure environment-specific config is predictable and rotation-ready across server/client boundaries.

Core Features & Use Cases

  • Centralized startup validation with Zod to fail-fast on missing or malformed env vars.
  • Rotation-aware secret access patterns (TTL-cached Secrets Manager fetch) and per-environment config governance.
  • Guidance on Next.js NEXT_PUBLIC_* discipline and Parameter Store vs environment variables.

Quick Start

Consolidate all process.env reads behind a validated server env module and review NEXT_PUBLIC_* usage to prevent secret leakage.

Frequently Asked Questions about secrets-and-config-safety

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

FAQPage Schema
How do I prevent secrets from leaking into Next.js client bundles?▼

To prevent secret leakage in Next.js, you must review NEXT_PUBLIC_ usage and consolidate process.env reads behind a validated server env module. This boundary keeps secrets out of client bundles.

How do I validate environment variables at startup in Node.js?▼

You can validate environment variables at startup using Zod-based schemas to fail-fast on missing or malformed env vars. This centralized approach ensures predictable environment-specific configuration across deployments.

What is the best way to handle secret rotation in AWS?▼

For secret rotation in AWS, use TTL-cached Secrets Manager fetch patterns. This rotation-aware access method keeps credentials current across deployments without application restarts.

When should I use AWS Parameter Store vs environment variables for config?▼

Use AWS Parameter Store for dynamic or rotation-ready configuration, and environment variables for static startup config. This Skill codifies the config-store vs env-var decision process across Node and AWS deployments.

Can I enforce secrets and config discipline across server and client boundaries?▼

Yes, you can enforce config discipline across server/client boundaries by centralizing environment hierarchy conventions and using a structured review checklist. This prevents misconfiguration and keeps secrets out of logs.

Related Skills

Explore More Software Engineering Skills→
ekremmkasapekremmkasap

python-configuration

Externalize Python application configuration to environment variables with pydantic-settings.

Community
Advanced
sitharaj88sitharaj88
1

aws-secrets

Generate secure AWS Secrets Manager and SSM Parameter Store configurations.

Community
Advanced
AratKruglikAratKruglik
9

server-component-patterns

Determine Server or Client Component usage in Next.js app router layouts.

Community
Advanced
smith-hornsmith-horn
75

varlock

Mask environment variables and validate secrets via the Varlock CLI.

Official
Advanced