iterate/iterate · Archived

creating-an-app

Create a new Cloudflare app in this repo with the expected package scripts, Doppler shape, and CI workflow wiring.

First seen Jul 30, 2026

Installation

$ npx skills add iterate/iterate --skill creating-an-app

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from iterate/iterate · top by installs.

npx skills add iterate/iterate

Browse all from iterate/iterate

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 198
License LICENSE
Default branch main
Open issues 4
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,523 B
  • docs SUMMARY.md 137 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Creating An App

Use this when adding a new Cloudflare app under apps/.

Keep the app contract small. Each app owns a handful of tsx scripts under apps/<app>/scripts/, exposed as package scripts and built on the shared deploy primitives in scripts/lib/ (see scripts/lib/deploy-app.ts):

  • deploy — pnpm run deploy --env <name> (build → wrangler deploy with atomic

secrets → smoke)

  • ensure-resources — create-only Cloudflare resource provisioning
  • erase-data — wipe an env's data without deleting the worker
  • gen:wrangler — expand the generated, gitignored wrangler.jsonc from the

root envs.ts

  • test:e2e if the app has live preview tests

The package scripts should own only the app action. Doppler selection belongs outside the app script (doppler run --config <env> -- pnpm run deploy).

CI Workflows

CI and deploy workflows are hand-written Depot CI YAML in .depot/workflows/ (see docs/depot-ci.md).

The current pattern is:

  1. Copy an existing deploy workflow (for example

.depot/workflows/deploy-semaphore.yml) to .depot/workflows/deploy-<app>.yml and edit the app name, Doppler project, deploy command, and paths filters directly.

  1. If the app participates in PR previews, wire it into the repo preview

router in scripts/preview/preview.ts.

  1. Depot registers triggers from the default branch, so a new workflow file

only starts running after it lands on main.

Preview deploys do not live in app-local routers anymore. They run through the repo preview router:

doppler run --project _shared --config prd -- pnpm preview sync --pull-request-number 1234
doppler run --project _shared --config prd -- pnpm preview cleanup --pull-request-number 1234

Workflow rules:

  • PR pushes deploy a leased preview_N
  • pushes to main deploy prd
  • PR deploys update the managed preview section in the PR body
  • main deploy successes and failures post to Slack via scripts/ci/notify.ts

Do not add preview logic back into apps/<app>/scripts/router.ts just to satisfy CI.

Doppler

Use the new-doppler-project skill for the project/config setup.

The app package should work with:

doppler run --project <app> --config preview_2 -- pnpm run deploy --env preview_2
doppler run --project <app> --config prd -- pnpm run deploy --env prd