@mandujs/mcp 0.12.2 → 0.13.0

package/src/resources/skills/mandu-guard/rules/guard-preset-mandu.md

@@ -1,81 +1,81 @@
----
-title: Use Mandu Preset for Full-Stack Projects
-impact: HIGH
-impactDescription: Recommended architecture preset
-tags: guard, preset, architecture
----
-
-## Use Mandu Preset for Full-Stack Projects
-
-The Mandu preset combines FSD (Feature-Sliced Design) for frontend with Clean Architecture for backend.
-
-## Preset Selection Guide
-
-| Preset | Use Case | Frontend | Backend |
-|--------|----------|----------|---------|
-| `mandu` | Full-stack projects | FSD | Clean |
-| `fsd` | Frontend-focused | FSD | - |
-| `clean` | Backend-focused | - | Clean |
-| `hexagonal` | Domain-heavy | - | Hexagonal |
-| `atomic` | Component libraries | Atomic | - |
-
-## Mandu Preset Structure
-
-```
-src/
-├── app/                    # App entry, routing
-├── pages/                  # Page components
-├── widgets/                # Complex UI blocks
-├── features/               # Feature modules
-│   ├── auth/
-│   ├── cart/
-│   └── search/
-├── entities/               # Business entities
-│   ├── user/
-│   ├── product/
-│   └── order/
-├── shared/                 # Shared utilities
-│   ├── ui/                 # UI components
-│   ├── lib/                # Utility functions
-│   ├── api/                # API client
-│   └── config/             # Configuration
-└── api/                    # Backend
-    ├── application/        # Use cases
-    ├── domain/             # Business logic
-    ├── infra/              # Database, external
-    └── core/               # Core utilities
-```
-
-## Configuration
-
-```typescript
-// mandu.config.ts
-
-export default {
-  guard: {
-    preset: "mandu",  // Use mandu preset
-    rules: {
-      "LAYER_VIOLATION": "error",
-      "SLOT_NAMING": "warn",
-    },
-    ignore: [
-      "**/test/**",
-      "**/*.test.ts",
-      "**/*.spec.ts",
-    ],
-  },
-};
-```
-
-## Switching Presets
-
-```bash
-# Use FSD only (frontend project)
-bunx mandu guard arch --preset fsd
-
-# Use Clean only (backend project)
-bunx mandu guard arch --preset clean
-
-# Use Mandu (full-stack, default)
-bunx mandu guard arch --preset mandu
-```
+---
+title: Use Mandu Preset for Full-Stack Projects
+impact: HIGH
+impactDescription: Recommended architecture preset
+tags: guard, preset, architecture
+---
+
+## Use Mandu Preset for Full-Stack Projects
+
+The Mandu preset combines FSD (Feature-Sliced Design) for frontend with Clean Architecture for backend.
+
+## Preset Selection Guide
+
+| Preset | Use Case | Frontend | Backend |
+|--------|----------|----------|---------|
+| `mandu` | Full-stack projects | FSD | Clean |
+| `fsd` | Frontend-focused | FSD | - |
+| `clean` | Backend-focused | - | Clean |
+| `hexagonal` | Domain-heavy | - | Hexagonal |
+| `atomic` | Component libraries | Atomic | - |
+
+## Mandu Preset Structure
+
+```
+src/
+├── app/                    # App entry, routing
+├── pages/                  # Page components
+├── widgets/                # Complex UI blocks
+├── features/               # Feature modules
+│   ├── auth/
+│   ├── cart/
+│   └── search/
+├── entities/               # Business entities
+│   ├── user/
+│   ├── product/
+│   └── order/
+├── shared/                 # Shared utilities
+│   ├── ui/                 # UI components
+│   ├── lib/                # Utility functions
+│   ├── api/                # API client
+│   └── config/             # Configuration
+└── api/                    # Backend
+    ├── application/        # Use cases
+    ├── domain/             # Business logic
+    ├── infra/              # Database, external
+    └── core/               # Core utilities
+```
+
+## Configuration
+
+```typescript
+// mandu.config.ts
+
+export default {
+  guard: {
+    preset: "mandu",  // Use mandu preset
+    rules: {
+      "LAYER_VIOLATION": "error",
+      "SLOT_NAMING": "warn",
+    },
+    ignore: [
+      "**/test/**",
+      "**/*.test.ts",
+      "**/*.spec.ts",
+    ],
+  },
+};
+```
+
+## Switching Presets
+
+```bash
+# Use FSD only (frontend project)
+bunx mandu guard arch --preset fsd
+
+# Use Clean only (backend project)
+bunx mandu guard arch --preset clean
+
+# Use Mandu (full-stack, default)
+bunx mandu guard arch --preset mandu
+```

package/src/resources/skills/mandu-guard/rules/guard-validate-import.md

