@mr.dj2u/knowledge 0.1.3 → 0.1.5

package/dist/content/guides/post-create-onboarding.md

@@ -42,17 +42,19 @@ mds mcp install --dry-run         # preview merge before writing
 Restart the host (or run `claude mcp reload`) and the MDS prompts are
 available from any workspace.
 
-Two prompts and several callable MDS MCP tools ship with the server:
-
+Two prompts and several callable MDS MCP tools ship with the server:
+
 - `create_expo_super_stack` — invoke from a **parent folder** (e.g.
   `F:\ReactNativeApps`) when the app folder does not exist yet. This is
-  now a thin orchestration prompt: the real guided intake happens
-  through `create_expo_super_stack_intake_step`, generation happens
-  through `create_expo_super_stack_generate`, and diagnostics come from
-  `mds_runtime_versions`.
-- `onboard_new_expo_app` — invoke from **inside an existing Expo app
-  folder** (a freshly generated one or a year-old project). Runs the
-  intake → normalize → plan → scaffold flow.
+  now a thin orchestration prompt: `mds_runtime_versions` checks for
+  stale installs, `create_expo_super_stack_resolve_info` resolves
+  project memory in one call when `info.md` is available,
+  `create_expo_super_stack_intake_step` is only the manual fallback for
+  missing or ambiguous answers, and generation happens through
+  `create_expo_super_stack_generate`.
+- `onboard_new_expo_app` — invoke from **inside an existing Expo app
+  folder** (a freshly generated one or a year-old project). Runs the
+  intake → normalize → plan → scaffold flow.
 
 After generation, the user-dev should open the generated app folder
 directly in a new agent session and run `mds continue`. That fresh
@@ -69,33 +71,39 @@ delete the marker line.
 error so the same blocker stops CI and editor surfaces until the user
 fills the section or deletes the marker line.
 
-### What's new in the agentic prompts and tools
-
-- **PHASE 0 file intake.** The agent offers to digest an existing
-  `project/info.md` and `project/style.md` if the user has them already.
-  Questions whose answers are unambiguous in the file are skipped; the
-  agent asks for clarification only when the file is silent or unclear.
-  A reference template URL is mentioned in the prompt; the agent can
-  also inline the template on request.
+### What's new in the agentic prompts and tools
+
+- **PHASE 0 file intake.** The agent offers to digest an existing
+  `project/info.md` and `project/style.md` if the user has them already.
+  Questions whose answers are unambiguous in the file are skipped; the
+  agent asks for clarification only when the file is silent or unclear.
+  A reference template URL is mentioned in the prompt; the agent can
+  also inline the template on request.
+- **Shared resolver-first intake.** `create_expo_super_stack_resolve_info`
+  parses existing project memory up front, derives app naming details,
+  merges explicit overrides, returns missing or ambiguous fields, and
+  produces a ready-to-pass generate payload so the user is not forced
+  through redundant question-by-question discovery.
 - **Android TV alongside Apple TV.** The platform multi-select now
   includes Android TV. Android TV builds from the same Android target
   with leanback config in `app.json`; Apple TV is a separate tvOS build
   target via `react-native-tvos`. Selecting either records the intent
   in project memory.
-- **Shared CLI-backed intake contract.** The agentic CESS flow now uses
-  callable MCP tools backed by the shared `@mr.dj2u/cli` intake
-  contract. That keeps the questionnaire, defaults, dependency rules,
-  and flag mapping aligned with the published CLI behavior.
-- **No silent defaults.** Guided intake must explicitly collect answers
-  or explicitly present visible defaults. If the CESS intake tools are
-  unavailable, the agent should stop and tell the user to refresh the
-  plugin or MCP install instead of inventing `--mds-yes` defaults.
+- **Shared CLI-backed intake contract.** The agentic CESS flow now uses
+  callable MCP tools backed by the shared `@mr.dj2u/cli` intake
+  contract. That keeps the questionnaire, defaults, dependency rules,
+  and flag mapping aligned with the published CLI behavior.
+- **No silent defaults.** Guided intake must explicitly collect answers
+  or explicitly present visible defaults. If the CESS intake tools are
+  unavailable, the agent should stop and tell the user to refresh the
+  plugin or MCP install instead of inventing `--mds-yes` defaults.
 - **Runtime version diagnostics.** `mds_runtime_versions` reports the
