@mr.dj2u/knowledge 0.1.0

package/dist/content/patterns/styling/uniwind-setup.md

@@ -0,0 +1,412 @@
+# Uniwind & Tailwind v4 Setup
+
+## Description
+
+Uniwind provides Tailwind v4 CSS integration for React Native with build-time style computation and Metro bundler configuration. Design tokens (colors, spacing, typography) live in CSS using `@layer theme` with `@variant` for light/dark modes, enabling cross-platform responsive styling without separate theme providers.
+
+## When to Use
+
+**Use Uniwind** for:
+- ✅ React Native projects (iOS, Android, Web)
+- ✅ Responsive design with breakpoints
+- ✅ Dark mode support with CSS variables
+- ✅ Tailwind utility-first styling approach
+- ✅ Projects using Tailwind v4+
+
+## Installation
+
+### 1. Install Dependencies
+
+```bash
+npm install uniwind
+npm install --save-dev tailwindcss@^4 @tailwindcss/postcss
+```
+
+### 2. Configure Metro Bundler
+
+```javascript
+// File: metro.config.js
+const { getDefaultConfig } = require('@react-native/metro-config');
+const { withUniwindConfig } = require('uniwind/metro');
+
+const config = getDefaultConfig(__dirname);
+
+module.exports = withUniwindConfig(config, {
+  cssEntryFile: './src/global.css',
+  // Optional: set rem polyfill if needed (default 16px)
+  // polyfills: { rem: 16 }
+});
+```
+
+### 3. Add PostCSS Configuration
+
+```javascript
+// File: postcss.config.js
+module.exports = {
+  plugins: {
+    'postcss-import': {},
+    'tailwindcss/nesting': {},
+    tailwindcss: {},
+    autoprefixer: {},
+  },
+};
+```
+
+## Code Example
+
+### Global CSS with Theme Tokens
+
+```css
+/* File: src/global.css */
+@import 'tailwindcss';
+@import 'uniwind';
+
+/* Define theme tokens as CSS variables */
+@layer theme {
+  :root {
+    /* Light mode (default) */
+    @variant light {
+      /* Primary colors */
+      --color-primary: #ef5350;
+      --color-primary-50: #ffebee;
+      --color-primary-100: #ffcdd2;
+      --color-primary-500: #ef5350;
+      --color-primary-700: #c62828;
+      --color-primary-900: #b71c1c;
+
+      /* Secondary colors */
+      --color-secondary: #29b6f6;
+      --color-secondary-500: #29b6f6;
+      --color-secondary-700: #0277bd;
+
+      /* Neutral colors */
+      --color-background: #fafafa;
+      --color-surface: #ffffff;
+      --color-typography: #212121;
+      --color-border: #e0e0e0;
+      --color-divider: #bdbdbd;
+
+      /* Status colors */
+      --color-success: #4caf50;
+      --color-warning: #ff9800;
+      --color-error: #f44336;
+      --color-info: #2196f3;
+    }
+
+    /* Dark mode */
+    @variant dark {
+      --color-primary: #ef5350;
+      --color-primary-50: #ffebee;
+      --color-primary-100: #ffcdd2;
+      --color-primary-500: #ef5350;
+      --color-primary-700: #d32f2f;
+      --color-primary-900: #b71c1c;
+
+      --color-secondary: #29b6f6;
+      --color-secondary-500: #29b6f6;
+      --color-secondary-700: #0288d1;
+
+      --color-background: #121212;
+      --color-surface: #1e1e1e;
+      --color-typography: #ffffff;
+      --color-border: #424242;
+      --color-divider: #616161;
+
+      --color-success: #66bb6a;
+      --color-warning: #ffb74d;
+      --color-error: #ef5350;
+      --color-info: #64b5f6;
+    }
+
+    /* Spacing scale */
+    --spacing-0: 0;
+    --spacing-1: 4px;
+    --spacing-2: 8px;
+    --spacing-3: 12px;
+    --spacing-4: 16px;
+    --spacing-6: 24px;
+    --spacing-8: 32px;
+
+    /* Typography */
+    --font-sans: 'Roboto', sans-serif;
+    --font-mono: 'RobotoMono', monospace;
+    --font-display: 'Modak', serif;
+  }
+}
+
+/* Define typography utilities */
+@layer utilities {
+  .typography-header {
+    @apply text-4xl font-bold tracking-tight;
+    font-family: var(--font-display);
+  }
+
+  .typography-subheader {
+    @apply text-2xl font-bold;
+    font-family: var(--font-sans);
+  }
+
+  .typography-body {
+    @apply text-base leading-6;
+    font-family: var(--font-sans);
+  }
+
+  .typography-caption {
+    @apply text-sm text-gray-500;
+    font-family: var(--font-sans);
+  }
+}
+
+/* Global style reset */
+@layer base {
+  * {
+    @apply margin-0 padding-0;
+  }
+
+  body {
+    @apply bg-[var(--color-background)] text-[var(--color-typography)];
+  }
+}
+```
+
+**From:** expo-super-template/global.css, DJsPortfolio/global.css
+
+### Component Styling with Uniwind
+
+```typescript
+// File: src/components/Button.tsx
+import { Pressable, Text } from 'react-native';
+import { cn } from '@/utils/cn'; // tailwind-merge helper
+
+interface ButtonProps {
+  title: string;
+  onPress: () => void;
+  variant?: 'primary' | 'secondary' | 'ghost';
+  disabled?: boolean;
+  fullWidth?: boolean;
+}
+
+export function Button({
+  title,
+  onPress,
+  variant = 'primary',
+  disabled = false,
+  fullWidth = false,
+}: ButtonProps) {
+  const baseStyles = 'px-4 py-3 rounded-lg active:opacity-80 disabled:opacity-50';
+
+  const variantStyles = {
+    primary: 'bg-[var(--color-primary)] text-white',
+    secondary: 'bg-[var(--color-secondary)] text-white',
+    ghost: 'bg-transparent border border-[var(--color-border)]',
+  };
+
+  const containerStyles = cn(
+    baseStyles,
+    variantStyles[variant],
+    fullWidth && 'w-full'
+  );
+
+  return (
+    <Pressable
+      className={containerStyles}
+      onPress={onPress}
+      disabled={disabled}
+    >
+      <Text className="text-center font-semibold">
+        {title}
+      </Text>
+    </Pressable>
+  );
+}
+```
+
+### Dark Mode Support
+
+```typescript
+// File: src/hooks/useColorScheme.ts
+import { useColorScheme as useNativeColorScheme } from 'react-native';
+
+export function useColorScheme() {
+  const scheme = useNativeColorScheme();
+  return scheme || 'light';
+}
+
+// File: src/components/ThemedView.tsx
+import { View, ViewProps } from 'react-native';
+import { useColorScheme } from '@/hooks/useColorScheme';
+
+interface ThemedViewProps extends ViewProps {
+  lightBg?: string;
+  darkBg?: string;
+}
+
+export function ThemedView({
+  lightBg = 'bg-white',
+  darkBg = 'dark:bg-black',
+  className,
+  ...props
+}: ThemedViewProps) {
+  const colorScheme = useColorScheme();
+
+  return (
+    <View
+      className={`${lightBg} ${darkBg} ${className || ''}`}
+      {...props}
+    />
+  );
+}
+
+// Usage
+function Screen() {
+  return (
+    <ThemedView
+      lightBg="bg-white"
+      darkBg="dark:bg-gray-900"
+      className="flex-1"
+    >
+      {/* Content */}
+    </ThemedView>
+  );
+}
+```
+
+### Responsive Breakpoints
+
+```typescript
+// File: src/components/ResponsiveGrid.tsx
+import { View } from 'react-native';
+
+export function ResponsiveGrid({ children }) {
+  return (
+    <View className="flex-row flex-wrap gap-4 w-full">
+      {/* 
+        Mobile (default): 1 column
+        md (768px): 2 columns
+        lg (1024px): 3 columns
+      */}
+      <View className="w-full md:w-1/2 lg:w-1/3">
+        {children}
+      </View>
+    </View>
+  );
+}
+```
+
+## Configuration
+
+### Tailwind Config
+
+```javascript
+// File: tailwind.config.js
+/** @type {import('tailwindcss').Config} */
+module.exports = {
+  content: [
+    './src/**/*.{js,jsx,ts,tsx}',
+    './App.{js,jsx,ts,tsx}',
+  ],
+  theme: {
+    extend: {
+      fontFamily: {
+        sans: ['Roboto', 'system-ui', 'sans-serif'],
+        mono: ['RobotoMono', 'monospace'],
+        display: ['Modak', 'serif'],
+      },
+      spacing: {
+        safe: 'env(safe-area-inset-bottom)',
+      },
+    },
+  },
+  plugins: [],
+};
+```
+
+## Best Practices
+
+### ✅ DO
+
+1. **Define all tokens in CSS** using `@layer theme`
+   ```css
+   @layer theme {
+     :root {
+       --color-primary: #ef5350;
+       --color-surface: #ffffff;
+     }
+   }
+   ```
+
+2. **Use CSS variables** in components
+   ```tsx
+   <View className="bg-[var(--color-primary)]" />
+   ```
+
+3. **Support dark mode** with `@variant dark`
+   ```css
+   @variant dark {
+     --color-background: #121212;
+   }
+   ```
+
+4. **Use `cn()` with tailwind-merge** for conditional classes
+   ```tsx
+   className={cn('bg-red-500', isActive && 'bg-blue-500')}
+   ```
+
+5. **Keep Tailwind config minimal** — use CSS variables instead
+   ```javascript
+   // ✅ MINIMAL config
+   module.exports = {
+     content: ['./src/**/*.tsx'],
+     theme: { extend: { fontFamily: { ... } } }
+   };
+   ```
+
+### ❌ DON'T
+
+1. **Don't define colors in tailwind.config.js**
+   ```javascript
+   // ❌ BAD - hard to theme dynamically
+   colors: { primary: '#ef5350' }
+   
+   // ✅ GOOD - use CSS variables
+   // In global.css: --color-primary: #ef5350
+   ```
+
+2. **Don't forget `prepare: false`** in Metro config
+   ```javascript
+   // ❌ BAD - required for Uniwind + Metro
+   // No withUniwindConfig
+   
+   // ✅ GOOD
+   module.exports = withUniwindConfig(config, {
+     cssEntryFile: './src/global.css',
+   });
+   ```
+
+3. **Don't use `StyleSheet.create()`** for layout/spacing
+   ```typescript
+   // ❌ BAD - verbose and hard to maintain
+   const styles = StyleSheet.create({
+     container: { flex: 1, padding: 16, backgroundColor: '#fff' }
+   });
+   
+   // ✅ GOOD - use Tailwind classes
+   <View className="flex-1 p-4 bg-white" />
+   ```
+
+4. **Don't forget to import global.css** in app root
+   ```typescript
+   // File: src/app/_layout.tsx
+   import '@/global.css'; // ← Required for Uniwind to work
+   ```
+
+## Related Patterns
+
+- [Theme Configuration](./theme-configuration.md) — Advanced theming patterns
+- [Responsive Patterns](./responsive-patterns.md) — Mobile-first responsive design
+- [Component Styling](./component-styling.md) — Component-specific styling
+
+---
+
+*Pattern extracted from production repositories: expo-super-template, DJsPortfolio, not-hot-dog*
+*Files: expo-super-template/global.css, metro.config.js*

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

