メニュー
Generate a new Drizzle migration file from schema changes in `libs/db`. Use when the user changed `libs/db/src/schema.ts` and needs a migration generated, or asks to run the drizzle generate command.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scaffold the 7 layered files for a new backend module following the strict convention (types → validation → repository → service → controller → routes → openapi). Use when adding a new feature module under apps/nebula-chat-server/src/modules/.
Run pnpm lint:fix and pnpm format across the monorepo and surface any remaining issues. Use before commits, after large edits, or when the user says "lint" or "clean up formatting".
Load the project's conventions into context — reads AGENTS.md and the nearest CLAUDE.md. Use at the start of any non-trivial task, or when you suspect a convention-violation drift. Every build agent should invoke this early.
Load the backend migration index and a specific TICKET-M<n>.md into context. Use before any work on the Fastify / Drizzle / LangChain / libs-folder rearchitecture described in docs/new-backend/. Takes the ticket number as argument.
Regenerate the backend OpenAPI spec and the frontend Orval client. Use after any backend route/schema change, or when the user says "regen the client", "types are out of sync", or "update openapi.yaml".
Scaffold a new Zustand store file following project conventions (no useState, module-level init, @/ aliases, one-file-per-store). Use when creating a new store in apps/nebula-chat-client/src/**/stores/.
| name | drizzle-migrate |
| description | Generate a new Drizzle migration file from schema changes in `libs/db`. Use when the user changed `libs/db/src/schema.ts` and needs a migration generated, or asks to run the drizzle generate command. |
| allowed-tools | Bash, Read |
| argument-hint | <kebab-case-migration-name> |
Generate a new SQL migration file from the current libs/db/src/schema.ts diff.
$ARGUMENTS. If not, ask for one.docs/adr/ covering the schema change (if not, stop and invoke adr-author).libs/db/src/schema.ts to confirm the pending schema change.pnpm --filter @nebula-chat/db db:generate
libs/db/migrations/ and verify it matches intent (column types, FK actions, indexes, defaults).pnpm --filter @nebula-chat/db db:push in place of db:generate when migrations are needed for production — db:push skips the migration history entirely.