-  active MCP server version, CLI version, and the published
-  `create-expo-super-stack@latest` generation path in use.
-- **Credits while waiting.** When generation kicks off, the agent
-  prints a recognition note for the upstream teams and individuals
-  whose work fills the MDS knowledge base.
+  active MCP server version, CLI version, concrete installed
+  `create-expo-super-stack` version, and the published generation path
+  in use.
+- **Credits while waiting.** When generation kicks off, the agent
+  prints a recognition note for the upstream teams and individuals
+  whose work fills the MDS knowledge base.
 - **Success message surfaced.** After a successful run, the agent
   quotes the generator's `MDS onboarding complete` tail block back
   verbatim so the Mr. DJ personal thank-you text appears in chat the same way
@@ -144,12 +152,12 @@ Copy-Item -Path .\plugins\vscode-copilot\.vscode\* -Destination .\.vscode -Recur
 ## Install Path & What This MD Is For
 
 - This markdown is a human- and agent-facing guide. It documents the onboarding flow and explains what the agent prompts do. It is used as input to the `packages/knowledge` build which generates plugin/agent bundles for Codex, Claude Code, and VS Code Copilot.
-- The agent itself is not this file — it is a runtime that loads generated prompts/skills from the plugin bundles or the MCP server. To activate the agent surfaces you must either:
-  - Install the MCP prompts via `mds mcp install --client <client>` (user or project scope), or
-  - Copy the generated plugin files from `plugins/vscode-copilot` / `plugins/codex` / `plugins/claude-code` into the target workspace or user profile and restart the corresponding client.
-- If a host keeps using stale prompt or plugin behavior after republish,
-  refresh the local plugin cache, reinstall the MDS MCP server, and run
-  `mds_runtime_versions` from the host surface to confirm which version
-  is actually active.
+- The agent itself is not this file — it is a runtime that loads generated prompts/skills from the plugin bundles or the MCP server. To activate the agent surfaces you must either:
+  - Install the MCP prompts via `mds mcp install --client <client>` (user or project scope), or
+  - Copy the generated plugin files from `plugins/vscode-copilot` / `plugins/codex` / `plugins/claude-code` into the target workspace or user profile and restart the corresponding client.
+- If a host keeps using stale prompt or plugin behavior after republish,
+  refresh the local plugin cache, reinstall the MDS MCP server, and run
+  `mds_runtime_versions` from the host surface to confirm which version
+  is actually active.
 
 If you want, I can: regenerate the VS Code bundle now, copy the assets into the current workspace, and verify Copilot sees the prompts. Say "Do it" and I'll run the build and copy steps for you.

package/dist/content/patterns/project/configuration-patterns.md

@@ -51,8 +51,8 @@ Configuration patterns establish consistent strategies for managing app configur
     
     "platforms": ["ios", "android", "web"],
     
