@mandujs/mcp 0.38.3 → 0.38.5

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

@@ -11,53 +11,53 @@ metadata:
   version: "1.0.0"
 ---
 
-# Mandu Composition
-
-Mandu 애플리케이션을 위한 React 컴포지션 패턴 가이드. Island 컴파운드 컴포넌트, 상태 관리 인터페이스, Provider 패턴, slot-client 분리를 다룹니다. Vercel의 Composition Patterns를 Mandu 컨텍스트로 변환하여 적용합니다.
-
-## Agent Workflow Contract
-
-This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
-Use it only after `mandu.agent.plan` selects composition, UI, hydration, slot, or component domains.
-
-Canonical workflow step: `plan -> apply -> verify`.
-
-Preferred MCP tools:
-
-| Step | Tools |
-|------|-------|
-| plan | `mandu.agent.plan`, `mandu.design.get`, `mandu.island.list` |
-| apply | `mandu.agent.apply` |
-| verify | `mandu.agent.verify`, `mandu.design.check`, `mandu.slot.validate` |
-| repair | `mandu.agent.repair` |
-
-Allowed file edits:
-
-- Island/client component files named in the plan
-- Provider/state modules scoped to the target feature
-- Slot-client boundaries only when the plan includes slot or hydration domains
-
-Verification command:
-
-```bash
-mandu agent verify --changed --json --write
-```
-
-Common failures:
-
-- Refactoring component APIs without checking island/client boundaries
-- Adding shared state providers broader than the planned feature
-- Mixing slot server logic into client composition files
-
-Repair path:
-
-```bash
-mandu agent repair --from .mandu/agent-verify.json --json
-```
-
-## When to Apply
-
-Reference these guidelines when:
+# Mandu Composition
+
+Mandu 애플리케이션을 위한 React 컴포지션 패턴 가이드. Island 컴파운드 컴포넌트, 상태 관리 인터페이스, Provider 패턴, slot-client 분리를 다룹니다. Vercel의 Composition Patterns를 Mandu 컨텍스트로 변환하여 적용합니다.
+
+## Agent Workflow Contract
+
+This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
+Use it only after `mandu.agent.plan` selects composition, UI, hydration, slot, or component domains.
+
+Canonical workflow step: `plan -> apply -> verify`.
+
+Preferred MCP tools:
+
+| Step | Tools |
+|------|-------|
+| plan | `mandu.agent.plan`, `mandu.design.get`, `mandu.island.list` |
+| apply | `mandu.agent.apply` |
+| verify | `mandu.agent.verify`, `mandu.design.check`, `mandu.slot.validate` |
+| repair | `mandu.agent.repair` |
+
+Allowed file edits:
+
+- Island/client component files named in the plan
+- Provider/state modules scoped to the target feature
+- Slot-client boundaries only when the plan includes slot or hydration domains
+
+Verification command:
+
+```bash
+mandu agent verify --changed --json --write
+```
+
+Common failures:
+
+- Refactoring component APIs without checking island/client boundaries
+- Adding shared state providers broader than the planned feature
+- Mixing slot server logic into client composition files
+
+Repair path:
+
+```bash
+mandu agent repair --from .mandu/agent-verify.json --json
+```
+
+## When to Apply
+
+Reference these guidelines when:
 - Designing Island component architecture
 - Managing shared state between Islands
 - Building reusable component APIs

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

@@ -12,63 +12,63 @@ globs:
   - "bunfig.toml"
 ---
 
