@mandujs/mcp 0.38.12 → 0.39.0-beta.1

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

@@ -1,81 +0,0 @@
----
-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 +0,0 @@
----
-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,139 +0,0 @@
----
-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를 로드합니다.
-
-## 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
-- 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 |
-
-## 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,
-  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 +0,0 @@
-{
-  "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 +0,0 @@
-# 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입니다.

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

@@ -1,72 +0,0 @@
-# Rule Template
-
-Use this template when creating new rules for mandu-hydration.
-
----
-
-```markdown
----
-title: Rule Title Here
-impact: CRITICAL | HIGH | MEDIUM | LOW
-impactDescription: 영향 설명
-tags: hydration, tag1, tag2
----
-
-## Rule Title Here
-
-**Impact: {LEVEL} ({impactDescription})**
-
-규칙의 목적과 중요성을 설명합니다.
-
-**Incorrect (문제점 설명):**
-
-\`\`\`tsx
-// 잘못된 예시
-import { useState } from "react";
-
-export default function Counter() {
-  const [count, setCount] = useState(0);  // ❌ "use client" 없음
-  return <button>{count}</button>;
-}
-\`\`\`
-
-**Correct (올바른 방법):**
-
-\`\`\`tsx
-// 올바른 예시
-"use client";
-
-import { useState } from "react";
-
-export default function Counter() {
-  const [count, setCount] = useState(0);  // ✅ 작동함
-  return <button onClick={() => setCount(c => c + 1)}>{count}</button>;
-}
-\`\`\`
-
-Reference: [관련 문서 링크](https://example.com)
-```
-
----
-
-## Naming Convention
-
-- 파일명: `{section}-{rule-name}.md`
-- 예시: `hydration-directive-use-client.md`, `hydration-island-setup.md`
-
-## Hydration Strategies Quick Reference
-
-| Strategy | JavaScript | Use Case |
-|----------|------------|----------|
-| `none` | 없음 | 순수 정적 페이지 |
-| `island` | 부분 | 정적 + 인터랙티브 혼합 (기본값) |
-| `full` | 전체 | SPA 스타일 페이지 |
-
-## Priority Quick Reference
-
-| Priority | Load Time | Use Case |
-|----------|-----------|----------|
-| `immediate` | 페이지 로드 | 중요한 인터랙션 |
-| `visible` | 뷰포트 진입 | 스크롤 아래 콘텐츠 (기본값) |
-| `idle` | 브라우저 유휴 | 비중요 기능 |
-| `interaction` | 사용자 액션 | 클릭해야 활성화 |

package/src/resources/skills/mandu-hydration/rules/hydration-data-event.md

@@ -1,109 +0,0 @@
----
-title: Use useIslandEvent for Island Communication
-impact: MEDIUM
-impactDescription: Enables Island-to-Island data flow
-tags: hydration, event, communication
----
-
-## Use useIslandEvent for Island Communication
-
-Islands are isolated by default. Use `useIslandEvent` to communicate between them.
-
-**Incorrect (shared global state):**
-
-```tsx
-// ❌ Don't use global variables for Island communication
-let globalCount = 0;
-
-// Island A
-export function CounterIsland() {
-  const [count, setCount] = useState(globalCount);
-  // This won't sync with other Islands
-}
-```
-
-**Correct (useIslandEvent):**
-
-```tsx
-// Island A: Counter (emits updates)
-"use client";
-
-import { useState } from "react";
-import { useIslandEvent } from "@mandujs/core/client";
-
-export function CounterIsland() {
-  const [count, setCount] = useState(0);
-  const { emit } = useIslandEvent<{ count: number }>("counter-update");
-
-  const increment = () => {
-    const newCount = count + 1;
-    setCount(newCount);
-    emit({ count: newCount });  // Notify other Islands
-  };
-
-  return <button onClick={increment}>Count: {count}</button>;
-}
-```
-
-```tsx
-// Island B: Display (receives updates)
-"use client";
-
-import { useState } from "react";
-import { useIslandEvent } from "@mandujs/core/client";
-
-export function DisplayIsland() {
-  const [lastCount, setLastCount] = useState(0);
-
-  useIslandEvent<{ count: number }>("counter-update", (data) => {
-    setLastCount(data.count);  // React to counter updates
-  });
-
-  return <p>Last count received: {lastCount}</p>;
-}
-```
-
-## API Reference
-
-```typescript
-// Emit events
-const { emit } = useIslandEvent<T>(eventName);
-emit(data);
-
-// Listen to events
-useIslandEvent<T>(eventName, (data) => {
-  // Handle received data
-});
-
-// Both emit and listen
-const { emit } = useIslandEvent<T>(eventName, (data) => {
-  // Handle received data
-});
-emit(otherData);
-```
-
-## Common Patterns
-
-### Cart Updates
-
-```tsx
-// Product Island
-emit({ action: "add", productId: 123 });
-
-// Cart Island
-useIslandEvent("cart-update", ({ action, productId }) => {
-  if (action === "add") addToCart(productId);
-});
-```
-
-### Form Validation
-
-```tsx
-// Form Field Island
-emit({ field: "email", valid: true, value: "user@example.com" });
-
-// Submit Button Island
-useIslandEvent("field-change", ({ field, valid }) => {
-  updateFieldStatus(field, valid);
-});
-```

package/src/resources/skills/mandu-hydration/rules/hydration-directive-use-client.md

@@ -1,55 +0,0 @@
----
-title: Add "use client" Directive for Client Components
-impact: CRITICAL
-impactDescription: Required for client-side interactivity
-tags: hydration, client, directive
----
-
-## Add "use client" Directive for Client Components
-
-Client components must have `"use client"` directive at the top of the file.
-
-**Incorrect (missing directive):**
-
-```tsx
-// app/counter/client.tsx
-
-import { useState } from "react";
-
-export default function Counter() {
-  const [count, setCount] = useState(0);  // ❌ Will error
-  return <button onClick={() => setCount(c => c + 1)}>{count}</button>;
-}
-```
-
-**Correct (with directive):**
-
-```tsx
-// app/counter/client.tsx
-
-"use client";
-
-import { useState } from "react";
-
-export default function Counter() {
-  const [count, setCount] = useState(0);  // ✅ Works
-  return <button onClick={() => setCount(c => c + 1)}>{count}</button>;
-}
-```
-
-## When to Use "use client"
-
-Use the directive when your component:
-- Uses React hooks (useState, useEffect, useRef, etc.)
-- Has event handlers (onClick, onChange, etc.)
-- Uses browser-only APIs (window, document, localStorage)
-- Needs client-side interactivity
-
-## File Naming Convention
-
-```
-app/
-├── counter/
-│   ├── page.tsx      # Server component (no directive needed)
-│   └── client.tsx    # Client component ("use client" required)
-```