make-env-setup

Get this machine ready to build a Make App: select the appropriate toolchain, verify Make login, and initialize a project folder only for a new App. Run it on a new machine, and again whenever the tools need updating. Use makecli for resource/deploy operations and the owning skills for implementation.

Safety Rules

• Do not print or store tokens, cookies, Authorization headers, passwords, or secrets.
• Do not manually create PRD, DSL, Service, or UI files; only run makecli app init in the selected directory.
• Interactive secret entry must be completed by the user. Do not ask the user to paste secrets into chat.
• Do not install pnpm through npm. For a new or explicitly migrated App, use the fixed Corepack/pnpm baseline below. An existing compatible npm or Yarn App keeps its declared installer and lockfile; this environment skill must not switch it to pnpm.

Select Project Mode

• For a new App or a user-requested explicit runtime migration, follow the fixed Node.js/Corepack/pnpm baseline below. Runtime migration itself belongs to make-app-runtime; do not change an existing repository's manifests or lockfile in this setup flow.
• For an existing Make App without an explicit migration, inspect its workspace packageManager, Node engines, Node-selection file, lockfile and CI/install workflow before choosing tools. Keep the compatible declared Node and package manager, including npm or Yarn. Do not add Corepack or pnpm merely to update the local environment. If these declarations disagree, the needed runtime is unclear, or the target platform build image is incompatible, stop and report the blocker to make-app-runtime rather than guessing or creating another lockfile.
• If the target folder or new-versus-existing mode is unclear, ask the user before choosing a project runtime or initializing a folder.

Install Or Update Toolchain