@@ -0,0 +1,27 @@
+# /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 `mds-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.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI flow:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath>` when blockers are unclear.
+
+## 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/create-expo-super-stack.md

@@ -0,0 +1,29 @@
+# /create-expo-super-stack
+
+Create a new Expo app with the MDS Super Stack flow, then hand off to phase-based continuation.
+
+## Arguments
+
+- `parentDir`: folder where the new app directory should be created.
+- `appName`: app folder name.
+
+## MCP-First Workflow
+
+1. Confirm the `mds-dev-suite` MCP server is available.
+2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory.
+3. Follow the prompt intake flow and keep one question per turn until generation completes.
+4. After generation, move into the new app folder and invoke `continue_project` (or prompt `continue_mds_project`) for the first implementation session.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI generation:
+   - `npx -y create-expo-super-stack <appName>`
+3. Then onboard/continue from inside the generated app:
+   - `mds continue <new-app-path>`
+
+## Verification And Output
+
+- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
+- Output: generated app path, onboarding status, and immediate next command.

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

@@ -0,0 +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 `mds-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 codex --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

@@ -0,0 +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.

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

@@ -0,0 +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 `mds-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 codex --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

@@ -0,0 +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 `mds-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 codex --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/review-expo-project.md

@@ -0,0 +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 `mds-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 codex --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

@@ -0,0 +1,30 @@
+# /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 `mds-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`).
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI alternatives:
+   - `mds doctor <projectPath>`
+   - `mds doctor <projectPath> --ci`
+   - `mds doctor <projectPath> --json`
+
+## 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/ship-test-loop.md

@@ -0,0 +1,24 @@
+# /ship-test-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/reference/create-expo-stack-uniwind.md

@@ -0,0 +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.