Promptles
Multi-Step

Describe Environments and Stages

When setting up CI/CD, describe each environment (staging, production), what triggers deployment to it, and what stages must pass first. Claude needs to understand the full pipeline topology -- not just 'set up CI' but the complete flow from code push to deployment.

Where you'll practice this

3 Promptles scenarios teach this principle directly. Each one drops you into a real engineering ticket and asks you to write the prompt you'd send to Claude Code.

  • The CI Pipeline

    Your TypeScript project needs a CI/CD pipeline using GitHub Actions. The project uses `pnpm` for package management, has ESLint for linting, Vitest for testing, and builds with `tsc`. You want: a CI workflow that runs lint, test, and build on every pull request; automatic…

  • The CI Pipeline

    Your team has a Postman collection (`postman/api-tests.json`) and two environment files (`postman/staging.env.json`, `postman/production.env.json`) checked into the repo. You want to run the collection in GitHub Actions on every pull request (against staging) and on every merge…

  • Tag and Release

    Your deploy job works, but releases are untracked — there's no version tag or changelog when code ships. You want to add a release step that runs after a successful deploy on `main`: it should create a git tag from the version in `package.json` and publish a GitHub Release with…

Other principles in Multi-Step