Skip to content
SkillModel-led2,123 tokens in use

environments

Keep development and production apart in an AI-built app: named targets, separate keys, a variables doc and env schema, safe migrations, secret rotation, backups with restore drills.

680 stars on the repository MIT Licensephuryn/product-engineering · app-stack/skills/environments
claude plugin install app-stack@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing environments costs

43tokens idle
2,123tokens in use
16,382tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure11/25
  • Examples3/15
  • Output10/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers