@mr.dj2u/knowledge 0.1.7 → 0.1.8

package/dist/content/skills/expo-ssr-safety.md

@@ -1,32 +1,32 @@
-# Skill: Expo SSR Safety
-
-Use when preparing or debugging Expo Router web/server output paths.
-
-## Main rule
-
-Assume server runtime first: guard browser-only APIs, isolate native-only code, and keep shared modules safe in both client and server contexts.
-
-## Checks
-
-- Guard `window`, `document`, `navigator`, `localStorage`, and `sessionStorage` access.
-- Confirm client-only packages are not imported by server/API execution paths.
-- Confirm storage/session access happens in client-safe lifecycle points.
-- Verify API routes and server modules do not rely on browser globals.
-- Validate dynamic imports or adapters for platform-specific behavior.
-
-## Preferred structure
-
-- Use small environment-check helpers for browser-global access.
-- Split client-only logic behind platform/runtime-specific modules.
-- Keep server-safe defaults and explicit fallbacks in shared utilities.
-
-## Example fix
-
-- Problem: Shared auth helper reads `localStorage` at module load and crashes SSR.
-- Fix: Move storage access into guarded runtime functions and provide a server-safe fallback.
-
-## Agent behavior
-
-- Fix crash-risk paths first, then clean up architecture.
-- Delegate framework SSR primitives to official Expo docs, then apply MDS-specific guard patterns and Doctor rule compatibility.
-
+# Skill: Expo SSR Safety
+
+Use when preparing or debugging Expo Router web/server output paths.
+
+## Main rule
+
+Assume server runtime first: guard browser-only APIs, isolate native-only code, and keep shared modules safe in both client and server contexts.
+
+## Checks
+
+- Guard `window`, `document`, `navigator`, `localStorage`, and `sessionStorage` access.
+- Confirm client-only packages are not imported by server/API execution paths.
+- Confirm storage/session access happens in client-safe lifecycle points.
+- Verify API routes and server modules do not rely on browser globals.
+- Validate dynamic imports or adapters for platform-specific behavior.
+
+## Preferred structure
+
+- Use small environment-check helpers for browser-global access.
+- Split client-only logic behind platform/runtime-specific modules.
+- Keep server-safe defaults and explicit fallbacks in shared utilities.
+
+## Example fix
+
+- Problem: Shared auth helper reads `localStorage` at module load and crashes SSR.
+- Fix: Move storage access into guarded runtime functions and provide a server-safe fallback.
+
+## Agent behavior
+
+- Fix crash-risk paths first, then clean up architecture.
+- Delegate framework SSR primitives to official Expo docs, then apply MDS-specific guard patterns and Doctor rule compatibility.
+

package/dist/content/skills/plugin-creation.md