-# Mandu Deployment Skill
-
-Mandu 앱을 프로덕션 환경에 안전하고 효율적으로 배포하기 위한 가이드입니다.
-
-## Agent Workflow Contract
-
-This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
-Use it only after `mandu.agent.plan` selects the deploy domain.
-
-Canonical workflow step: `plan -> apply -> verify`.
-
-Preferred MCP tools:
-
-| Step | Tools |
-|------|-------|
-| plan | `mandu.agent.plan`, `mandu.deploy.plan` |
-| apply | `mandu.agent.apply`, `mandu.deploy.compile` |
-| verify | `mandu.agent.verify`, `mandu.deploy.preview` |
-| repair | `mandu.agent.repair` |
-
-Allowed file edits:
-
-- `.mandu/deploy.intent.json`
-- Provider artifacts named in the plan, such as `render.yaml`, `Dockerfile`, `docker-compose.yml`, `fly.toml`, `vercel.json`, or `netlify.toml`
-- CI workflow files only when deploy automation is explicitly requested
-
-Verification command:
-
-```bash
-mandu agent verify --changed --json --write
-```
-
-Common failures:
-
-- Executing a provider deploy before a dry-run or preview step
-- Writing secrets into tracked config
-- Changing provider artifacts without route/deploy intent verification
-
-Repair path:
-
-```bash
-mandu agent repair --from .mandu/agent-verify.json --json
-```
-
-## 핵심 원칙
-
-1. **Bun 네이티브**: Bun 런타임과 번들러를 최대한 활용
+# Mandu Deployment Skill
+
+Mandu 앱을 프로덕션 환경에 안전하고 효율적으로 배포하기 위한 가이드입니다.
+
+## Agent Workflow Contract
+
+This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
+Use it only after `mandu.agent.plan` selects the deploy domain.
+
+Canonical workflow step: `plan -> apply -> verify`.
+
+Preferred MCP tools:
+
+| Step | Tools |
+|------|-------|
+| plan | `mandu.agent.plan`, `mandu.deploy.plan` |
+| apply | `mandu.agent.apply`, `mandu.deploy.compile` |
+| verify | `mandu.agent.verify`, `mandu.deploy.preview` |
+| repair | `mandu.agent.repair` |
+
+Allowed file edits:
+
+- `.mandu/deploy.intent.json`
+- Provider artifacts named in the plan, such as `render.yaml`, `Dockerfile`, `docker-compose.yml`, `fly.toml`, `vercel.json`, or `netlify.toml`
+- CI workflow files only when deploy automation is explicitly requested
+
+Verification command:
+
+```bash
+mandu agent verify --changed --json --write
+```
+
+Common failures:
+
+- Executing a provider deploy before a dry-run or preview step
+- Writing secrets into tracked config
+- Changing provider artifacts without route/deploy intent verification
+
+Repair path:
+
+```bash
+mandu agent repair --from .mandu/agent-verify.json --json
+```
+
+## 핵심 원칙
+
+1. **Bun 네이티브**: Bun 런타임과 번들러를 최대한 활용
 2. **환경 분리**: 개발/스테이징/프로덕션 환경 명확히 구분
 3. **자동화**: CI/CD를 통한 일관된 배포 프로세스
 4. **보안 우선**: 민감 정보는 환경 변수로 관리
 
-## Provider Artifact Examples
-
-Use these examples only after `mandu.agent.plan` selects the deploy domain and
-`mandu.agent.apply` has produced the intended action order.
-
-### Render 배포 (권장)
+## Provider Artifact Examples
+
+Use these examples only after `mandu.agent.plan` selects the deploy domain and
+`mandu.agent.apply` has produced the intended action order.
+
+### Render 배포 (권장)
 
 ```yaml
 # render.yaml

package/src/resources/skills/mandu-deployment/rules/db-provider-supabase.md

@@ -138,8 +138,8 @@ export function createServerSupabase() {
 Mandu 의 client island 에서 Realtime 구독:
 
 ```tsx
-// app/messages/MessagesIsland.client.tsx
-import { wrapComponent } from "@mandujs/core/client";
+// app/messages/MessagesIsland.client.tsx
+import { wrapComponent } from "@mandujs/core/client";
 import { useEffect, useState } from "react";
 import { supabase } from "@/lib/supabase";
 
@@ -174,7 +174,7 @@ function Messages() {
   );
 }
 
