メニュー
Use when changing websocket / Socket.IO behavior — events, payloads, or gateways. open-meet has two namespaces (/meeting and /chat); this skill keeps the shared socket contract and both ends in sync.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Playbook for adding or changing API behavior in apps/server (NestJS + Fastify). Use when implementing endpoints, services, repositories, DTOs, guards, or gateways. Enforces controller→service→repository layering, the shared response/error envelope, DTO validation, and the separate user/admin auth systems.
Playbook for UI work in apps/web and apps/admin (Next.js App Router + next-intl). Use when adding pages, components, hooks, forms, or data fetching. Enforces Server Components by default, TanStack Query, react-hook-form + Zod, the typed API clients, @open-meet/ui primitives, and locale-aware routing.
Use whenever adding or changing user-facing UI or API copy. open-meet ships 15 locales; this skill keeps every locale in lockstep and registers new namespaces so useTranslations doesn't throw at runtime.
Use for database/schema work in apps/server — adding models, fields, relations, indexes, or migrations. The Prisma schema is split into multiple files by domain; this skill keeps edits and migrations in the right place.
Orientation map for the open-meet monorepo. Use at the start of a task to find which app, module, and shared package own a feature (auth, meetings, meeting-scoped chat, persistent team chat, recording, RBAC, branding, uploads) before editing. Answers "where does this change go?".
Use before finishing a task to pick and run the narrowest relevant checks for what you changed, and to self-review the change checklist. Maps the changed area to the exact lint/typecheck/test commands.
| name | realtime-contracts |
| description | Use when changing websocket / Socket.IO behavior — events, payloads, or gateways. open-meet has two namespaces (/meeting and /chat); this skill keeps the shared socket contract and both ends in sync. |
Two Socket.IO namespaces, both fanned out via the Redis adapter (apps/server/src/websocket/redis-io.adapter.ts):
/meeting — meeting orchestration (join/leave, knock, reactions, raise hand, ephemeral meeting chat, presence, recording). Gateway: apps/server/src/modules/client/chat/chat.gateway.ts. Web consumer: apps/web/features/web/meeting/*./chat — persistent team messaging (messages, reactions, typing, read receipts, presence, polls, pins, conversation updates). Gateway: apps/server/src/modules/client/messaging/conversation.gateway.ts. Web consumer: apps/web/features/web/chat/*.packages/types/src/socket.ts (SocketNamespace / ClientEvent / ServerEvent and ChatNamespace / ChatClientEvent / ChatServerEvent). Edit there first — never inline event-name strings in a gateway or client.dto/messaging.ts / dto/meeting.ts) and the repositories.pnpm --filter @open-meet/types build && pnpm --filter @open-meet/server typecheck && pnpm --filter @open-meet/web typecheck
Add server test:e2e when socket contracts change.