@@ -1,41 +1,41 @@
-# Skill: MDS Plugin Creation
-
-Use when building or extending an MDS plugin bundle for any agent client (Claude Code, Codex, Cursor, etc.).
-
-## Main rule
-
-Plugins are thin bundles. `packages/knowledge` is the source of truth for skills, command prompts, checklists, and examples. Do not hand-author plugin skill/command copies in plugin folders.
-
-## Structure conventions
-
-Every MDS plugin lives in `plugins/<client-name>/`:
-
-```
-plugins/<client-name>/
-  README.md
-  CLAUDE.md            # Claude-specific merge instructions (if relevant)
-  .mcp.json
-  commands/            # generated command markdown from canonical prompt specs
-  skills/              # generated skill files
-```
-
-## Checks
-
-- Skill markdown lives only in `packages/knowledge/src/content/skills/`.
-- Prompt/command markdown lives only in `packages/knowledge/src/content/prompts/`.
-- `plugins/<client>/skills/` remains generated output and is not manually edited.
-- Commands reference real MCP tool names from `packages/mcp-server`.
-- MCP config uses the `mr-djs-dev-suite` server key.
-
-## Adding a plugin capability
-
-1. Add or update canonical content in `packages/knowledge/src/content/*`.
-2. Update canonical prompt metadata in `packages/knowledge/src/prompts/index.ts`.
-3. Regenerate outputs via `pnpm --filter @mr.dj2u/knowledge build`.
-4. Verify generated plugin assets under `plugins/codex/` and `plugins/claude-code/`.
-
-## Agent behavior
-
-- Prefer extending canonical knowledge specs over patching generated plugin files.
-- Keep command prompts action-oriented and generated from canonical prompt specs, with clear fallback paths.
-- Delegate framework guidance to Expo-owned skills/docs when available; layer MDS project-memory and workflow guidance on top.
+# Skill: MDS Plugin Creation
+
+Use when building or extending an MDS plugin bundle for any agent client (Claude Code, Codex, Cursor, etc.).
+
+## Main rule
+
+Plugins are thin bundles. `packages/knowledge` is the source of truth for skills, command prompts, checklists, and examples. Do not hand-author plugin skill/command copies in plugin folders.
+
+## Structure conventions
+
+Every MDS plugin lives in `plugins/<client-name>/`:
+
+```
+plugins/<client-name>/
+  README.md
+  CLAUDE.md            # Claude-specific merge instructions (if relevant)
+  .mcp.json
+  commands/            # generated command markdown from canonical prompt specs
+  skills/              # generated skill files
+```
+
+## Checks
+
+- Skill markdown lives only in `packages/knowledge/src/content/skills/`.
+- Prompt/command markdown lives only in `packages/knowledge/src/content/prompts/`.
+- `plugins/<client>/skills/` remains generated output and is not manually edited.
+- Commands reference real MCP tool names from `packages/mcp-server`.
+- MCP config uses the `mr-djs-dev-suite` server key.
+
+## Adding a plugin capability
+
+1. Add or update canonical content in `packages/knowledge/src/content/*`.
+2. Update canonical prompt metadata in `packages/knowledge/src/prompts/index.ts`.
+3. Regenerate outputs via `pnpm --filter @mr.dj2u/knowledge build`.
+4. Verify generated plugin assets under `plugins/codex/` and `plugins/claude-code/`.
+
+## Agent behavior
+
+- Prefer extending canonical knowledge specs over patching generated plugin files.
+- Keep command prompts action-oriented and generated from canonical prompt specs, with clear fallback paths.
+- Delegate framework guidance to Expo-owned skills/docs when available; layer MDS project-memory and workflow guidance on top.

package/dist/content/skills/production-server-patterns.md

@@ -1,31 +1,31 @@
-# Skill: Production Server Patterns
-
-Use when setting up or debugging how an Expo project serves production traffic.
-
-## Main rule
-
-Pick one explicit production serving mode per environment and codify it in scripts; avoid mixed runtime assumptions.
-
-## Checks
-
-- Confirm selected mode is documented: managed Expo/EAS, Express adapter, or dual-server.
-- Confirm serving scripts match the selected runtime (`npx expo serve`, `node server.js`, or dual process scripts).
-- Confirm routing boundaries are clear when app and API are separate services.
-- Confirm env var ownership differs correctly across app server and API server in dual-server mode.
-- Confirm “fresh” start scripts exist where server state/caches can cause drift.
-
-## Preferred structure
-
-- Define `serve:prod` and `serve:prod:fresh` scripts for the chosen mode.
-- Keep server bootstrap and adapter code in dedicated files/modules.
-- Keep deployment notes aligned with runtime mode in project memory.
-
-## Example fix
-
-- Problem: Team mixes Expo serve and custom Express commands, causing inconsistent behavior.
-- Fix: Select one primary mode per environment, standardize scripts, and document routing/env boundaries.
-
-## Agent behavior
-
-- Use the project’s declared serving mode unless a migration is explicitly requested.
-- Delegate framework runtime primitives to official Expo docs, then enforce MDS conventions for script consistency, environment boundaries, and operational clarity.
+# Skill: Production Server Patterns
+
+Use when setting up or debugging how an Expo project serves production traffic.
+
+## Main rule
+
+Pick one explicit production serving mode per environment and codify it in scripts; avoid mixed runtime assumptions.
+
+## Checks
+
+- Confirm selected mode is documented: managed Expo/EAS, Express adapter, or dual-server.
+- Confirm serving scripts match the selected runtime (`npx expo serve`, `node server.js`, or dual process scripts).
+- Confirm routing boundaries are clear when app and API are separate services.
+- Confirm env var ownership differs correctly across app server and API server in dual-server mode.
+- Confirm “fresh” start scripts exist where server state/caches can cause drift.
+
+## Preferred structure
+
+- Define `serve:prod` and `serve:prod:fresh` scripts for the chosen mode.
+- Keep server bootstrap and adapter code in dedicated files/modules.
+- Keep deployment notes aligned with runtime mode in project memory.
+
+## Example fix
+
+- Problem: Team mixes Expo serve and custom Express commands, causing inconsistent behavior.
+- Fix: Select one primary mode per environment, standardize scripts, and document routing/env boundaries.
+
+## Agent behavior
+
+- Use the project’s declared serving mode unless a migration is explicitly requested.
+- Delegate framework runtime primitives to official Expo docs, then enforce MDS conventions for script consistency, environment boundaries, and operational clarity.

