@mr.dj2u/knowledge 0.1.7 → 0.1.8

package/dist/content/prompts/continue-development.md

@@ -1,35 +1,35 @@
-# /continue-development
-
-Resume work on an onboarded project by following MDS phase order from `project/todo.md`.
-
-## Arguments
-
-- `projectPath`: onboarded app path (default: current directory).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Call `continue_project` first to get the active-phase brief.
-3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
-4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
-
-## MDS Routing Guardrails
-
-- Treat a request to continue development with MDS as a request for the MDS MCP tool and phase rules first.
-- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
-- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI flow:
-   - `mds continue <projectPath>`
-   - `mds doctor <projectPath>` when blockers are unclear.
-3. If `mds` is not on PATH, invoke the published CLI by binary name:
-   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
-
-## Verification And Output
-
-- Confirm the chosen task belongs to the active phase or has an explicit deferral note.
-- Output: selected next task, blockers, and validation commands to run after implementation.
+# /continue-development
+
+Resume work on an onboarded project by following MDS phase order from `project/todo.md`.
+
+## Arguments
+
+- `projectPath`: onboarded app path (default: current directory).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `continue_project` first to get the active-phase brief.
+3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
+4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
+
+## MDS Routing Guardrails
+
+- Treat a request to continue development with MDS as a request for the MDS MCP tool and phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI flow:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
+
+## Verification And Output
+
+- Confirm the chosen task belongs to the active phase or has an explicit deferral note.
+- Output: selected next task, blockers, and validation commands to run after implementation.

package/dist/content/prompts/fix-seo.md

@@ -1,29 +1,29 @@
-# /fix-seo
-
-Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix verification.
-
-## Arguments
-
-- `projectPath`: Expo project path (default: current directory).
-- `routeOrFile`: optional route/file focus for targeted checks.
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Pull `get_skill` for `seo-metadata`.
-3. Optionally run `doctor_scan_file` for focused route files, then `doctor_scan_project` for full checks.
-4. Use `knowledge_list_resources` (`kind: "rule"`) to ensure canonical/indexing strategy is complete.
-5. Implement metadata, canonical, robots, and sitemap corrections in route ownership boundaries.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI checks:
-   - `mds doctor <projectPath> --ci`
-   - Run project-specific web build/preview commands to verify metadata output.
-
-## Verification And Output
-
-- Confirm canonical tags, social metadata, and sitemap/robots behavior on affected routes.
-- Output: changed files, resolved SEO gaps, and any remaining manual verification steps.
+# /fix-seo
+
+Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix verification.
+
+## Arguments
+
+- `projectPath`: Expo project path (default: current directory).
+- `routeOrFile`: optional route/file focus for targeted checks.
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Pull `get_skill` for `seo-metadata`.
+3. Optionally run `doctor_scan_file` for focused route files, then `doctor_scan_project` for full checks.
+4. Use `knowledge_list_resources` (`kind: "rule"`) to ensure canonical/indexing strategy is complete.
+5. Implement metadata, canonical, robots, and sitemap corrections in route ownership boundaries.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI checks:
+   - `mds doctor <projectPath> --ci`
+   - Run project-specific web build/preview commands to verify metadata output.
+
+## Verification And Output
+
+- Confirm canonical tags, social metadata, and sitemap/robots behavior on affected routes.
+- Output: changed files, resolved SEO gaps, and any remaining manual verification steps.

package/dist/content/prompts/onboard-new-expo-app.md

@@ -1,11 +1,11 @@
-# /onboard-new-expo-app
-
-Run onboarding intake for an existing Expo app folder.
-
-## Arguments
-
-- `projectPath`: existing Expo app path (default: current directory).
-
-## MCP Prompt Notes
-
-This canonical spec backs the `onboard_new_expo_app` MCP prompt metadata. The runtime onboarding prompt text is generated from the server-side onboarding template so it can include current context and path-dependent instructions.
+# /onboard-new-expo-app
+
+Run onboarding intake for an existing Expo app folder.
+
+## Arguments
+
+- `projectPath`: existing Expo app path (default: current directory).
+
+## MCP Prompt Notes
+
+This canonical spec backs the `onboard_new_expo_app` MCP prompt metadata. The runtime onboarding prompt text is generated from the server-side onboarding template so it can include current context and path-dependent instructions.