@@ -1,80 +1,80 @@
----
-title: Validate Import Paths Against Architecture
-impact: HIGH
-impactDescription: Prevents architecture violations
-tags: guard, validate, import
----
-
-## Validate Import Paths Against Architecture
-
-Check that all imports respect layer boundaries before committing code.
-
-## Valid Import Examples
-
-```typescript
-// ✅ features/auth/login.ts → entities/user
-import { User, createUser } from "@/entities/user";
-
-// ✅ widgets/header/index.tsx → features/auth
-import { useAuth } from "@/features/auth";
-
-// ✅ pages/home/page.tsx → widgets/header
-import { Header } from "@/widgets/header";
-
-// ✅ Any layer → shared
-import { formatDate } from "@/shared/lib/date";
-```
-
-## Invalid Import Examples
-
-```typescript
-// ❌ entities/user → features/auth (upward)
-import { useAuth } from "@/features/auth";  // VIOLATION!
-
-// ❌ shared/lib → entities/user (upward)
-import { User } from "@/entities/user";  // VIOLATION!
-
-// ❌ features/auth → features/cart (same layer cross-import)
-import { CartItem } from "@/features/cart";  // VIOLATION!
-```
-
-## Checking Imports
-
-### CLI
-
-```bash
-# Check single import
-bunx mandu guard check-import \
-  --from "src/features/auth/index.ts" \
-  --import "@/entities/user"
-
-# Check all imports in a file
-bunx mandu guard check src/features/auth/index.ts
-```
-
-### MCP Tool
-
-```typescript
-// Check import validity
-mandu_check_import({
-  fromFile: "src/features/auth/index.ts",
-  importPath: "@/entities/user"
-})
-// Returns: { valid: true, layer: "features", targetLayer: "entities" }
-```
-
-## Fixing Violations
-
-| Pattern | Problem | Solution |
-|---------|---------|----------|
-| Upward import | Lower layer needs higher | Move shared logic down or use DI |
-| Cross-feature import | Feature A uses Feature B | Extract to shared or create entity |
-| Circular import | A → B → A | Restructure or use interfaces |
-
-## CI Integration
-
-```yaml
-# .github/workflows/guard.yml
-- name: Check Architecture
-  run: bunx mandu guard arch --ci
-```
+---
+title: Validate Import Paths Against Architecture
+impact: HIGH
+impactDescription: Prevents architecture violations
+tags: guard, validate, import
+---
+
+## Validate Import Paths Against Architecture
+
+Check that all imports respect layer boundaries before committing code.
+
+## Valid Import Examples
+
+```typescript
+// ✅ features/auth/login.ts → entities/user
+import { User, createUser } from "@/entities/user";
+
+// ✅ widgets/header/index.tsx → features/auth
+import { useAuth } from "@/features/auth";
+
+// ✅ pages/home/page.tsx → widgets/header
+import { Header } from "@/widgets/header";
+
+// ✅ Any layer → shared
+import { formatDate } from "@/shared/lib/date";
+```
+
+## Invalid Import Examples
+
+```typescript
+// ❌ entities/user → features/auth (upward)
+import { useAuth } from "@/features/auth";  // VIOLATION!
+
+// ❌ shared/lib → entities/user (upward)
+import { User } from "@/entities/user";  // VIOLATION!
+
+// ❌ features/auth → features/cart (same layer cross-import)
+import { CartItem } from "@/features/cart";  // VIOLATION!
+```
+
+## Checking Imports
+
+### CLI
+
+```bash
+# Check single import
+bunx mandu guard check-import \
+  --from "src/features/auth/index.ts" \
+  --import "@/entities/user"
+
+# Check all imports in a file
+bunx mandu guard check src/features/auth/index.ts
+```
+
+### MCP Tool
+
+```typescript
+// Check import validity
+mandu_check_import({
+  fromFile: "src/features/auth/index.ts",
+  importPath: "@/entities/user"
+})
+// Returns: { valid: true, layer: "features", targetLayer: "entities" }
+```
+
+## Fixing Violations
+
+| Pattern | Problem | Solution |
+|---------|---------|----------|
+| Upward import | Lower layer needs higher | Move shared logic down or use DI |
+| Cross-feature import | Feature A uses Feature B | Extract to shared or create entity |
+| Circular import | A → B → A | Restructure or use interfaces |
+
+## CI Integration
+
+```yaml
+# .github/workflows/guard.yml
+- name: Check Architecture
+  run: bunx mandu guard arch --ci
+```

package/src/resources/skills/mandu-hydration/SKILL.md

