@mandujs/mcp 0.36.2 → 0.37.0

package/src/resources/skills/index.ts

@@ -1,12 +1,12 @@
-export { GUIDES, getGuide, listGuides, type GuideId } from "./guides.js";
-export { RECIPES, getRecipe, listRecipes, type RecipeId } from "./recipes.js";
-
-// Agent Skills pattern
-export {
-  listSkills,
-  getSkill,
-  listSkillRules,
-  getSkillRule,
-  type SkillMeta,
-  type RuleMeta,
-} from "./loader.js";
+export { GUIDES, getGuide, listGuides, type GuideId } from "./guides.js";
+export { RECIPES, getRecipe, listRecipes, type RecipeId } from "./recipes.js";
+
+// Agent Skills pattern
+export {
+  listSkills,
+  getSkill,
+  listSkillRules,
+  getSkillRule,
+  type SkillMeta,
+  type RuleMeta,
+} from "./loader.js";

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

@@ -1,91 +1,91 @@
----
-name: mandu-composition
-description: |
-  React composition patterns for Mandu applications. Use when designing
-  Island components, managing shared state, or building reusable component
-  APIs. Triggers on compound components, context providers, boolean props,
-  or component architecture tasks.
-license: MIT
-metadata:
-  author: mandu
-  version: "1.0.0"
----
-
-# Mandu Composition
-
-Mandu 애플리케이션을 위한 React 컴포지션 패턴 가이드. Island 컴파운드 컴포넌트, 상태 관리 인터페이스, Provider 패턴, slot-client 분리를 다룹니다. Vercel의 Composition Patterns를 Mandu 컨텍스트로 변환하여 적용합니다.
-
-## When to Apply
-
-Reference these guidelines when:
-- Designing Island component architecture
-- Managing shared state between Islands
-- Building reusable component APIs
-- Refactoring components with boolean prop proliferation
-- Working with compound components or context providers
-
-## Rule Categories by Priority
-
-| Priority | Category | Impact | Prefix |
-|----------|----------|--------|--------|
-| 1 | Component Architecture | HIGH | `comp-arch-` |
-| 2 | State Management | HIGH | `comp-state-` |
-| 3 | Island Patterns | MEDIUM | `comp-island-` |
-| 4 | Implementation Patterns | MEDIUM | `comp-pattern-` |
-
-## Quick Reference
-
-### 1. Component Architecture (HIGH)
-
-- `comp-arch-avoid-boolean-props` - Use composition instead of boolean customization
-- `comp-arch-compound-components` - Structure Islands as compound components
-- `comp-arch-explicit-variants` - Create explicit variant components
-
-### 2. State Management (HIGH)
-
-- `comp-state-context-interface` - Define generic state/actions/meta interface
-- `comp-state-lift-state` - Move state into provider for sibling access
-- `comp-state-decouple-impl` - Provider is the only place knowing implementation
-
-### 3. Island Patterns (MEDIUM)
-
-- `comp-island-compound` - Compose Islands with shared context
-- `comp-island-event` - Communicate between Islands with useIslandEvent
-- `comp-island-slot-split` - Separate server logic (slot) from client (Island)
-
-### 4. Implementation Patterns (MEDIUM)
-
-- `comp-pattern-children` - Use children for composition over render props
-- `comp-pattern-provider-boundary` - Understand provider boundary vs visual nesting
-
-## Core Principle
-
-**Lift state, compose internals, make state dependency-injectable.**
-
-```
-┌─────────────────────────────────────────┐
-│  Provider (state + actions + meta)      │
-│  ┌───────────────────────────────────┐  │
-│  │  Composer.Frame                   │  │
-│  │  ┌─────────┐ ┌─────────────────┐  │  │
-│  │  │ Input   │ │ Footer          │  │  │
-│  │  └─────────┘ │ ┌─────┐ ┌─────┐ │  │  │
-│  │              │ │Emoji│ │Send │ │  │  │
-│  │              │ └─────┘ └─────┘ │  │  │
-│  │              └─────────────────┘  │  │
-│  └───────────────────────────────────┘  │
-│  ┌───────────────┐  ← Outside Frame     │
-│  │ Preview       │     but inside       │
-│  └───────────────┘     Provider!        │
-└─────────────────────────────────────────┘
-```
-
-## How to Use
-
-Read individual rule files for detailed explanations:
-
-```
-rules/comp-arch-compound-components.md
-rules/comp-state-context-interface.md
-rules/comp-island-event.md
-```
+---
+name: mandu-composition
+description: |
+  React composition patterns for Mandu applications. Use when designing
+  Island components, managing shared state, or building reusable component
+  APIs. Triggers on compound components, context providers, boolean props,
+  or component architecture tasks.
+license: MIT
+metadata:
+  author: mandu
+  version: "1.0.0"
+---
+
+# Mandu Composition
+
+Mandu 애플리케이션을 위한 React 컴포지션 패턴 가이드. Island 컴파운드 컴포넌트, 상태 관리 인터페이스, Provider 패턴, slot-client 분리를 다룹니다. Vercel의 Composition Patterns를 Mandu 컨텍스트로 변환하여 적용합니다.
+
+## When to Apply
+
+Reference these guidelines when:
+- Designing Island component architecture
+- Managing shared state between Islands
+- Building reusable component APIs
+- Refactoring components with boolean prop proliferation
+- Working with compound components or context providers
+
+## Rule Categories by Priority
+
+| Priority | Category | Impact | Prefix |
+|----------|----------|--------|--------|
+| 1 | Component Architecture | HIGH | `comp-arch-` |
+| 2 | State Management | HIGH | `comp-state-` |
+| 3 | Island Patterns | MEDIUM | `comp-island-` |
+| 4 | Implementation Patterns | MEDIUM | `comp-pattern-` |
+
+## Quick Reference
+
+### 1. Component Architecture (HIGH)
+
+- `comp-arch-avoid-boolean-props` - Use composition instead of boolean customization
+- `comp-arch-compound-components` - Structure Islands as compound components
+- `comp-arch-explicit-variants` - Create explicit variant components
+
+### 2. State Management (HIGH)
+
+- `comp-state-context-interface` - Define generic state/actions/meta interface
+- `comp-state-lift-state` - Move state into provider for sibling access
+- `comp-state-decouple-impl` - Provider is the only place knowing implementation
+
+### 3. Island Patterns (MEDIUM)
+
+- `comp-island-compound` - Compose Islands with shared context
+- `comp-island-event` - Communicate between Islands with useIslandEvent
+- `comp-island-slot-split` - Separate server logic (slot) from client (Island)
+
+### 4. Implementation Patterns (MEDIUM)
+
+- `comp-pattern-children` - Use children for composition over render props
+- `comp-pattern-provider-boundary` - Understand provider boundary vs visual nesting
+
+## Core Principle
+
+**Lift state, compose internals, make state dependency-injectable.**
+
+```
+┌─────────────────────────────────────────┐
+│  Provider (state + actions + meta)      │
+│  ┌───────────────────────────────────┐  │
+│  │  Composer.Frame                   │  │
+│  │  ┌─────────┐ ┌─────────────────┐  │  │
+│  │  │ Input   │ │ Footer          │  │  │
+│  │  └─────────┘ │ ┌─────┐ ┌─────┐ │  │  │
+│  │              │ │Emoji│ │Send │ │  │  │
+│  │              │ └─────┘ └─────┘ │  │  │
+│  │              └─────────────────┘  │  │
+│  └───────────────────────────────────┘  │
+│  ┌───────────────┐  ← Outside Frame     │
+│  │ Preview       │     but inside       │
+│  └───────────────┘     Provider!        │
+└─────────────────────────────────────────┘
+```
+
+## How to Use
+
+Read individual rule files for detailed explanations:
+
+```
+rules/comp-arch-compound-components.md
+rules/comp-state-context-interface.md
+rules/comp-island-event.md
+```

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

