@mr.dj2u/cli 0.1.12 → 0.1.14

package/bundles/claude-code/.claude-plugin/plugin.json

@@ -1,20 +1,20 @@
-{
-  "name": "mr-djs-dev-suite",
-  "displayName": "Mr. DJ's Dev Suite",
-  "version": "0.1.9",
-  "description": "Expo review, Doctor, onboarding, deployment readiness, and project continuation workflows for Claude Code, backed by callable MDS MCP tools.",
-  "author": {
-    "name": "DJ Grimsley",
-    "url": "https://davidjgrimsley.com"
-  },
-  "homepage": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
-  "repository": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
-  "license": "MIT",
-  "keywords": [
-    "expo",
-    "react-native",
-    "mcp",
-    "doctor",
-    "claude-code"
-  ]
-}
+{
+  "name": "mr-djs-dev-suite",
+  "displayName": "Mr. DJ's Dev Suite",
+  "version": "0.1.10",
+  "description": "Expo review, Doctor, onboarding, deployment readiness, and project continuation workflows for Claude Code, backed by callable MDS MCP tools.",
+  "author": {
+    "name": "DJ Grimsley",
+    "url": "https://davidjgrimsley.com"
+  },
+  "homepage": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
+  "repository": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
+  "license": "MIT",
+  "keywords": [
+    "expo",
+    "react-native",
+    "mcp",
+    "doctor",
+    "claude-code"
+  ]
+}

package/bundles/claude-code/.mcp.json

@@ -1,11 +1,11 @@
-{
-  "mcpServers": {
-    "mr-djs-dev-suite": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@mr.dj2u/mcp-server@0.1.6"
-      ]
-    }
-  }
-}
+{
+  "mcpServers": {
+    "mr-djs-dev-suite": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@mr.dj2u/mcp-server@0.1.7"
+      ]
+    }
+  }
+}

package/bundles/claude-code/agents/mds.md

@@ -1,36 +1,36 @@
----
-name: mds
-description: Use for Mr. DJ's Dev Suite Expo project work: Doctor scans, project review, onboarding, deployment readiness, and phase-based continuation.
-model: inherit
-skills:
-  - deployment
-  - debugging
-  - continue-development
-  - project-onboarding
-  - expo-router-architecture
-  - expo-ssr-safety
-  - env-vars
-  - seo-metadata
----
-
-# MDS Agent
-
-You are the Mr. DJ's Dev Suite agent for Expo projects. Treat callable MDS MCP tools as the runtime behavior surface and plugin markdown as guidance only.
-
-## Tool Routing
-
-- Use `continue_project` before choosing phase work from `project/todo.md`.
-- Use `doctor_scan_project` before release, broad refactors, or git handoff.
-- Use `doctor_scan_file` for focused route, env, SSR, or API changes.
-- Use `generate_refactor_plan` before moving architecture across folders.
-- Use `generate_deploy_checklist` before release or client handoff.
-- Use `list_skills`, `get_skill`, and `get_guide` before giving MDS-specific guidance.
-
-## Guardrails
-
-- Treat `project/` as the source of truth for product intent, style, roadmap, and technical rules.
-- Keep route files thin, env secrets server-only, and release work gated by Doctor checks.
-- Prefer official Expo/React Native guidance for framework mechanics; MDS adds project memory, checks, defaults, and workflows.
-- Do not skip unresolved `# TodoForContext(optional):` markers before implementation.
-- When a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, use commands such as `mds doctor`, `mds continue`, and `mds report`.
+---
+name: mds
+description: Use for Mr. DJ's Dev Suite Expo project work: Doctor scans, project review, onboarding, deployment readiness, and phase-based continuation.
+model: inherit
+skills:
+  - deployment
+  - debugging
+  - continue-development
+  - project-onboarding
+  - expo-router-architecture
+  - expo-ssr-safety
+  - env-vars
+  - seo-metadata
+---
+
+# MDS Agent
+
+You are the Mr. DJ's Dev Suite agent for Expo projects. Treat callable MDS MCP tools as the runtime behavior surface and plugin markdown as guidance only.
+
+## Tool Routing
+
+- Use `continue_project` before choosing phase work from `project/todo.md`.
+- Use `doctor_scan_project` before release, broad refactors, or git handoff.
+- Use `doctor_scan_file` for focused route, env, SSR, or API changes.
+- Use `generate_refactor_plan` before moving architecture across folders.
+- Use `generate_deploy_checklist` before release or client handoff.
+- Use `list_skills`, `get_skill`, and `get_guide` before giving MDS-specific guidance.
+
+## Guardrails
+
+- Treat `project/` as the source of truth for product intent, style, roadmap, and technical rules.
+- Keep route files thin, env secrets server-only, and release work gated by Doctor checks.
+- Prefer official Expo/React Native guidance for framework mechanics; MDS adds project memory, checks, defaults, and workflows.
+- Do not skip unresolved `# TodoForContext(optional):` markers before implementation.
+- When a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, use commands such as `mds doctor`, `mds continue`, and `mds report`.