package/dist/content/prompts/prepare-deploy.md

@@ -1,29 +1,29 @@
-# /prepare-deploy
-
-Prepare an Expo project for release using deployment-focused skills plus Doctor parity checks.
-
-## Arguments
-
-- `projectPath`: release candidate project path (default: current directory).
-- `includeSeo`: whether to include web metadata/indexing checks (default: `true` when web is targeted).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Run `doctor_scan_project` in `ci` mode for release parity.
-3. Pull `get_skill` for `deployment`; if web is involved also pull `seo-metadata`.
-4. Use `knowledge_list_resources` (`kind: "rule"`) to confirm env hygiene, SSR safety, and metadata requirements.
-5. Produce a release checklist mapped to current failing checks.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI path:
-   - `mds doctor <projectPath> --ci`
-   - Run project scripts: `lint`, `type-check`, `test`, and production build/profile scripts.
-
-## Verification And Output
-
-- Re-run `doctor_scan_project` (or CLI equivalent) until blockers are cleared.
-- Output: release readiness status, unresolved blockers, and rollback/readiness notes.
+# /prepare-deploy
+
+Prepare an Expo project for release using deployment-focused skills plus Doctor parity checks.
+
+## Arguments
+
+- `projectPath`: release candidate project path (default: current directory).
+- `includeSeo`: whether to include web metadata/indexing checks (default: `true` when web is targeted).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Run `doctor_scan_project` in `ci` mode for release parity.
+3. Pull `get_skill` for `deployment`; if web is involved also pull `seo-metadata`.
+4. Use `knowledge_list_resources` (`kind: "rule"`) to confirm env hygiene, SSR safety, and metadata requirements.
+5. Produce a release checklist mapped to current failing checks.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI path:
+   - `mds doctor <projectPath> --ci`
+   - Run project scripts: `lint`, `type-check`, `test`, and production build/profile scripts.
+
+## Verification And Output
+
+- Re-run `doctor_scan_project` (or CLI equivalent) until blockers are cleared.
+- Output: release readiness status, unresolved blockers, and rollback/readiness notes.

package/dist/content/prompts/project-research-plan.md

@@ -1,29 +1,29 @@
-# /project-research-plan
-
-Turn rough product notes/research into actionable MDS project memory and next-phase plan.
-
-## Arguments
-
-- `projectPath`: target project path (default: current directory).
-- `inputs`: attached notes/docs to normalize into canonical memory files.
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Pull `get_skill` for `research-plan-intake` (and `project-onboarding` when onboarding context is mixed in).
-3. Call `knowledge_list_resources` for `guide` and `reference` resources as needed for structure and validation.
-4. Normalize clear context directly; ask focused follow-up only where ambiguity changes implementation direction.
-5. Update project memory files and produce an implementation-ready next-phase plan.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI fallback:
-   - Use `mds onboard <projectPath>` for structured intake when memory files are missing.
-   - Use `mds continue <projectPath>` after memory normalization to select the next task.
-
-## Verification And Output
-
-- Confirm `project/info.md`, `project/style.md`, and `project/todo.md` align with extracted research context.
-- Output: resolved unknowns, outstanding questions, and the recommended next implementation slice.
+# /project-research-plan
+
+Turn rough product notes/research into actionable MDS project memory and next-phase plan.
+
+## Arguments
+
+- `projectPath`: target project path (default: current directory).
+- `inputs`: attached notes/docs to normalize into canonical memory files.
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Pull `get_skill` for `research-plan-intake` (and `project-onboarding` when onboarding context is mixed in).
+3. Call `knowledge_list_resources` for `guide` and `reference` resources as needed for structure and validation.
+4. Normalize clear context directly; ask focused follow-up only where ambiguity changes implementation direction.
+5. Update project memory files and produce an implementation-ready next-phase plan.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI fallback:
+   - Use `mds onboard <projectPath>` for structured intake when memory files are missing.
+   - Use `mds continue <projectPath>` after memory normalization to select the next task.
+
+## Verification And Output
+
+- Confirm `project/info.md`, `project/style.md`, and `project/todo.md` align with extracted research context.
+- Output: resolved unknowns, outstanding questions, and the recommended next implementation slice.

package/dist/content/prompts/push-merge-loop.md

