This skill covers how an AI-built app separates development from production and moves configuration and secrets between them. It sets rules for naming the target of every command, giving each environment its own resources and keys, and recording every variable in three places in the same change.
It also covers changing schema while code still serves, rotating and revoking secrets in the right order, handling a leaked key, and treating a backup as unverified until a restore drill has run. The rules keep the principle and swap mechanisms for stacks other than Next.js, Supabase, Clerk and Netlify.
What You Get
- A binding rule set: stated targets, separate resources and keys, server-only secrets, a three-part change for every new variable
- An environments doc with verified, dated resource mappings and an environment log
- A variables doc with one row per variable and a map of where each secret copy lives
- A migration window procedure with expand and contract steps for columns and grants
- Runbooks for incidents, backups and rebuilding both environments from empty accounts
Common Use Cases
- Adding an environment variable with its placeholder, doc row and schema check
- Setting up production for the first time before the first users
- Rotating a provider key without breaking holders that still use the old one
- Planning a rename or drop of a column while old builds still serve
What Makes It Unique
It treats the environment itself as the thing to verify, with dated read-backs, and bans operator commands that inherit a target from a config file. A planned rotation revokes last, a backup counts only after a restore drill, and a screen may not promise automatic deletion until a job performs it.
Under The Hood
The skill is instructions and reference markdown, with no scripts. Following it, the agent runs shell and provider commands that name an environment explicitly, applies database migrations by hand with a connection string, and edits files in the product: the env schema, .env.example, and the variables, environments and backlog docs. It handles secrets and provider tokens the owner supplies, writes generated production secrets to an operator file outside the development checkout, and may open a quick tunnel to show development to the owner.