跳到技能内容
词映 AI导航
发现工具选型指南Skills 技能AI 快讯AI图片AI视频AI文档AI办公AI助手AI搜索AI编程AI音频AI设计AI智能体模型与开发AI学习模型评测AI提示词内容检测AI金融AI 3D扫描与识别其他工具跨境电商 AI
词映 AI导航
工具库Skills 技能
我的收藏
词映 AI导航
发现工具选型指南Skills 技能AI 快讯AI图片AI视频AI文档AI办公AI助手AI搜索AI编程AI音频AI设计AI智能体模型与开发AI学习模型评测AI提示词内容检测AI金融AI 3D扫描与识别其他工具跨境电商 AI
Skills directory/suraj-kashyap-dev/open-meet/prisma-schema

Codex Update an Open Meet Prisma Meeting Schema by Domain

Choose the domain file in Open Meet's split Prisma schema and verify migration, client generation, and DTO implications.

中文

Install in Codex

Use the Open Meet checkout, pnpm, and an isolated local test database.

  1. Copy the pinned `.codex/skills/prisma-schema/` directory into `.agents/skills/prisma-schema/` in the project.
  2. Open `apps/server/prisma.config.ts` and the relevant file under `apps/server/prisma/schema/` to confirm schema and migration paths.

Example task

Add nullable `agenda` to a local demo meeting record in `meeting.prisma`. Generate the client and check existing rows remain readable in the test database.

What to check

The meeting domain owns the change, the migration adds one nullable field, and client generation and type checks include it.

Original SKILL.md on GitHub · Updated 2026-11-13

Frequently asked question

Must every database field be exposed to clients?

Update DTOs and mappings when the interface contract calls for it. A field can remain internal.

Related skills from this repository

  • Codex Open-meet Cross-App Feature Specifications
  • Codex Open Meet Frontend Feature for Localized Next.js Forms
  • Codex i18n-copy for Matching open-meet Locale Keys
Browse Codex skills in the Chinese directory
词映 AI 导航Skills 技能
工具分类全部工具已本地化技能选型指南AI 快讯