-export default wrapComponent(Messages);
+export default wrapComponent(Messages);
 ```
 
 ### 3.3 Storage

package/src/resources/skills/mandu-fs-routes/SKILL.md

@@ -10,53 +10,53 @@ metadata:
   version: "1.0.0"
 ---
 
-# Mandu FS Routes
-
-FS Routes는 파일 시스템 기반 라우팅입니다. `app/` 폴더의 파일 구조가 URL이 됩니다.
-
-## Agent Workflow Contract
-
-This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
-Use it only after `mandu.agent.plan` selects the route or API domain.
-
-Canonical workflow step: `plan -> apply -> verify`.
-
-Preferred MCP tools:
-
-| Step | Tools |
-|------|-------|
-| plan | `mandu.agent.plan`, `mandu.route.list` |
-| apply | `mandu.agent.apply`, `mandu.generate`, `mandu.route.add` |
-| verify | `mandu.agent.verify`, `mandu.manifest.validate` |
-| repair | `mandu.agent.repair` |
-
-Allowed file edits:
-
-- `app/**/page.tsx`, `app/**/layout.tsx`, `app/**/route.ts`
-- Route-local metadata files and co-located helpers
-- Related contract/slot files only when the plan includes those domains
-
-Verification command:
-
-```bash
-mandu agent verify --changed --json --write
-```
-
-Common failures:
-
-- Creating a page or API route before reading the local `app/` pattern
-- Editing generated route manifests by hand
-- Adding API files without contract verification when the plan includes API work
-
-Repair path:
-
-```bash
-mandu agent repair --from .mandu/agent-verify.json --json
-```
-
-## When to Apply
-
-Reference these guidelines when:
+# Mandu FS Routes
+
+FS Routes는 파일 시스템 기반 라우팅입니다. `app/` 폴더의 파일 구조가 URL이 됩니다.
+
+## Agent Workflow Contract
+
+This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
+Use it only after `mandu.agent.plan` selects the route or API domain.
+
+Canonical workflow step: `plan -> apply -> verify`.
+
+Preferred MCP tools:
+
+| Step | Tools |
+|------|-------|
+| plan | `mandu.agent.plan`, `mandu.route.list` |
+| apply | `mandu.agent.apply`, `mandu.generate`, `mandu.route.add` |
+| verify | `mandu.agent.verify`, `mandu.manifest.validate` |
+| repair | `mandu.agent.repair` |
+
+Allowed file edits:
+
+- `app/**/page.tsx`, `app/**/layout.tsx`, `app/**/route.ts`
+- Route-local metadata files and co-located helpers
+- Related contract/slot files only when the plan includes those domains
+
+Verification command:
+
+```bash
+mandu agent verify --changed --json --write
+```
+
+Common failures:
+
+- Creating a page or API route before reading the local `app/` pattern
+- Editing generated route manifests by hand
+- Adding API files without contract verification when the plan includes API work
+
+Repair path:
+
+```bash
+mandu agent repair --from .mandu/agent-verify.json --json
+```
+
+## When to Apply
+
+Reference these guidelines when:
 - Creating new pages or API endpoints
 - Setting up dynamic routes with parameters
 - Implementing shared layouts

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

@@ -10,53 +10,53 @@ metadata:
   version: "1.0.0"
 ---
 
-# Mandu Guard
-
-Mandu Guard는 아키텍처 규칙을 강제하는 시스템입니다.
-레이어 간 의존성을 검사하고 위반을 실시간으로 감지합니다.
-
-## Agent Workflow Contract
-
-This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
-Use it only after `mandu.agent.verify` reports guard diagnostics or `mandu.agent.plan` selects the guard domain.
-
-Canonical workflow step: `verify -> repair`.
-
-Preferred MCP tools:
-
-| Step | Tools |
-|------|-------|
-| plan | `mandu.agent.plan` |
-| verify | `mandu.agent.verify`, `mandu.guard.check`, `mandu.guard.explain` |
-| repair | `mandu.agent.repair`, `mandu.guard.heal` |
-
-Allowed file edits:
-
-- Source files that violate import/layer rules
-- `mandu.config.*` guard settings only when the plan explicitly changes policy
-- Generated files are not direct-edit targets
-
-Verification command:
-
-```bash
-mandu agent verify --changed --json --write
-```
-
-Common failures:
-
-- Running low-level guard commands before reading the agent verify report
-- Weakening guard config instead of fixing the import boundary
-- Directly editing generated files to silence diagnostics
-
-Repair path:
-
-```bash
-mandu agent repair --from .mandu/agent-verify.json --json
-```
-
-## When to Apply
-
-Reference these guidelines when:
+# Mandu Guard
+
+Mandu Guard는 아키텍처 규칙을 강제하는 시스템입니다.
+레이어 간 의존성을 검사하고 위반을 실시간으로 감지합니다.
+
+## Agent Workflow Contract
+
+This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
+Use it only after `mandu.agent.verify` reports guard diagnostics or `mandu.agent.plan` selects the guard domain.
+
+Canonical workflow step: `verify -> repair`.
+
+Preferred MCP tools:
+
+| Step | Tools |
+|------|-------|
+| plan | `mandu.agent.plan` |
+| verify | `mandu.agent.verify`, `mandu.guard.check`, `mandu.guard.explain` |
+| repair | `mandu.agent.repair`, `mandu.guard.heal` |
+
+Allowed file edits:
+
+- Source files that violate import/layer rules
+- `mandu.config.*` guard settings only when the plan explicitly changes policy
+- Generated files are not direct-edit targets
+
+Verification command:
+
+```bash
+mandu agent verify --changed --json --write
+```
+
+Common failures:
+
+- Running low-level guard commands before reading the agent verify report
+- Weakening guard config instead of fixing the import boundary
+- Directly editing generated files to silence diagnostics
+
+Repair path:
+
+```bash
+mandu agent repair --from .mandu/agent-verify.json --json
+```
+
+## When to Apply
+
+Reference these guidelines when:
 - Setting up architecture rules
 - Checking layer dependencies
 - Validating import paths
@@ -142,17 +142,17 @@ shared       # Shared
 | `SLOT_NAMING` | Slot file naming rule violation |
 | `FORBIDDEN_IMPORT` | Forbidden import (fs, child_process, etc.) |
 
-## Low-Level CLI Commands
-
-Use these only when `agent verify` or `agent repair` asks for guard-specific detail:
-
-```bash
-mandu agent verify --changed --json --write
-mandu guard arch --ci
-mandu guard arch --preset fsd
-```
-
-## How to Use
+## Low-Level CLI Commands
+
+Use these only when `agent verify` or `agent repair` asks for guard-specific detail:
+
+```bash
+mandu agent verify --changed --json --write
+mandu guard arch --ci
+mandu guard arch --preset fsd
+```
+
+## How to Use
 
 Read individual rule files for detailed explanations:
 

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

@@ -10,54 +10,54 @@ metadata:
   version: "1.0.0"
 ---
 
-# Mandu Island Hydration
-
-Island Hydration은 페이지의 일부분만 클라이언트에서 인터랙티브하게 만드는 기술입니다.
-대부분의 페이지는 정적 HTML로 유지하고, 필요한 부분만 JavaScript를 로드합니다.
-
-## Agent Workflow Contract
-
-This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
-Use it only after `mandu.agent.plan` selects the hydration, island, partial, or route domain.
-
-Canonical workflow step: `plan -> apply -> verify -> repair`.
-
-Preferred MCP tools:
-
-| Step | Tools |
-|------|-------|
-| plan | `mandu.agent.plan`, `mandu.island.list` |
-| apply | `mandu.agent.apply`, `mandu.hydration.set`, `mandu.hydration.addClientSlot` |
-| verify | `mandu.agent.verify`, `mandu.build`, `mandu.build.status` |
-| repair | `mandu.agent.repair` |
-
-Allowed file edits:
-
-- `app/**/*.partial.tsx`, `app/**/*.island.tsx`, route-local client components
-- Page hydration metadata only when the plan names the route
-- Shared client utilities only after inspecting existing client boundaries
-
-Verification command:
-
-```bash
-mandu agent verify --changed --json --write
-```
-
-Common failures:
-
-- Rendering page-level islands inline instead of using `partial().Render`
-- Forgetting route hydration metadata when a server page renders partials
-- Moving server-only imports into client bundles
-
-Repair path:
-
-```bash
-mandu agent repair --from .mandu/agent-verify.json --json
-```
-
-## When to Apply
-
-Reference these guidelines when:
+# Mandu Island Hydration
+
+Island Hydration은 페이지의 일부분만 클라이언트에서 인터랙티브하게 만드는 기술입니다.
+대부분의 페이지는 정적 HTML로 유지하고, 필요한 부분만 JavaScript를 로드합니다.
+
+## Agent Workflow Contract
+
+This skill is a Domain addendum. It must not replace `mandu-agent-workflow`.
+Use it only after `mandu.agent.plan` selects the hydration, island, partial, or route domain.
+
+Canonical workflow step: `plan -> apply -> verify -> repair`.
+
+Preferred MCP tools:
+
+| Step | Tools |
+|------|-------|
+| plan | `mandu.agent.plan`, `mandu.island.list` |
+| apply | `mandu.agent.apply`, `mandu.hydration.set`, `mandu.hydration.addClientSlot` |
+| verify | `mandu.agent.verify`, `mandu.build`, `mandu.build.status` |
+| repair | `mandu.agent.repair` |
+
+Allowed file edits:
+
+- `app/**/*.partial.tsx`, `app/**/*.island.tsx`, route-local client components
+- Page hydration metadata only when the plan names the route
+- Shared client utilities only after inspecting existing client boundaries
+
+Verification command:
+
+```bash
+mandu agent verify --changed --json --write
+```
+
+Common failures:
+
+- Rendering page-level islands inline instead of using `partial().Render`
+- Forgetting route hydration metadata when a server page renders partials
+- Moving server-only imports into client bundles
+
+Repair path:
+
+```bash
+mandu agent repair --from .mandu/agent-verify.json --json
+```
+
+## When to Apply
+
+Reference these guidelines when:
 - Creating interactive client components
 - Adding client-side state to pages
 - Implementing partial hydration
@@ -97,25 +97,25 @@ Reference these guidelines when:
 - `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 |