package/bundles/claude-code/commands/create-expo-super-stack.md

@@ -1,32 +1,34 @@
-# /create-expo-super-stack
-
-Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
-
-## Arguments
-
-- `parentDir`: folder where the new app directory should be created.
-- `appName`: app folder name.
-
-## Required MDS MCP Tool Flow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Drive intake with `create_expo_super_stack_intake_step`.
-3. Ask exactly one question per turn.
-4. Always show the returned default and options.
-5. Never invent or silently accept defaults on the user's behalf.
-6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
-7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
-8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
-
-## Failure Behavior
-
-1. If the guided intake or generate tools are unavailable, stop.
-2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
-3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
-4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
-
-## Verification And Output
-
-- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
-- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.
+# /create-expo-super-stack
+
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
+
+## Arguments
+
+- `parentDir`: folder where the new app directory should be created.
+- `appName`: app folder name.
+
+## Required MDS MCP Tool Flow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. If the user pasted or attached `info.md` / project memory, call `create_expo_super_stack_extract_info` first.
+3. Seed the returned answers into `create_expo_super_stack_intake_step` and use intake only for missing or ambiguous questions.
+4. Ask exactly one question per turn.
+5. Always show the returned default and options.
+6. Never invent or silently accept defaults on the user's behalf.
+7. If extraction found the app name, do not ask a second display-name question.
+8. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+9. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+10. Then call `create_expo_super_stack_generate` with `confirmed: true`.
+
+## Failure Behavior
+
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
+
+## Verification And Output
+
+- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
+- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/claude-code/skills/create-expo-super-stack/SKILL.md

@@ -15,13 +15,15 @@ Create a new Expo app with the MDS Super Stack flow, using the published CESS CL
 ## Required MDS MCP Tool Flow
 
 1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Drive intake with `create_expo_super_stack_intake_step`.
-3. Ask exactly one question per turn.
-4. Always show the returned default and options.
-5. Never invent or silently accept defaults on the user's behalf.
-6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
-7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
-8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
+2. If the user pasted or attached `info.md` / project memory, call `create_expo_super_stack_extract_info` first.
+3. Seed the returned answers into `create_expo_super_stack_intake_step` and use intake only for missing or ambiguous questions.
+4. Ask exactly one question per turn.
+5. Always show the returned default and options.
+6. Never invent or silently accept defaults on the user's behalf.
+7. If extraction found the app name, do not ask a second display-name question.
+8. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+9. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+10. Then call `create_expo_super_stack_generate` with `confirmed: true`.
 
 ## Failure Behavior
 

package/bundles/claude-code/skills/super-stack-startup/SKILL.md

@@ -21,10 +21,10 @@ Run generator + onboarding as one guided flow, keep agent-facing wording sourced
 
 ## Preferred structure
 
-- Keep startup conversation in plain language and summarize choices before execution.
-- Keep generation details in scripts/flags, but keep user-facing flow conversational.
-- Keep post-generation workflow phase-based using the generated `project/todo.md`, and derive that roadmap from normalized `project/info.md` before handoff.
-- Prefer shared knowledge content over duplicating long onboarding prose in plugin or MCP wrappers.
+- Keep startup conversation in plain language and summarize choices before execution.
+- Keep generation details in scripts/flags, but keep user-facing flow conversational.
+- Keep post-generation workflow phase-based using the generated `project/todo.md`, and derive that roadmap from normalized `project/info.md` before handoff.
+- Prefer shared knowledge content over duplicating long onboarding prose in plugin or MCP wrappers.
 
 ## Example fix
 

package/bundles/codex/.codex-plugin/plugin.json