@@ -1,91 +1,91 @@
----
-name: mandu-hydration
-description: |
-  Island Hydration pattern for Mandu. Use when creating interactive components,
-  client-side state, or partial hydration. Triggers on tasks involving
-  "use client", client.tsx, useState, useEffect, Island, or hydration.
-license: MIT
-metadata:
-  author: mandu
-  version: "1.0.0"
----
-
-# Mandu Island Hydration
-
-Island Hydration은 페이지의 일부분만 클라이언트에서 인터랙티브하게 만드는 기술입니다.
-대부분의 페이지는 정적 HTML로 유지하고, 필요한 부분만 JavaScript를 로드합니다.
-
-## When to Apply
-
-Reference these guidelines when:
-- Creating interactive client components
-- Adding client-side state to pages
-- Implementing partial hydration
-- Setting up client-server data flow
-- Working with Island communication
-
-## Rule Categories by Priority
-
-| Priority | Category | Impact | Prefix |
-|----------|----------|--------|--------|
-| 1 | Client Directive | CRITICAL | `hydration-directive-` |
-| 2 | Island Structure | HIGH | `hydration-island-` |
-| 3 | Hydration Priority | MEDIUM | `hydration-priority-` |
-| 4 | Data Flow | MEDIUM | `hydration-data-` |
-
-## Quick Reference
-
-### 1. Client Directive (CRITICAL)
-
-- `hydration-directive-use-client` - Add "use client" directive for client components
-- `hydration-directive-file-naming` - Use .client.tsx for client component files
-
-### 2. Island Structure (HIGH)
-
-- `hydration-island-setup` - Use Mandu.island() with setup function
-- `hydration-island-render` - Separate state logic from render
-
-### 3. Hydration Priority (MEDIUM)
-
-- `hydration-priority-immediate` - Load on page load (critical interactions)
-- `hydration-priority-visible` - Load when visible (default)
-- `hydration-priority-idle` - Load when browser idle
-- `hydration-priority-interaction` - Load on user interaction
-
-### 4. Data Flow (MEDIUM)
-
-- `hydration-data-server` - Access server data with useServerData
-- `hydration-data-event` - Communicate between Islands with useIslandEvent
-
-## Hydration Strategies
-
-| Strategy | Description | Use Case |
-|----------|-------------|----------|
-| `none` | No JavaScript | Pure static pages |
-| `island` | Partial hydration (default) | Static + interactive mix |
-| `full` | Full hydration | SPA-style pages |
-
-## Client Hooks
-
-```typescript
-import {
-  useServerData,
-  useHydrated,
-  useIslandEvent,
-} from "@mandujs/core/client";
-
-// Access SSR data
-const data = useServerData<UserData>("user", defaultValue);
-
-// Check hydration status
-const isHydrated = useHydrated();
-```
-
-## How to Use
-
-Read individual rule files for detailed explanations:
-
-```
-rules/hydration-directive-use-client.md
-rules/hydration-island-setup.md
-```
+---
+name: mandu-hydration
+description: |
+  Island Hydration pattern for Mandu. Use when creating interactive components,
+  client-side state, or partial hydration. Triggers on tasks involving
+  "use client", client.tsx, useState, useEffect, Island, or hydration.
+license: MIT
+metadata:
+  author: mandu
+  version: "1.0.0"
+---
+
+# Mandu Island Hydration
+
+Island Hydration은 페이지의 일부분만 클라이언트에서 인터랙티브하게 만드는 기술입니다.
+대부분의 페이지는 정적 HTML로 유지하고, 필요한 부분만 JavaScript를 로드합니다.
+
+## When to Apply
+
+Reference these guidelines when:
+- Creating interactive client components
+- Adding client-side state to pages
+- Implementing partial hydration
+- Setting up client-server data flow
+- Working with Island communication
+
+## Rule Categories by Priority
+
+| Priority | Category | Impact | Prefix |
+|----------|----------|--------|--------|
+| 1 | Client Directive | CRITICAL | `hydration-directive-` |
+| 2 | Island Structure | HIGH | `hydration-island-` |
+| 3 | Hydration Priority | MEDIUM | `hydration-priority-` |
+| 4 | Data Flow | MEDIUM | `hydration-data-` |
+
+## Quick Reference
+
+### 1. Client Directive (CRITICAL)
+
+- `hydration-directive-use-client` - Add "use client" directive for client components
+- `hydration-directive-file-naming` - Use .client.tsx for client component files
+
+### 2. Island Structure (HIGH)
+
+- `hydration-island-setup` - Use Mandu.island() with setup function
+- `hydration-island-render` - Separate state logic from render
+
+### 3. Hydration Priority (MEDIUM)
+
+- `hydration-priority-immediate` - Load on page load (critical interactions)
+- `hydration-priority-visible` - Load when visible (default)
+- `hydration-priority-idle` - Load when browser idle
+- `hydration-priority-interaction` - Load on user interaction
+
+### 4. Data Flow (MEDIUM)
+
+- `hydration-data-server` - Access server data with useServerData
+- `hydration-data-event` - Communicate between Islands with useIslandEvent
+
+## Hydration Strategies
+
+| Strategy | Description | Use Case |
+|----------|-------------|----------|
+| `none` | No JavaScript | Pure static pages |
+| `island` | Partial hydration (default) | Static + interactive mix |
+| `full` | Full hydration | SPA-style pages |
+
+## Client Hooks
+
+```typescript
+import {
+  useServerData,
+  useHydrated,
+  useIslandEvent,
+} from "@mandujs/core/client";
+
+// Access SSR data
+const data = useServerData<UserData>("user", defaultValue);
+
+// Check hydration status
+const isHydrated = useHydrated();
+```
+
+## How to Use
+
+Read individual rule files for detailed explanations:
+
+```
+rules/hydration-directive-use-client.md
+rules/hydration-island-setup.md
+```