@@ -1,13 +1,13 @@
-{
-  "version": "1.0.0",
-  "organization": "Mandu Framework",
-  "date": "February 2026",
-  "abstract": "Mandu 애플리케이션을 위한 React 컴포지션 패턴 가이드. Island 컴파운드 컴포넌트, state/actions/meta 인터페이스, Provider 패턴, useIslandEvent를 통한 Island 간 통신, slot-client 분리 패턴을 다룹니다. Vercel Composition Patterns 기반으로 Mandu 컨텍스트에 맞게 변환되었습니다.",
-  "references": [
-    "https://react.dev/learn/passing-data-deeply-with-context",
-    "https://react.dev/learn/scaling-up-with-reducer-and-context",
-    "https://www.patterns.dev/react/compound-pattern",
-    "https://kentcdodds.com/blog/compound-components-with-react-hooks"
-  ],
-  "tags": ["composition", "compound", "context", "state", "island", "mandu"]
-}
+{
+  "version": "1.0.0",
+  "organization": "Mandu Framework",
+  "date": "February 2026",
+  "abstract": "Mandu 애플리케이션을 위한 React 컴포지션 패턴 가이드. Island 컴파운드 컴포넌트, state/actions/meta 인터페이스, Provider 패턴, useIslandEvent를 통한 Island 간 통신, slot-client 분리 패턴을 다룹니다. Vercel Composition Patterns 기반으로 Mandu 컨텍스트에 맞게 변환되었습니다.",
+  "references": [
+    "https://react.dev/learn/passing-data-deeply-with-context",
+    "https://react.dev/learn/scaling-up-with-reducer-and-context",
+    "https://www.patterns.dev/react/compound-pattern",
+    "https://kentcdodds.com/blog/compound-components-with-react-hooks"
+  ],
+  "tags": ["composition", "compound", "context", "state", "island", "mandu"]
+}

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

@@ -1,26 +1,26 @@
-# 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. Component Architecture (comp-arch)
-
-**Impact:** HIGH
-**Description:** Boolean props 대신 컴포지션 사용, 컴파운드 컴포넌트 구조화. 코드베이스가 확장됨에 따라 유지보수성에 큰 영향을 미칩니다.
-
-## 2. State Management (comp-state)
-
-**Impact:** HIGH
-**Description:** state/actions/meta 인터페이스 정의, Provider를 통한 의존성 주입. 같은 UI를 다양한 상태 구현과 함께 재사용할 수 있게 합니다.
-
-## 3. Island Patterns (comp-island)
-
-**Impact:** MEDIUM
-**Description:** Mandu Island 특화 패턴. 컴파운드 Island, Island 간 이벤트 통신, slot-client 분리를 다룹니다.
-
-## 4. Implementation Patterns (comp-pattern)
-
-**Impact:** MEDIUM
-**Description:** children 활용, Provider 경계 이해 등 구현 세부 사항. 올바른 패턴 적용으로 유연성을 확보합니다.
+# 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. Component Architecture (comp-arch)
+
+**Impact:** HIGH
+**Description:** Boolean props 대신 컴포지션 사용, 컴파운드 컴포넌트 구조화. 코드베이스가 확장됨에 따라 유지보수성에 큰 영향을 미칩니다.
+
+## 2. State Management (comp-state)
+
+**Impact:** HIGH
+**Description:** state/actions/meta 인터페이스 정의, Provider를 통한 의존성 주입. 같은 UI를 다양한 상태 구현과 함께 재사용할 수 있게 합니다.
+
+## 3. Island Patterns (comp-island)
+
+**Impact:** MEDIUM
+**Description:** Mandu Island 특화 패턴. 컴파운드 Island, Island 간 이벤트 통신, slot-client 분리를 다룹니다.
+
+## 4. Implementation Patterns (comp-pattern)
+
+**Impact:** MEDIUM
+**Description:** children 활용, Provider 경계 이해 등 구현 세부 사항. 올바른 패턴 적용으로 유연성을 확보합니다.

package/src/resources/skills/mandu-composition/rules/_template.md