@@ -1,42 +1,42 @@
-{
-  "name": "mr-djs-dev-suite",
-  "version": "0.1.9",
-  "description": "MDS Expo development workflows for review, onboarding, deployment readiness, and project continuation.",
-  "author": {
-    "name": "DJ Grimsley",
-    "url": "https://davidjgrimsley.com"
-  },
-  "homepage": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
-  "repository": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
-  "license": "MIT",
-  "keywords": [
-    "expo",
-    "react-native",
-    "mcp",
-    "doctor",
-    "onboarding",
-    "codex-plugin"
-  ],
-  "skills": "./skills/",
-  "mcpServers": "./.mcp.json",
-  "interface": {
-    "displayName": "Mr. DJ's Dev Suite",
-    "shortDescription": "Expo review, doctor, onboarding, and deploy workflows powered by MDS MCP tools",
-    "longDescription": "Generate and use MDS skills plus command playbooks for Expo project review, onboarding, deployment prep, SEO fixes, and phase-based continuation, with callable MDS MCP tools for runtime behavior.",
-    "developerName": "MDS",
-    "category": "Coding",
-    "capabilities": [
-      "Interactive",
-      "Read",
-      "Write"
-    ],
-    "websiteURL": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
-    "defaultPrompt": [
-      "Review my Expo project and give me the next safe implementation steps.",
-      "Run a deployment-readiness check with Doctor and fix blockers first.",
-      "Continue the next task from my project/todo.md using MDS phase order."
-    ],
-    "brandColor": "#0A6A6A",
-    "screenshots": []
-  }
-}
+{
+  "name": "mr-djs-dev-suite",
+  "version": "0.1.10",
+  "description": "MDS Expo development workflows for review, onboarding, deployment readiness, and project continuation.",
+  "author": {
+    "name": "DJ Grimsley",
+    "url": "https://davidjgrimsley.com"
+  },
+  "homepage": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
+  "repository": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
+  "license": "MIT",
+  "keywords": [
+    "expo",
+    "react-native",
+    "mcp",
+    "doctor",
+    "onboarding",
+    "codex-plugin"
+  ],
+  "skills": "./skills/",
+  "mcpServers": "./.mcp.json",
+  "interface": {
+    "displayName": "Mr. DJ's Dev Suite",
+    "shortDescription": "Expo review, doctor, onboarding, and deploy workflows powered by MDS MCP tools",
+    "longDescription": "Generate and use MDS skills plus command playbooks for Expo project review, onboarding, deployment prep, SEO fixes, and phase-based continuation, with callable MDS MCP tools for runtime behavior.",
+    "developerName": "MDS",
+    "category": "Coding",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://github.com/DavidJGrimsley/mrdj-dev-suite",
+    "defaultPrompt": [
+      "Review my Expo project and give me the next safe implementation steps.",
+      "Run a deployment-readiness check with Doctor and fix blockers first.",
+      "Continue the next task from my project/todo.md using MDS phase order."
+    ],
+    "brandColor": "#0A6A6A",
+    "screenshots": []
+  }
+}

package/bundles/codex/.mcp.json

@@ -1,11 +1,11 @@
-{
-  "mcpServers": {
-    "mr-djs-dev-suite": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@mr.dj2u/mcp-server@0.1.6"
-      ]
-    }
-  }
-}
+{
+  "mcpServers": {
+    "mr-djs-dev-suite": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@mr.dj2u/mcp-server@0.1.7"
+      ]
+    }
+  }
+}

package/bundles/codex/README.md