package/src/resources/skills/mandu-hydration/metadata.json

@@ -1,12 +1,12 @@
-{
-  "version": "1.0.0",
-  "organization": "Mandu Framework",
-  "date": "February 2026",
-  "abstract": "Island Hydration 패턴 가이드. 부분 hydration으로 페이지의 일부만 인터랙티브하게 만드는 기술입니다. \"use client\" 지시어, Mandu.island() API, hydration 우선순위, Island 간 통신을 다룹니다.",
-  "references": [
-    "https://jasonformat.com/islands-architecture/",
-    "https://docs.astro.build/en/concepts/islands/",
-    "https://fresh.deno.dev/docs/concepts/islands"
-  ],
-  "tags": ["hydration", "island", "client", "interactive", "mandu"]
-}
+{
+  "version": "1.0.0",
+  "organization": "Mandu Framework",
+  "date": "February 2026",
+  "abstract": "Island Hydration 패턴 가이드. 부분 hydration으로 페이지의 일부만 인터랙티브하게 만드는 기술입니다. \"use client\" 지시어, Mandu.island() API, hydration 우선순위, Island 간 통신을 다룹니다.",
+  "references": [
+    "https://jasonformat.com/islands-architecture/",
+    "https://docs.astro.build/en/concepts/islands/",
+    "https://fresh.deno.dev/docs/concepts/islands"
+  ],
+  "tags": ["hydration", "island", "client", "interactive", "mandu"]
+}

package/src/resources/skills/mandu-hydration/rules/_sections.md

@@ -1,31 +1,31 @@
-# Sections
-
-This file defines all sections, their ordering, impact levels, and descriptions.
-The section ID (in parentheses) is the filename prefix used to group rules.
-
----
-
-## 1. Client Directive (hydration-directive)
-
-**Impact:** CRITICAL
-**Description:** "use client" 지시어와 .client.tsx 파일 명명. 클라이언트 컴포넌트 식별에 필수입니다.
-
-## 2. Island Structure (hydration-island)
-
-**Impact:** HIGH
-**Description:** Mandu.island() API로 Island 컴포넌트 구조화. setup/render 분리 패턴을 다룹니다.
-
-## 3. Hydration Priority (hydration-priority)
-
-**Impact:** MEDIUM
-**Description:** immediate, visible, idle, interaction 우선순위. 초기 로드 성능 최적화에 중요합니다.
-
-## 4. Data Flow (hydration-data)
-
-**Impact:** MEDIUM
-**Description:** useServerData, useIslandEvent를 통한 데이터 흐름. 서버-클라이언트, Island 간 통신입니다.
-
-## 5. Error Handling (hydration-error)
-
-**Impact:** LOW
-**Description:** errorBoundary, loading 상태 처리. 사용자 경험 향상을 위한 폴백 UI입니다.
+# Sections
+
+This file defines all sections, their ordering, impact levels, and descriptions.
+The section ID (in parentheses) is the filename prefix used to group rules.
+
+---
+
+## 1. Client Directive (hydration-directive)
+
+**Impact:** CRITICAL
+**Description:** "use client" 지시어와 .client.tsx 파일 명명. 클라이언트 컴포넌트 식별에 필수입니다.
+
+## 2. Island Structure (hydration-island)
+
+**Impact:** HIGH
+**Description:** Mandu.island() API로 Island 컴포넌트 구조화. setup/render 분리 패턴을 다룹니다.
+
+## 3. Hydration Priority (hydration-priority)
+
+**Impact:** MEDIUM
+**Description:** immediate, visible, idle, interaction 우선순위. 초기 로드 성능 최적화에 중요합니다.
+
+## 4. Data Flow (hydration-data)
+
+**Impact:** MEDIUM
+**Description:** useServerData, useIslandEvent를 통한 데이터 흐름. 서버-클라이언트, Island 간 통신입니다.
+
+## 5. Error Handling (hydration-error)
+
+**Impact:** LOW
+**Description:** errorBoundary, loading 상태 처리. 사용자 경험 향상을 위한 폴백 UI입니다.