@@ -1,25 +1,25 @@
-# /push-merge-loop
-
-Execute the short PR iteration loop for the test branch with strict quality gates.
-
-## Goal
-
-Push intentional changes with a meaningful commit message, open/update a PR to `test`, poll for feedback and failed checks, fix issues, and merge to `test` once all checks are green.
-
-## Loop Rules
-
-1. Run `mds doctor --ci` before any git mutation.
-2. Stage only intentional files and create a meaningful commit message.
-3. Push branch and open or update a PR targeting `test`.
-4. Wait about 2 minutes, then poll PR comments, review threads, and failed checks.
-5. Fix issues locally, rerun Doctor, push updates, and poll again.
-6. Repeat polling/fix cycles up to 5 total iterations.
-7. Merge to `test` only when all required checks are green and no unresolved blocking feedback remains.
-
-## Guardrails
-
-- Do not merge when required checks are failing.
-- Do not skip Doctor between fix cycles.
-- Keep a concise changelog per iteration: what failed, what was changed, what passed.
-- If still failing after 5 cycles, stop and summarize remaining blockers with concrete next actions.
-
+# /push-merge-loop
+
+Execute the short PR iteration loop for the test branch with strict quality gates.
+
+## Goal
+
+Push intentional changes with a meaningful commit message, open/update a PR to `test`, poll for feedback and failed checks, fix issues, and merge to `test` once all checks are green.
+
+## Loop Rules
+
+1. Run `mds doctor --ci` before any git mutation.
+2. Stage only intentional files and create a meaningful commit message.
+3. Push branch and open or update a PR targeting `test`.
+4. Wait about 2 minutes, then poll PR comments, review threads, and failed checks.
+5. Fix issues locally, rerun Doctor, push updates, and poll again.
+6. Repeat polling/fix cycles up to 5 total iterations.
+7. Merge to `test` only when all required checks are green and no unresolved blocking feedback remains.
+
+## Guardrails
+
+- Do not merge when required checks are failing.
+- Do not skip Doctor between fix cycles.
+- Keep a concise changelog per iteration: what failed, what was changed, what passed.
+- If still failing after 5 cycles, stop and summarize remaining blockers with concrete next actions.
+

package/dist/content/prompts/review-expo-project.md