@@ -1,51 +1,51 @@
-# Mr. DJ's Dev Suite Codex Plugin
-
-The Mr. DJ's Dev Suite Codex plugin bundle is generated from `packages/knowledge` and ships the Codex-native MDS surface: plugin manifest, MCP server config, generated skills, and command prompts.
-
-## What's Included
-
-- Codex plugin manifest: `.codex-plugin/plugin.json`
-- MCP server config: `.mcp.json`
-- Generated skills: `skills/<skill-id>/SKILL.md`
-- Command prompt files: `commands/*.md`
-
-The source of truth for skills remains `packages/knowledge/src/content/skills`.
-Runtime behavior comes from callable MDS MCP tools exposed by `@mr.dj2u/mcp-server`.
-
-## One-Command Install
-
-Project scope installs MCP plus the local marketplace/plugin enable blocks into `.codex/config.toml`, copies this plugin into `plugins/mr-djs-dev-suite`, and registers it in `.agents/plugins/marketplace.json`:
-
-```sh
-mds agent install --client codex --scope project --target /path/to/your/expo-app
-mds agent verify --client codex --scope project --target /path/to/your/expo-app
-```
-
-User scope installs MCP plus the local marketplace/plugin enable blocks into `~/.codex/config.toml`, copies the plugin into `~/plugins/mr-djs-dev-suite`, and registers it in `~/.agents/plugins/marketplace.json`:
-
-```sh
-mds agent install --client codex --scope user
-mds agent verify --client codex --scope user
-mds agent install --client codex --scope user --dry-run
-```
-
-After install, restart Codex so it picks up the local marketplace. Then type `@Mr. DJ's Dev Suite` in chat to get the install pop-up, hit Install, and use `@Mr. DJ's Dev Suite` in Codex Desktop or the Codex extension for VS Code.
-
-If Codex keeps using stale behavior after republish, refresh the local plugin cache, reinstall the MDS MCP server, then run `mds_runtime_versions` from the host surface to confirm which versions are active.
-
-## MCP-Only Fallback
-
-Use this when you only want the callable MDS MCP tools/prompts and not the plugin/skills bundle:
-
-```sh
-mds mcp install --client codex --scope project --target /path/to/your/expo-app
-mds mcp install --client codex --scope user
-```
-
-## Regenerate
-
-```sh
-pnpm --filter @mr.dj2u/knowledge build
-```
-
-Do not edit generated plugin skills directly; update `packages/knowledge` and rebuild.
+# Mr. DJ's Dev Suite Codex Plugin
+
+The Mr. DJ's Dev Suite Codex plugin bundle is generated from `packages/knowledge` and ships the Codex-native MDS surface: plugin manifest, MCP server config, generated skills, and command prompts.
+
+## What's Included
+
+- Codex plugin manifest: `.codex-plugin/plugin.json`
+- MCP server config: `.mcp.json`
+- Generated skills: `skills/<skill-id>/SKILL.md`
+- Command prompt files: `commands/*.md`
+
+The source of truth for skills remains `packages/knowledge/src/content/skills`.
+Runtime behavior comes from callable MDS MCP tools exposed by `@mr.dj2u/mcp-server`.
+
+## One-Command Install
+
+Project scope installs MCP plus the local marketplace/plugin enable blocks into `.codex/config.toml`, copies this plugin into `plugins/mr-djs-dev-suite`, and registers it in `.agents/plugins/marketplace.json`:
+
+```sh
+mds agent install --client codex --scope project --target /path/to/your/expo-app
+mds agent verify --client codex --scope project --target /path/to/your/expo-app
+```
+
+User scope installs MCP plus the local marketplace/plugin enable blocks into `~/.codex/config.toml`, copies the plugin into `~/plugins/mr-djs-dev-suite`, and registers it in `~/.agents/plugins/marketplace.json`:
+
+```sh
+mds agent install --client codex --scope user
+mds agent verify --client codex --scope user
+mds agent install --client codex --scope user --dry-run
+```
+
+After install, restart Codex so it picks up the local marketplace. Then type `@Mr. DJ's Dev Suite` in chat to get the install pop-up, hit Install, and use `@Mr. DJ's Dev Suite` in Codex Desktop or the Codex extension for VS Code.
+
+If Codex keeps using stale behavior after republish, refresh the local plugin cache, reinstall the MDS MCP server, then run `mds_runtime_versions` from the host surface to confirm which versions are active.
+
+## MCP-Only Fallback
+
+Use this when you only want the callable MDS MCP tools/prompts and not the plugin/skills bundle:
+
+```sh
+mds mcp install --client codex --scope project --target /path/to/your/expo-app
+mds mcp install --client codex --scope user
+```
+
+## Regenerate
+
+```sh
+pnpm --filter @mr.dj2u/knowledge build
+```
+
+Do not edit generated plugin skills directly; update `packages/knowledge` and rebuild.

package/bundles/codex/commands/create-expo-super-stack.md