package/dist/content/skills/project-onboarding.md

@@ -1,31 +1,31 @@
-# Skill: Project Onboarding
-
-Use when onboarding an existing Expo app into the MDS workflow after project creation.
-
-## Main rule
-
-Establish project memory and workflow defaults first, then scaffold only the selected technical additions.
-
-## Checks
-
-- Confirm onboarding target is the existing app folder (not a parent directory).
-- Confirm project memory files exist or are generated: `project/info.md`, `project/todo.md`, `project/style.md`, `project/guidelines.md`.
-- Confirm unresolved context markers are cleared before deep implementation work.
-- Confirm selected defaults (styling, state, data, CI, route placement) are documented in project memory.
-- Run Doctor after onboarding changes to validate baseline health.
-
-## Preferred structure
-
-- Use conversational intake to capture audience, flows, data needs, platform targets, and deployment intent.
-- Keep visual guidance in `project/style.md`; keep technical/agent rules in `project/guidelines.md`.
-- Keep onboarding outputs phase-based so follow-up work can continue from `project/todo.md`.
-
-## Example fix
-
-- Problem: Team starts coding before onboarding, causing missing docs and conflicting architecture assumptions.
-- Fix: Run onboarding flow, generate canonical project memory, reconcile open context markers, then resume implementation using phase order.
-
-## Agent behavior
-
-- Ask one focused onboarding question at a time when required by the flow.
-- Delegate framework primitive setup guidance to official Expo resources, then layer MDS project-memory and workflow automation rules.
+# Skill: Project Onboarding
+
+Use when onboarding an existing Expo app into the MDS workflow after project creation.
+
+## Main rule
+
+Establish project memory and workflow defaults first, then scaffold only the selected technical additions.
+
+## Checks
+
+- Confirm onboarding target is the existing app folder (not a parent directory).
+- Confirm project memory files exist or are generated: `project/info.md`, `project/todo.md`, `project/style.md`, `project/guidelines.md`.
+- Confirm unresolved context markers are cleared before deep implementation work.
+- Confirm selected defaults (styling, state, data, CI, route placement) are documented in project memory.
+- Run Doctor after onboarding changes to validate baseline health.
+
+## Preferred structure
+
+- Use conversational intake to capture audience, flows, data needs, platform targets, and deployment intent.
+- Keep visual guidance in `project/style.md`; keep technical/agent rules in `project/guidelines.md`.
+- Keep onboarding outputs phase-based so follow-up work can continue from `project/todo.md`.
+
+## Example fix
+
+- Problem: Team starts coding before onboarding, causing missing docs and conflicting architecture assumptions.
+- Fix: Run onboarding flow, generate canonical project memory, reconcile open context markers, then resume implementation using phase order.
+
+## Agent behavior
+
+- Ask one focused onboarding question at a time when required by the flow.
+- Delegate framework primitive setup guidance to official Expo resources, then layer MDS project-memory and workflow automation rules.

package/dist/content/skills/research-plan-intake.md