@@ -1,29 +1,29 @@
-# /review-expo-project
-
-Review an Expo project with MCP-first diagnostics and skill-guided remediation.
-
-## Arguments
-
-- `projectPath`: absolute or relative project path (default: current directory).
-- `mode`: Doctor mode (`fast`, `ci`, or `full`; default: `ci`).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Call `continue_project` to summarize current project state and blockers.
-3. Call `doctor_scan_project` with `projectPath` and `mode`.
-4. For each warning/error, call `doctor_explain_result`, then pull targeted guidance with `get_skill` (for example: `project-onboarding`, `debugging`, `deployment`).
-5. Call `knowledge_list_resources` with `kind: "guide"` if extra reference context is needed.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. If MCP still cannot run, use direct CLI flows:
-   - `mds continue <projectPath>`
-   - `mds doctor <projectPath> --ci`
-
-## Verification And Output
-
-- Re-run `doctor_scan_project` (or `mds doctor --ci`) after fixes.
-- Output: blocker summary, failing checks, recommended next task, and concrete follow-up commands.
+# /review-expo-project
+
+Review an Expo project with MCP-first diagnostics and skill-guided remediation.
+
+## Arguments
+
+- `projectPath`: absolute or relative project path (default: current directory).
+- `mode`: Doctor mode (`fast`, `ci`, or `full`; default: `ci`).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `continue_project` to summarize current project state and blockers.
+3. Call `doctor_scan_project` with `projectPath` and `mode`.
+4. For each warning/error, call `doctor_explain_result`, then pull targeted guidance with `get_skill` (for example: `project-onboarding`, `debugging`, `deployment`).
+5. Call `knowledge_list_resources` with `kind: "guide"` if extra reference context is needed.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. If MCP still cannot run, use direct CLI flows:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath> --ci`
+
+## Verification And Output
+
+- Re-run `doctor_scan_project` (or `mds doctor --ci`) after fixes.
+- Output: blocker summary, failing checks, recommended next task, and concrete follow-up commands.

package/dist/content/prompts/run-doctor.md

@@ -1,38 +1,38 @@
-# /run-doctor
-
-Run MDS Doctor as the primary health check for an Expo project.
-
-## Arguments
-
-- `projectPath`: project root path (default: current directory).
-- `mode`: `fast`, `ci`, or `full` (default: `ci`).
-- `runScripts`: whether Doctor should execute project scripts (default: `true` for `ci` mode).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Call `doctor_scan_project` with selected arguments.
-3. For each non-pass result, call `doctor_explain_result`.
-4. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
-
-## MDS Routing Guardrails
-
-- Treat a request to run MDS Doctor as a request for the MDS MCP tool, not as a request to run app-local npm scripts.
-- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
-- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI alternatives:
-   - `mds doctor <projectPath>`
-   - `mds doctor <projectPath> --ci`
-   - `mds doctor <projectPath> --json`
-3. If `mds` is not on PATH, invoke the published CLI by binary name:
-   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
-
-## Verification And Output
-
-- Re-run Doctor after each fix batch.
-- Output: check summary, blocking errors first, and the exact command used for re-check.
+# /run-doctor
+
+Run MDS Doctor as the primary health check for an Expo project.
+
+## Arguments
+
+- `projectPath`: project root path (default: current directory).
+- `mode`: `fast`, `ci`, or `full` (default: `ci`).
+- `runScripts`: whether Doctor should execute project scripts (default: `true` for `ci` mode).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `doctor_scan_project` with selected arguments.
+3. For each non-pass result, call `doctor_explain_result`.
+4. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
+
+## MDS Routing Guardrails
+
+- Treat a request to run MDS Doctor as a request for the MDS MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI alternatives:
+   - `mds doctor <projectPath>`
+   - `mds doctor <projectPath> --ci`
+   - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
+
+## Verification And Output
+
+- Re-run Doctor after each fix batch.
+- Output: check summary, blocking errors first, and the exact command used for re-check.

package/dist/content/prompts/wrap-up.md

@@ -1,67 +1,67 @@
-# /wrap-up
-
-Run the post-testing release wrap-up flow: final local checks, git inclusion confirmation, PR loop, and merge handling.
-
-## Goal
-
-When the developer says testing is complete, finish the handoff safely by:
-
-1. Marking completed todo items.
-2. Running `mds doctor --ci`.
-3. Reviewing `git status` and confirming intentionally excluded files.
-4. Running the publish/PR/check loop.
-5. Handling merge according to policy defaults and repo overrides.
-
-## Required Flow Order
-
-1. Update `project/todo.md` only for tasks clearly completed in this session.
-2. Run `mds doctor --ci` before any git mutation.
-3. Review `git status --short` and list changed files.
-4. Confirm any intentionally omitted files with the developer before staging.
-5. Publish through GitHub flow (branch push + PR).
-6. Poll checks and unresolved feedback.
-7. Fix failures locally, rerun Doctor, push updates, and poll again.
-8. Repeat up to 5 cycles total.
-
-## GitHub Skill Routing
-
-Use GitHub workflows in this order when available:
-
-1. `github` for repo/PR context and routing.
-2. `yeet` for commit/push/open-or-update PR flow.
-3. `gh-fix-ci` for failed checks/log inspection and CI-driven fix loops.
-4. `gh-address-comments` when unresolved review threads are blocking merge.
-
-## Merge Policy
-
-Evaluate policy in this order:
-
-1. Explicit user instruction in the current session.
-2. Optional repo config at `project/release-policy.json`.
-3. Defaults if config is absent.
-
-Supported repo config shape:
-
-```json
-{
-  "wrapUp": {
-    "autoMergeTest": true,
-    "autoMergeMain": false
-  }
-}
-```
-
-Default behavior:
-
-- Auto-merge to `test`: enabled.
-- Per-repo override: allowed.
-- Auto-merge to `main`: never allowed.
-
-If the workflow targets `main` directly (no `test` branch flow), stop before merge and tell the developer to merge manually.
-
-## Guardrails
-
-- Never auto-merge to `main`.
-- Do not skip `mds doctor --ci` between fix cycles.
-- Do not assume omitted files are intentional; confirm them.
-- If checks or blocking threads still fail after 5 cycles, stop and request human help with a concise blocker summary.
+# /wrap-up
+
+Run the post-testing release wrap-up flow: final local checks, git inclusion confirmation, PR loop, and merge handling.
+
+## Goal
+
+When the developer says testing is complete, finish the handoff safely by:
+
+1. Marking completed todo items.
+2. Running `mds doctor --ci`.
+3. Reviewing `git status` and confirming intentionally excluded files.
+4. Running the publish/PR/check loop.
+5. Handling merge according to policy defaults and repo overrides.
+
+## Required Flow Order
+
+1. Update `project/todo.md` only for tasks clearly completed in this session.
+2. Run `mds doctor --ci` before any git mutation.
+3. Review `git status --short` and list changed files.
+4. Confirm any intentionally omitted files with the developer before staging.
+5. Publish through GitHub flow (branch push + PR).
+6. Poll checks and unresolved feedback.
+7. Fix failures locally, rerun Doctor, push updates, and poll again.
+8. Repeat up to 5 cycles total.
+
+## GitHub Skill Routing
+
+Use GitHub workflows in this order when available:
+
+1. `github` for repo/PR context and routing.
+2. `yeet` for commit/push/open-or-update PR flow.
+3. `gh-fix-ci` for failed checks/log inspection and CI-driven fix loops.
+4. `gh-address-comments` when unresolved review threads are blocking merge.
+
+## Merge Policy
+
+Evaluate policy in this order:
+
+1. Explicit user instruction in the current session.
+2. Optional repo config at `project/release-policy.json`.
+3. Defaults if config is absent.
+
+Supported repo config shape:
+
+```json
+{
+  "wrapUp": {
+    "autoMergeTest": true,
+    "autoMergeMain": false
+  }
+}
+```
+
+Default behavior:
+
+- Auto-merge to `test`: enabled.
+- Per-repo override: allowed.
+- Auto-merge to `main`: never allowed.
+
+If the workflow targets `main` directly (no `test` branch flow), stop before merge and tell the developer to merge manually.
+
+## Guardrails
+
+- Never auto-merge to `main`.
+- Do not skip `mds doctor --ci` between fix cycles.
+- Do not assume omitted files are intentional; confirm them.
+- If checks or blocking threads still fail after 5 cycles, stop and request human help with a concise blocker summary.

package/dist/content/reference/create-expo-stack-uniwind.md

@@ -1,29 +1,29 @@
-# create-expo-stack Uniwind Exploration
-
-Source: https://github.com/roninoss/create-expo-stack
-
-## Findings
-
-- The project describes itself as an interactive CLI for `rn-new`.
-- It already supports multiple styling choices, including NativeWind,
-  Unistyles, StyleSheets, and Tamagui.
-- The README describes a per-file template model: base files live in a base
-  template folder, while optional package features live in package template
-  folders and use EJS to patch shared files.
-
-## Phase 1 Decision
-
-A friendly upstream Uniwind contribution should stay small:
-
-- add Uniwind as another styling option,
-- follow the existing package-slice template convention,
-- include `web` in Expo Router generated `app.json` platforms when web config
-  and dependencies are generated,
-- add focused Software Mansion core package options where they are not already
-  covered,
-- avoid MDS project memory files, MCP config, agent prompts, or richer
-  boilerplate,
-- keep the deeper post-create setup in `mds onboard` and
-  `create-expo-super-stack`.
-
-No local Phase 1 code should depend on the upstream fork or PR existing.
+# create-expo-stack Uniwind Exploration
+
+Source: https://github.com/roninoss/create-expo-stack
+
+## Findings
+
+- The project describes itself as an interactive CLI for `rn-new`.
+- It already supports multiple styling choices, including NativeWind,
+  Unistyles, StyleSheets, and Tamagui.
+- The README describes a per-file template model: base files live in a base
+  template folder, while optional package features live in package template
+  folders and use EJS to patch shared files.
+
+## Phase 1 Decision
+
+A friendly upstream Uniwind contribution should stay small:
+
+- add Uniwind as another styling option,
+- follow the existing package-slice template convention,
+- include `web` in Expo Router generated `app.json` platforms when web config
+  and dependencies are generated,
+- add focused Software Mansion core package options where they are not already
+  covered,
+- avoid MDS project memory files, MCP config, agent prompts, or richer
+  boilerplate,
+- keep the deeper post-create setup in `mds onboard` and
+  `create-expo-super-stack`.
+
+No local Phase 1 code should depend on the upstream fork or PR existing.