@@ -1,32 +1,34 @@
-# /create-expo-super-stack
-
-Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
-
-## Arguments
-
-- `parentDir`: folder where the new app directory should be created.
-- `appName`: app folder name.
-
-## Required MDS MCP Tool Flow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Drive intake with `create_expo_super_stack_intake_step`.
-3. Ask exactly one question per turn.
-4. Always show the returned default and options.
-5. Never invent or silently accept defaults on the user's behalf.
-6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
-7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
-8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
-
-## Failure Behavior
-
-1. If the guided intake or generate tools are unavailable, stop.
-2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
-3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
-4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
-
-## Verification And Output
-
-- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
-- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.
+# /create-expo-super-stack
+
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
+
+## Arguments
+
+- `parentDir`: folder where the new app directory should be created.
+- `appName`: app folder name.
+
+## Required MDS MCP Tool Flow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. If the user pasted or attached `info.md` / project memory, call `create_expo_super_stack_extract_info` first.
+3. Seed the returned answers into `create_expo_super_stack_intake_step` and use intake only for missing or ambiguous questions.
+4. Ask exactly one question per turn.
+5. Always show the returned default and options.
+6. Never invent or silently accept defaults on the user's behalf.
+7. If extraction found the app name, do not ask a second display-name question.
+8. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+9. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+10. Then call `create_expo_super_stack_generate` with `confirmed: true`.
+
+## Failure Behavior
+
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
+
+## Verification And Output
+
+- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
+- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/codex/skills/super-stack-startup/SKILL.md

@@ -1,34 +1,34 @@
-# Skill: Super Stack Startup
-
-Use when kicking off a new app with `create-expo-super-stack` and transitioning into phase-based MDS development.
-
-## Main rule
-
-Run generator + onboarding as one guided flow, keep agent-facing wording sourced from `packages/knowledge`, and let the current CLI implementation remain the execution source of truth.
-
-## Checks
-
-- Confirm command runs from a parent directory where the app folder does not already exist.
-- Confirm stack choices and MDS intake values are captured before generation.
-- Confirm generated app includes project memory and onboarding next-step output.
-- Confirm prompt and skill text stay thin and defer detailed behavior to the canonical knowledge package.
-- Confirm unresolved context markers are resolved before coding begins.
-- Confirm follow-up uses `mds continue` from inside the generated app folder.
-
-## Preferred structure
-
-- Keep startup conversation in plain language and summarize choices before execution.
-- Keep generation details in scripts/flags, but keep user-facing flow conversational.
-- Keep post-generation workflow phase-based using the generated `project/todo.md`, and derive that roadmap from normalized `project/info.md` before handoff.
-- Prefer shared knowledge content over duplicating long onboarding prose in plugin or MCP wrappers.
-
-## Example fix
-
-- Problem: User runs generation inside an existing app folder and gets mixed state artifacts.
-- Fix: Restart from parent directory, regenerate cleanly, then continue in a new app-folder session.
-
-## Agent behavior
-
-- Prevent ambiguous execution context and confirm folder target before running generation.
-- Delegate framework/template primitives to upstream Expo tooling, then apply MDS memory shaping, defaults, and continue-workflow conventions.
-- Update `packages/knowledge` first when the wording or flow changes, then regenerate downstream surfaces from it.
+# Skill: Super Stack Startup
+
+Use when kicking off a new app with `create-expo-super-stack` and transitioning into phase-based MDS development.
+
+## Main rule
+
+Run generator + onboarding as one guided flow, keep agent-facing wording sourced from `packages/knowledge`, and let the current CLI implementation remain the execution source of truth.
+
+## Checks
+
+- Confirm command runs from a parent directory where the app folder does not already exist.
+- Confirm stack choices and MDS intake values are captured before generation.
+- Confirm generated app includes project memory and onboarding next-step output.
+- Confirm prompt and skill text stay thin and defer detailed behavior to the canonical knowledge package.
+- Confirm unresolved context markers are resolved before coding begins.
+- Confirm follow-up uses `mds continue` from inside the generated app folder.
+
+## Preferred structure
+
+- Keep startup conversation in plain language and summarize choices before execution.
+- Keep generation details in scripts/flags, but keep user-facing flow conversational.
+- Keep post-generation workflow phase-based using the generated `project/todo.md`, and derive that roadmap from normalized `project/info.md` before handoff.
+- Prefer shared knowledge content over duplicating long onboarding prose in plugin or MCP wrappers.
+
+## Example fix
+
+- Problem: User runs generation inside an existing app folder and gets mixed state artifacts.
+- Fix: Restart from parent directory, regenerate cleanly, then continue in a new app-folder session.
+
+## Agent behavior
+
+- Prevent ambiguous execution context and confirm folder target before running generation.
+- Delegate framework/template primitives to upstream Expo tooling, then apply MDS memory shaping, defaults, and continue-workflow conventions.
+- Update `packages/knowledge` first when the wording or flow changes, then regenerate downstream surfaces from it.