How do I install the Recreate Production skill?

Run npx skillmds@latest add iterate/recreate-production in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Recreate Production safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Recreate Production?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Recreate Production free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Recreate Production?

iterate (@iterate) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Recreate Production by iterate — Agent Skill

Name: Recreate Production
Author: iterate

File contents

Recreate production

Use the project-seed CLI. A seed is a small semantic snapshot, not a database dump and not a stream export. Read Project seeds before operating.

Capture

pnpm --dir apps/os cli project-seed capture --project <slug>

Direct capture defaults to os/prd. Pass --environment <config> or --file <path> when needed. The default file is ~/.iterate/project-seeds/<slug>.project-seed.yaml; it is written mode 0600.

Run project-seed check --file <path> --project <slug> and report the non-secret summary. Never commit or print the archive.

Restore

doppler run --project os --config prd -- \
  pnpm --dir apps/os cli project-seed check \
  --file <archive.yaml> --project <slug>

doppler run --project os --config prd -- \
  pnpm --dir apps/os cli project-seed apply \
  --file <archive.yaml> --project <slug>

apply restores Auth users, minimum organization membership, the exact project ID, hostnames, inbound-email senders, generic secrets, supported integrations, and the config repository. It is convergent and proves its GitHub/local state and the served config commit before returning.

GitHub is authoritative. Every apply re-establishes the existing remote link without an initial push and imports its current default branch only when the local head differs. A local-only config repository comes from the archived file tree. Other project repositories are deliberately outside the recovery seed.

Boundaries

Never export, import, or replay stream histories, offsets, processor output, idempotency keys, SQLite rows, or Durable Object state.
Secret capture reads the current encrypted secret cell only. Ciphertext remains usable while the exact project/path binding and production SECRET_ENCRYPTION_KEY remain unchanged; apply decrypts locally and sends plaintext through the owning create/connect command for fresh encryption.
Supported built-in integrations are Slack, GitHub, and Google. A connected unsupported integration makes capture fail instead of silently omitting it.
Cloudflare custom-hostname metadata is not part of the seed. The deployed worker's project-hostname KV directory is the ownership and routing source of truth.
Do not erase data, deploy workers, push GitHub changes, or perform externally visible provider smokes unless the user included that action.
Keep the stable archive. Delete only disposable local work created during the run.

If apply fails, fix the current command or archive and rerun it. Do not repair around it by appending old events.

---name: recreate-productiondescription: Capture or restore a selected OS project after a deliberate proof-of-concept production erase.---# Recreate productionUse the project-seed CLI. A seed is a small semantic snapshot, not a databasedump and not a stream export. Read[Project seeds](../../../apps/os/docs/project-seeds.md) before operating.## Capture```bashpnpm --dir apps/os cli project-seed capture --project <slug>```Direct capture defaults to `os/prd`. Pass `--environment <config>` or`--file <path>` when needed. The default file is`~/.iterate/project-seeds/<slug>.project-seed.yaml`; it is written mode 0600.Run `project-seed check --file <path> --project <slug>` and report thenon-secret summary. Never commit or print the archive.## Restore```bashdoppler run --project os --config prd -- \ pnpm --dir apps/os cli project-seed check \ --file <archive.yaml> --project <slug>doppler run --project os --config prd -- \ pnpm --dir apps/os cli project-seed apply \ --file <archive.yaml> --project <slug>````apply` restores Auth users, minimum organization membership, the exact projectID, hostnames, inbound-email senders, generic secrets, supported integrations,and the config repository. It is convergent and proves its GitHub/local stateand the served config commit before returning.GitHub is authoritative. Every apply re-establishes the existing remote linkwithout an initial push and imports its current default branch only when thelocal head differs. A local-only config repository comes from the archivedfile tree. Other project repositories are deliberately outside the recoveryseed.## Boundaries- Never export, import, or replay stream histories, offsets, processor output, idempotency keys, SQLite rows, or Durable Object state.- Secret capture reads the current encrypted secret cell only. Ciphertext remains usable while the exact project/path binding and production `SECRET_ENCRYPTION_KEY` remain unchanged; `apply` decrypts locally and sends plaintext through the owning create/connect command for fresh encryption.- Supported built-in integrations are Slack, GitHub, and Google. A connected unsupported integration makes capture fail instead of silently omitting it.- Cloudflare custom-hostname metadata is not part of the seed. The deployed worker's project-hostname KV directory is the ownership and routing source of truth.- Do not erase data, deploy workers, push GitHub changes, or perform externally visible provider smokes unless the user included that action.- Keep the stable archive. Delete only disposable local work created during the run.If `apply` fails, fix the current command or archive and rerun it. Do not repairaround it by appending old events.

Frequently asked questions

Recreate Production