メニュー
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mandu-testing |
| description | Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks. |
| license | MIT |
| metadata | {"author":"mandu","version":"1.0.0"} |
Mandu 애플리케이션의 테스트 패턴 가이드. Bun test를 활용한 단위 테스트, slot 테스트, Island 컴포넌트 테스트, Playwright E2E 테스트를 다룹니다.
This skill is a Domain addendum. It must not replace mandu-agent-workflow.
Use it only after mandu.agent.plan selects testing or mandu.agent.verify asks for targeted test coverage.
Canonical workflow step: verify -> repair.
Preferred MCP tools:
| Step | Tools |
|---|---|
| plan | mandu.agent.plan |
| verify | mandu.agent.verify, mandu.run.tests, mandu.ate.generate, mandu.ate.run |
| repair | mandu.agent.repair, mandu.ate.heal |
Allowed file edits:
*.test.ts / *.test.tsx filestests/e2e/**/*.spec.tsVerification command:
mandu agent verify --changed --json --write
Common failures:
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Slot Testing | HIGH | test-slot- |
| 2 | Component Testing | HIGH | test-component- |
| 3 | E2E Testing | MEDIUM | test-e2e- |
| 4 | Mocking | MEDIUM | test-mock- |
test-slot-unit - Unit test slot handlerstest-slot-guard - Test guard authenticationtest-slot-integration - Integration test with databasetest-component-island - Test Island componentstest-component-render - Test rendering outputtest-component-interaction - Test user interactionstest-e2e-playwright - Playwright setup and patternstest-e2e-auth - Test authentication flowstest-e2e-navigation - Test page navigationtest-mock-fetch - Mock fetch requeststest-mock-database - Mock database operationsUse these only after agent plan or agent verify identifies the target:
mandu agent verify --changed --json --write
bun test src/slots/user.test.ts
bun test --coverage
spec/slots/
├── users.slot.ts
├── users.slot.test.ts # Slot tests
app/
├── dashboard/
│ ├── client.tsx
│ └── client.test.tsx # Component tests
tests/
└── e2e/
└── auth.spec.ts # E2E tests
Read individual rule files for detailed explanations:
rules/test-slot-unit.md
rules/test-component-island.md
rules/test-e2e-playwright.md
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.
Production deployment patterns for Mandu applications
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.