@@ -1,77 +1,77 @@
-# Rule Template
-
-Use this template when creating new rules for mandu-composition.
-
----
-
-```markdown
----
-title: Rule Title Here
-impact: HIGH | MEDIUM | LOW
-impactDescription: 영향 설명 (예: "enables flexible composition")
-tags: composition, tag1, tag2
----
-
-## Rule Title Here
-
-**Impact: {LEVEL} ({impactDescription})**
-
-규칙의 목적과 아키텍처적 영향을 설명합니다.
-
-**Incorrect (문제가 되는 패턴):**
-
-\`\`\`tsx
-// ❌ Boolean props로 기능 추가
-function Composer({
-  showAttachments,
-  showFormatting,
-  showEmojis,
-  isCompact,
-  isReadOnly,
-}: Props) {
-  return (
-    <form>
-      {!isReadOnly && <Input />}
-      {showAttachments && <Attachments />}
-      {showFormatting && <Formatting />}
-      {showEmojis && <Emojis />}
-    </form>
-  );
-}
-```
-
-**Correct (컴포지션 패턴):**
-
-\`\`\`tsx
-// ✅ 컴포지션으로 유연하게 구성
-<Composer.Provider state={state} actions={actions}>
-  <Composer.Frame>
-    <Composer.Input />
-    <Composer.Footer>
-      <Composer.Emojis />
-      <Composer.Submit />
-    </Composer.Footer>
-  </Composer.Frame>
-</Composer.Provider>
-\`\`\`
-
-## Mandu Context
-
-Mandu Island에서 이 패턴을 적용하는 방법을 설명합니다.
-
-Reference: [관련 문서 링크](https://example.com)
-```
-
----
-
-## Naming Convention
-
-- 파일명: `comp-{category}-{rule-name}.md`
-- 예시: `comp-arch-compound-components.md`, `comp-state-context-interface.md`
-
-## Core Principle
-
-**Lift state, compose internals, make state dependency-injectable.**
-
-UI는 조합 가능한 조각들이고, 상태는 Provider가 주입합니다.
-Provider를 바꾸면 UI는 그대로 유지됩니다.
+# Rule Template
+
+Use this template when creating new rules for mandu-composition.
+
+---
+
+```markdown
+---
+title: Rule Title Here
+impact: HIGH | MEDIUM | LOW
+impactDescription: 영향 설명 (예: "enables flexible composition")
+tags: composition, tag1, tag2
+---
+
+## Rule Title Here
+
+**Impact: {LEVEL} ({impactDescription})**
+
+규칙의 목적과 아키텍처적 영향을 설명합니다.
+
+**Incorrect (문제가 되는 패턴):**
+
+\`\`\`tsx
+// ❌ Boolean props로 기능 추가
+function Composer({
+  showAttachments,
+  showFormatting,
+  showEmojis,
+  isCompact,
+  isReadOnly,
+}: Props) {
+  return (
+    <form>
+      {!isReadOnly && <Input />}
+      {showAttachments && <Attachments />}
+      {showFormatting && <Formatting />}
+      {showEmojis && <Emojis />}
+    </form>
+  );
+}
+```
+
+**Correct (컴포지션 패턴):**
+
+\`\`\`tsx
+// ✅ 컴포지션으로 유연하게 구성
+<Composer.Provider state={state} actions={actions}>
+  <Composer.Frame>
+    <Composer.Input />
+    <Composer.Footer>
+      <Composer.Emojis />
+      <Composer.Submit />
+    </Composer.Footer>
+  </Composer.Frame>
+</Composer.Provider>
+\`\`\`
+
+## Mandu Context
+
+Mandu Island에서 이 패턴을 적용하는 방법을 설명합니다.
+
+Reference: [관련 문서 링크](https://example.com)
+```
+
+---
+
+## Naming Convention
+
+- 파일명: `comp-{category}-{rule-name}.md`
+- 예시: `comp-arch-compound-components.md`, `comp-state-context-interface.md`
+
+## Core Principle
+
+**Lift state, compose internals, make state dependency-injectable.**
+
+UI는 조합 가능한 조각들이고, 상태는 Provider가 주입합니다.
+Provider를 바꾸면 UI는 그대로 유지됩니다.