-    "sdkVersion": "56.0.0",
-    "runtimeVersion": "56.0.0",
+    "sdkVersion": "56.0.0",
+    "runtimeVersion": "56.0.0",
     
     "web": {
       "output": "static",
@@ -178,7 +178,7 @@ export default ({ config }) => {
   "dependencies": {
     "react": "^19.0.0",
     "react-native": "^0.83.0",
-    "expo": "^56.0.0",
+    "expo": "^56.0.0",
     "expo-router": "^3.0.0",
     "zustand": "^4.4.0",
     "drizzle-orm": "^0.30.0",
@@ -456,4 +456,4 @@ export function useConfig() {
 ---
 
 *Pattern extracted from production repositories: DJsPortfolio, time2pay, not-hot-dog*
-*Examples: app.json, app.config.js, metro.config.js, babel.config.js, tsconfig.json*
+*Examples: app.json, app.config.js, metro.config.js, babel.config.js, tsconfig.json*

package/dist/content/patterns/project/documentation-org.md

@@ -66,7 +66,7 @@ truth and should not make changes that conflict with those files.
 Personal portfolio and project showcase for David J Grimsley.
 
 ## Core Stack
-- **Framework**: Expo SDK 56 + React Native 0.85
+- **Framework**: Expo SDK 56 + React Native 0.85
 - **Routing**: Expo Router (file-based)
 - **Styling**: Uniwind v1.2.6 + Tailwind v4
 - **State**: Zustand (atomic stores)

package/dist/content/patterns/project/monorepo-structure.md

@@ -179,7 +179,7 @@ ignore:
     
     "react": "^19.0.0",
     "react-native": "^0.83.0",
-    "expo": "^56.0.0",
+    "expo": "^56.0.0",
     "expo-router": "^3.0.0",
     "zustand": "^4.4.0"
   },

package/dist/content/prompts/create-expo-super-stack.md

@@ -1,6 +1,6 @@
 # /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.
+Create a new Expo app with the MDS Super Stack flow, using callable MDS MCP tools as the guided intake surface and the Super Stack generator as the scaffold source of truth.
 
 ## Arguments
 
@@ -9,14 +9,37 @@ 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`.
+1. Call `mds_runtime_versions` first to inspect the active runtime and invocation path.
+2. If the user pasted or attached `info.md` / project memory, call `create_expo_super_stack_resolve_info` once with `parentDir`, `appName`, `infoMarkdown`, optional `styleMarkdown`, and any explicit user overrides.
+3. Treat the resolver `answers` object as the canonical accumulated answers object.
+4. Ask exactly one question per turn only for `missingQuestionIds` or `ambiguousQuestionIds`.
+5. Do not restart intake with one answer at a time after a successful resolve call.
+6. If no `info.md` is available, fall back to `create_expo_super_stack_intake_step` and always pass the full accumulated `answers` object.
+7. When the resolver returns `confirm`, summarize `summaryLines` and ask the user for one final confirmation.
+8. After explicit confirmation, print the waiting message below, then call `create_expo_super_stack_generate` with the resolver `generateInput` and `confirmed: true`.
+
+## Waiting Message Before Generate
+
+After the user confirms, print this block before running the generator so they have something useful to read while scaffolding runs:
+
+Generating now. This typically takes 2-5 minutes. While we wait, let's shout out and recognize how this is working.
+
+create-expo-super-stack by Mr. DJ (who also built this agentic flow) wraps create-expo-stack by Roni OSS with major contributions by Dan Stepanov (NativeWind). Big thanks to them and to several other teams and individuals whose work and educational materials fill Mr. DJ's Dev Suite knowledge base:
+
+- Expo team (Evan Bacon for Expo Router, Brent Vatne, Charlie Cheever, and the broader Expo crew)
+- React and React Native core teams
+- Software Mansion (Reanimated, Gesture Handler, Screens, Worklets; Krzysztof Magiera and team)
+- Supabase, Drizzle, and Zustand teams
+- Adam Wathan and the Tailwind CSS team (the foundation Uniwind and NativeWind build on)
+- Janic Duplessis for "The real cost of React Native animations: benchmarking every approach"
+- Simon Grimm of Galaxies.dev
+- Beto Adrian Maldonado of codewithbeto.dev
+- Vadim of notJust.dev
+- William Candillon for the React Native animation deep-dive content
+- Catalin Miron for the React Native animation tutorials
+- Infinite Red / Jamon Holmgren for Ignite and the broader RN community
+
+Their contributions to the software development community are what fill the pages of Mr. DJ's Dev Suite knowledge base, alongside contributions and organization by Mr. DJ. Please enjoy the experience of the Mr. DJ's Dev Suite plugin as you continue your development.
 
 ## Failure Behavior
 
@@ -25,8 +48,12 @@ Create a new Expo app with the MDS Super Stack flow, using the published CESS CL
 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.
 
+Warn only when `mds_runtime_versions.warnings` is non-empty or when the user expected different versions than the runtime reports.
+Do not describe the normal published install path as a fallback, and do not mention `npm exec` or `npx` to the user unless there is an actual runtime problem they need to act on.
+
 ## 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`.
+- If those Super Stack artifacts are missing, treat generation as a failure or partial scaffold and say so clearly instead of presenting it as a normal success.
 - 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/dist/content/skills/super-stack-startup.md

@@ -17,10 +17,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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mr.dj2u/knowledge",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Skills, patterns, guides, and rules for Expo development (MCP resources)",
   "type": "module",
   "files": [