Skip to content
Skills Library
Programming · Building & coding

dev

/dev

Runs a Microsoft App locally with hot reload via `ms app dev`. Use when starting or restarting local development and surfacing the App Player URL.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Runs a Microsoft App locally with hot reload via `ms app dev`. Use when starting or restarting local development and surfacing the App Player URL.

Original author description

Runs a Microsoft App locally with hot reload via `ms app dev`. Use when starting or restarting local development and surfacing the App Player URL.

How it works

  1. Workflow
Original SKILL.md headings · 91 lines, 849 words
SKILL.md preview
---
name: dev
description: Runs a Microsoft App locally with hot reload via `ms app dev`. Use when starting or restarting local development and surfacing the App Player URL.
allowed-tools: Read Grep Bash AskUserQuestion
---

**📋 Shared Instructions: [shared-instructions.md](../../shared/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

```bash
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:

```bash
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:

```bash
$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. |

If the user invoked `/dev` without arguments, run plain `$BIN app dev` first; surface flags only if the run fails.

**Run in the background** (`run_in_background: true`) so the session can continue. Stream stdout via `Monitor` until the line `Ready. You can play your app locally at: <URL>` appears — that's the App Player URL.

### Step 4: Open the Browser and Hand Off the URL

**Open the browser automatically** — run `Start-Process "<captured URL>"` (Windows) or `open "<captured URL>"` (macOS) / `xdg-open "<captured URL>"` (Linux) so the user sees their app immediately without copy-pasting. If the open command fails, fall back to printing the URL.

Print the App Player URL as a **markdown link** so it stays clickable even in narrow terminals. **Also show the URL on its own line** — markdown links can render as plain label text in some environments (e.g. tables), hiding the actual URL from the user.

```
Local dev running — opened the app in your default browser.

Local URL: [Open app in browser](<captured URL>)
           <captured URL>
Stop:      Ctrl+C in the dev terminal (or kill the background task).
Restart:   /dev (from this project folder)
```

Do **not** show the git remote URL in the dev summary — it's an internal detail that confuses users who expect a browser-openable link. The only URL to surface is the App Player URL printed by `ms app dev` (the domain varies by cloud/region — always use the exact URL the CLI outputs, never hardcode the host).

Then add a one-liner reminder of the iterate → preview → deploy loop:

> "The browser tab hot-reloads as I edit code — tell me what to change. When you're happy with it, I'll commit + push your changes, run `ms app play --mode preview` for a cloud preview URL in your environment, and then ask if you want me to `/deploy`."

When the user signals readiness, follow the **Ready-to-Ship Gate** in [shared-instructions.md](../../shared/shared-instructions.md) — commit, push, preview, then ask about `/deploy`.

If the dev server prints an error during startup (port conflict, missing `ms.config.json`, expired auth), stop the background task, surface the error verbatim, and propose the targeted fix:

| Error                                                | Fix                                                                                         |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| `EADDRINUSE` on 8080                                  | Re-run with `$BIN app dev --port 8081` (or kill whatever's on 8080).                        |
| `ms.config.json not found`                         | The user is in the wrong directory, or this isn't a Microsoft App workspace. Verify and stop. |
| `Authentication failed` (token expired)               | Run `$BIN auth login` (interactive) and retry.                                              |
| `Failed to fetch app metadata for <app-id>`           | App was deleted in the service. Confirm with `$BIN app list --json` and restore or recreate.|

Do NOT push or deploy from this skill, even if the user mentions it mid-session — bounce them to `/deploy` (which requires explicit confirmation).

> **Sharing a cloud preview:** The App Player URL from `ms app dev` is local-only. Once code is pushed to main, use `/play` (`ms app play --mode preview`) to open a cloud-hosted preview URL that works for others without a deploy.

Versions

RepositoryScoreLicence
This page · microsoft/Copilot-Managed-Runtime95MIT
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
slopus/happy100MIT
automattic/wordpress-activitypub100MIT
lucastamoios/skills100MIT
gpshead/cpython-skills100CC0-1.0
microsoft/managed-apps95MIT
heliohq/ship95MIT

Database snapshot: 13.11.2026 · package version 4897d13c74a5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100clerk-local-dev-loop
    Set up local development workflow with Clerk. Use when configuring development environment, testing auth locally, or setting up hot reload with Clerk. Trigger with phrases like "clerk local dev", "clerk development", "test clerk locally", "clerk dev environment".
  • 100create-app
    Creates apps on Copilot Managed Runtime using React and Vite. Use when scaffolding a new app with `ms app create` and ending on local dev with `ms app dev`.
  • 86run-app
    Use when the user wants this project's app running locally to test.
  • 100vercel-local-dev-loop
    Configure Vercel local development with vercel dev, environment variables, and hot reload. Use when setting up a development environment, testing serverless functions locally, or establishing a fast iteration cycle with Vercel. Trigger with phrases like "vercel dev setup",…
  • 100firecrawl-local-dev-loop
    Configure FireCrawl local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with FireCrawl. Trigger with phrases like "firecrawl dev setup", "firecrawl local development",…
  • 100fireflies-local-dev-loop
    Configure Fireflies.ai local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Fireflies.ai. Trigger with phrases like "fireflies dev setup", "fireflies local…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.