メニュー
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.
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 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.
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 | prisma-schema |
| description | 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. |
The schema is split by domain under apps/server/prisma/schema/ (user.prisma, meeting.prisma, chat.prisma, messaging.prisma, admin.prisma, rbac.prisma, recording.prisma, schema.prisma), configured via apps/server/prisma.config.ts. Migrations live inside apps/server/prisma/schema/migrations.
schema.prisma.backend-feature skill) — never query Prisma from a controller.pnpm --filter @open-meet/server prisma:generate
pnpm --filter @open-meet/server prisma:migrate
pnpm db:reset / pnpm db:wipe drop every table.packages/types/src/dto/* and the mapping in the service.pnpm --filter @open-meet/server prisma:generate && pnpm --filter @open-meet/server typecheck && pnpm --filter @open-meet/server test