القائمة
Generate and review TypeORM database migrations in server/ — migration:generate vs migration:create, and the column-rename DROP+ADD pitfall. Read before generating or writing any db migration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
NestJS endpoint return-type and DTO rules — explicit DTO return types, @ApiOkResponse matching, wrapper DTOs, constructor patterns, and the post-edit `bun run gen-api` step. Read before editing any *.dto.ts or *.controller.ts in server/.
Query the local Postgres database — credentials via server/.env, psql one-liners, TypeORM table/column naming, dev vs test DB.
Verify changes against the locally running apps — curl the API, drive the admin/frontend GUIs with Playwright
استنادا إلى تصنيف SOC المهني
| name | migrations |
| description | Generate and review TypeORM database migrations in server/ — migration:generate vs migration:create, and the column-rename DROP+ADD pitfall. Read before generating or writing any db migration. |
cd server && bun migration:generate -- migrations/{name}
Never hand-write migrations from scratch — always start from a generated one.
The generator can get things wrong. Key pitfall:
DROP + ADD, deleting data. Edit to RENAME COLUMN instead.Always review the generated SQL and edit when needed before committing.
For migrations with only raw SQL (triggers, functions) and no entity changes, migration:generate fails with "no changes". Use migration:create:
cd server && bun migration:create -- migrations/{name}
Then write SQL in the empty file.