@@ -1,32 +1,32 @@
-# Skill: Research Plan Intake
-
-Use when a user has partial product context (notes, research docs, or incomplete project memory) and needs it transformed into canonical MDS project memory.
-
-## Main rule
-
-Normalize fragmented input into decision-ready `project/info.md` and `project/style.md` structure without inventing missing product facts.
-
-## Checks
-
-- Parse provided artifacts and classify each required section as clear, ambiguous, or unknown.
-- Reuse clear sections directly; ask focused follow-up only for ambiguous or missing high-impact decisions.
-- Keep visual guidance in style memory and technical/process guidance in guidelines memory.
-- Confirm resulting project memory aligns with current roadmap phase and target platforms.
-- Record unresolved unknowns explicitly instead of guessing.
-
-## Preferred structure
-
-- Accept inputs from pasted markdown, notes, and prior project memory files.
-- Map extracted content into canonical sections with concise normalization.
-- Produce follow-up questions only where answers materially change implementation direction.
-
-## Example fix
-
-- Problem: User provides a long brainstorm doc with no clear MVP flow or audience.
-- Fix: Extract known context, mark missing decision points, ask targeted follow-up, then generate canonical project memory sections.
-
-## Agent behavior
-
-- Preserve user intent and wording where it is already clear.
-- Keep uncertainty visible and collaborative; do not fill strategic gaps with assumptions that can misdirect implementation.
-- Treat this as an MDS-only project-memory skill: use official framework guidance only after product intent is clear, then record the MDS workflow context agents need.
+# Skill: Research Plan Intake
+
+Use when a user has partial product context (notes, research docs, or incomplete project memory) and needs it transformed into canonical MDS project memory.
+
+## Main rule
+
+Normalize fragmented input into decision-ready `project/info.md` and `project/style.md` structure without inventing missing product facts.
+
+## Checks
+
+- Parse provided artifacts and classify each required section as clear, ambiguous, or unknown.
+- Reuse clear sections directly; ask focused follow-up only for ambiguous or missing high-impact decisions.
+- Keep visual guidance in style memory and technical/process guidance in guidelines memory.
+- Confirm resulting project memory aligns with current roadmap phase and target platforms.
+- Record unresolved unknowns explicitly instead of guessing.
+
+## Preferred structure
+
+- Accept inputs from pasted markdown, notes, and prior project memory files.
+- Map extracted content into canonical sections with concise normalization.
+- Produce follow-up questions only where answers materially change implementation direction.
+
+## Example fix
+
+- Problem: User provides a long brainstorm doc with no clear MVP flow or audience.
+- Fix: Extract known context, mark missing decision points, ask targeted follow-up, then generate canonical project memory sections.
+
+## Agent behavior
+
+- Preserve user intent and wording where it is already clear.
+- Keep uncertainty visible and collaborative; do not fill strategic gaps with assumptions that can misdirect implementation.
+- Treat this as an MDS-only project-memory skill: use official framework guidance only after product intent is clear, then record the MDS workflow context agents need.

package/dist/content/skills/seo-metadata.md

@@ -1,31 +1,31 @@
-# Skill: SEO Metadata
-
-Use when preparing Expo web routes for crawlability, sharing previews, and production indexing behavior.
-
-## Main rule
-
-Define metadata intentionally per route group and ensure canonical/indexing strategy is explicit before release.
-
-## Checks
-
-- Confirm title, description, and canonical strategy are defined for production web routes.
-- Confirm Open Graph and social preview metadata exist for key entry routes.
-- Confirm dynamic routes have deterministic metadata sources.
-- Confirm sitemap and robots strategy is documented for the chosen web output mode.
-- Confirm duplicate or conflicting titles/canonicals are resolved.
-
-## Preferred structure
-
-- Keep shared metadata defaults centralized and route-level overrides explicit.
-- Keep metadata source-of-truth close to route ownership boundaries.
-- Keep SEO rules documented in project memory so onboarding and Doctor checks align.
-
-## Example fix
-
-- Problem: Dynamic content routes ship with repeated title/description and no canonical mapping.
-- Fix: Add route-level metadata builder, include canonical generation logic, and update sitemap coverage.
-
-## Agent behavior
-
-- Prioritize production routes and highest-traffic entry points first.
-- Delegate framework metadata primitives to official Expo guidance, then enforce MDS standards for canonical/indexing completeness.
+# Skill: SEO Metadata
+
+Use when preparing Expo web routes for crawlability, sharing previews, and production indexing behavior.
+
+## Main rule
+
+Define metadata intentionally per route group and ensure canonical/indexing strategy is explicit before release.
+
+## Checks
+
+- Confirm title, description, and canonical strategy are defined for production web routes.
+- Confirm Open Graph and social preview metadata exist for key entry routes.
+- Confirm dynamic routes have deterministic metadata sources.
+- Confirm sitemap and robots strategy is documented for the chosen web output mode.
+- Confirm duplicate or conflicting titles/canonicals are resolved.
+
+## Preferred structure
+
+- Keep shared metadata defaults centralized and route-level overrides explicit.
+- Keep metadata source-of-truth close to route ownership boundaries.
+- Keep SEO rules documented in project memory so onboarding and Doctor checks align.
+
+## Example fix
+
+- Problem: Dynamic content routes ship with repeated title/description and no canonical mapping.
+- Fix: Add route-level metadata builder, include canonical generation logic, and update sitemap coverage.
+
+## Agent behavior
+
+- Prioritize production routes and highest-traffic entry points first.
+- Delegate framework metadata primitives to official Expo guidance, then enforce MDS standards for canonical/indexing completeness.

