📋 Shared Instructions: shared-instructions.md — Cross-cutting concerns.

Local Dev

Starts ms app dev in the project's working directory. The CLI runs two servers — a dev script (Vite or equivalent, default port 8080) and a config server — and prints the App Player URL the user opens in their browser.

This skill does NOT deploy to the cloud. For that, use /deploy.

Workflow

Memory Bank → 2. Verify Project + Env → 3. Start Dev Server → 4. Hand Off URL

Step 1: Check Memory Bank

Read memory-bank.md from the project root (the project the user has cd'd into, or the path captured from a prior skill invocation) for context — the app slug/GUID and which environment this project targets — so you can confirm you're starting the right app.

ms app dev does not need environmentId or appId passed to it: it runs in the project working directory and reads ms.config.json itself. The memory bank is only for orienting yourself; if it's missing, that's fine — skip straight to Step 2.