Menü
Production deployment patterns for Mandu applications
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Canonical Mandu agent workflow. Use first in Mandu projects before direct source edits so Codex, Claude Code, Gemini CLI, and other agents follow the same context -> plan -> apply -> verify -> repair loop.
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.
File-system based routing for Mandu. Use when creating pages, API routes, layouts, or dynamic routes. Triggers on tasks involving app/ folder, page.tsx, route.ts, layout.tsx, [id], [...slug], or URL patterns.
Architecture guard system for Mandu. Use when checking layer dependencies, enforcing architecture rules, or validating file locations. Triggers on tasks involving architecture, layers, dependencies, or guard commands.
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.
Performance optimization patterns for Mandu applications. Use when optimizing slot handlers, Island components, bundle size, or Bun runtime. Triggers on tasks involving async/await, Promise.all, lazy loading, caching, or performance.
| name | Mandu Deployment |
| description | Production deployment patterns for Mandu applications |
| metadata | {"version":"1.0.0","author":"mandu"} |
| globs | ["render.yaml","Dockerfile","docker-compose.yml",".github/workflows/*.yml","bunfig.toml"] |
Mandu 앱을 프로덕션 환경에 안전하고 효율적으로 배포하기 위한 가이드입니다.
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.jsonrender.yaml, Dockerfile, docker-compose.yml, fly.toml, vercel.json, or netlify.tomlVerification command:
mandu agent verify --changed --json --write
Common failures:
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
Use these examples only after mandu.agent.plan selects the deploy domain and
mandu.agent.apply has produced the intended action order.
# render.yaml
services:
- type: web
name: mandu-app
runtime: node
buildCommand: bun install && bun run build
startCommand: bun run start
envVars:
- key: NODE_ENV
value: production
- key: BUN_ENV
value: production
FROM oven/bun:1.0
WORKDIR /app
COPY package.json bun.lockb ./
RUN bun install --frozen-lockfile --production
COPY . .
RUN bun run build
EXPOSE 3000
CMD ["bun", "run", "start"]
bun run build 성공 확인| Category | Description | Rules |
|---|---|---|
| Build | 프로덕션 빌드 최적화 | 2 |
| Platform | 플랫폼별 배포 설정 | 3 |
| Container | Docker 컨테이너화 | 2 |
| CI/CD | 자동화 파이프라인 | 1 |
→ 세부 규칙은 rules/ 폴더 참조