package/dist/content/skills/super-stack-startup.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.

package/dist/content/skills/uniwind-theming.md

@@ -1,32 +1,32 @@
-# Skill: Uniwind Theming
-
-Use when setting up or maintaining Tailwind v4 + Uniwind styling in Expo projects.
-
-## Main rule
-
-Prefer Uniwind with Tailwind v4 defaults, keep theme tokens centralized, and ensure bundler/style wiring is consistent across environments.
-
-## Checks
-
-- Confirm Tailwind v4 and Uniwind dependencies/config are aligned with project SDK.
-- Confirm `global.css` import order loads Tailwind before Uniwind layers.
-- Confirm Metro/bundler integration uses `withUniwindConfig` (or project-equivalent wiring).
-- Confirm design tokens are centralized and reused instead of ad-hoc values.
-- Confirm platform-specific style behavior is intentional and documented.
-
-## Preferred structure
-
-- Keep token definitions in one source module/file.
-- Keep style-system setup in project bootstrap/config files, not scattered across screens.
-- Keep shared class patterns in reusable UI components.
-
-## Example fix
-
-- Problem: Global styles load in the wrong order, causing token classes to fail on web.
-- Fix: Reorder style imports, verify Metro integration, and move duplicate token literals into shared theme config.
-
-## Agent behavior
-
-- Preserve existing design intent while fixing setup drift.
-- Delegate framework styling primitives to official Expo/Uniwind docs, then apply MDS conventions for token consistency and onboarding readiness.
-
+# Skill: Uniwind Theming
+
+Use when setting up or maintaining Tailwind v4 + Uniwind styling in Expo projects.
+
+## Main rule
+
+Prefer Uniwind with Tailwind v4 defaults, keep theme tokens centralized, and ensure bundler/style wiring is consistent across environments.
+
+## Checks
+
+- Confirm Tailwind v4 and Uniwind dependencies/config are aligned with project SDK.
+- Confirm `global.css` import order loads Tailwind before Uniwind layers.
+- Confirm Metro/bundler integration uses `withUniwindConfig` (or project-equivalent wiring).
+- Confirm design tokens are centralized and reused instead of ad-hoc values.
+- Confirm platform-specific style behavior is intentional and documented.
+
+## Preferred structure
+
+- Keep token definitions in one source module/file.
+- Keep style-system setup in project bootstrap/config files, not scattered across screens.
+- Keep shared class patterns in reusable UI components.
+
+## Example fix
+
+- Problem: Global styles load in the wrong order, causing token classes to fail on web.
+- Fix: Reorder style imports, verify Metro integration, and move duplicate token literals into shared theme config.
+
+## Agent behavior
+
+- Preserve existing design intent while fixing setup drift.
+- Delegate framework styling primitives to official Expo/Uniwind docs, then apply MDS conventions for token consistency and onboarding readiness.
+

package/package.json

@@ -1,8 +1,13 @@
 {
   "name": "@mr.dj2u/knowledge",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "Skills, patterns, guides, and rules for Expo development (MCP resources)",
   "type": "module",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/DavidJGrimsley/mrdj-dev-suite.git",
+    "directory": "packages/knowledge"
+  },
   "files": [
     "dist"
   ],