-
-## Runtime API Constraints
-
-- `island()` / `Mandu.island()` takes one definition object: `island({ setup, render })`.
-- Do not call `island("visible", Component)`; use `wrapComponent(Component)` for a simple page-level island wrapper.
-- Islands are page-level client bundles. Do not render them as inline JSX like `<MyIsland />`.
-- For an embedded interactive region inside a server page, use `partial()`: put it in `*.partial.tsx`, export `partial({ id, component })`, and render the returned `.Render` component from the server page.
-- A server page that renders partials must opt into hydration, for example `export const hydration = { strategy: "island", priority: "visible", preload: false }`.
-
-## Client Hooks
-
-```typescript
+## 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 |
+
+## Runtime API Constraints
+
+- `island()` / `Mandu.island()` takes one definition object: `island({ setup, render })`.
+- Do not call `island("visible", Component)`; use `wrapComponent(Component)` for a simple page-level island wrapper.
+- Islands are page-level client bundles. Do not render them as inline JSX like `<MyIsland />`.
+- For an embedded interactive region inside a server page, use `partial()`: put it in `*.partial.tsx`, export `partial({ id, component })`, and render the returned `.Render` component from the server page.
+- A server page that renders partials must opt into hydration, for example `export const hydration = { strategy: "island", priority: "visible", preload: false }`.
+
+## Client Hooks
+
+```typescript
 import {
   useServerData,
   useHydrated,