dev

📋 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

1. 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.

Step 2: Verify Project + Env

test -f ms.config.json || { echo "Not in a Microsoft App workspace (no ms.config.json)."; exit 1; }

Probe the CLI binary and confirm auth:

BIN=ms
$BIN auth status

If auth status reports the wrong UPN or is signed out, prompt the user to fix it before continuing (ms auth login). Don't try to repair auth silently — wrong-account dev sessions waste time downstream.

Step 3: Start the Dev Server

Default invocation:

$BIN app dev

Flags worth surfacing (only when the user mentions a need):

Flag	When to use
--port <n> (-p)	Port 8080 is busy. Pick another (e.g., --port 8081).
--local-app-url <url> (-l)	The user's Vite/dev script is on a non-default URL (default http://localhost:3000).
--config-only (-C)	Only run the config server. Useful when the user runs npm run dev separately.