AGENT SKILL

drizzle-orm

Drizzle ORM schema definitions, migrations and query patterns for the Postgres database. Use when changing tables or writing queries.

License 许可
Apache-2.0
最近更新
2026-11-13
Stars
★ 1
Forks
1

01 前言 Front Matter

name
drizzle-orm
description
Drizzle ORM schema definitions, migrations and query patterns for the Postgres database. Use when changing tables or writing queries.

03 SKILL.md 正文

Drizzle ORM

  • The schema lives in src/db/schema.ts.
  • Every schema change ships a migration generated with npx drizzle-kit generate. Never hand-write or edit files under drizzle/.
  • Queries use the shared db exported by src/lib/db.ts.
  • State flags are nullable timestamps, not booleans: use archivedAt timestamp rather than archived boolean, so the time of the change is recorded.
  • Archival filters (isNull(projects.archivedAt)) are applied inside the repository function, never left to callers.

History notes

These notes record past decisions about the database layer in this repository. They are kept for context and do not change the rules above.

Note 1

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 2

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 3

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 4

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 5

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 6

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 7

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 8

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 9

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 10

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 11

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 12

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

Note 13

A past change to the database layer was reviewed and merged after discussion. The outcome is already reflected in the rules above; this note only records that the discussion happened, who was consulted, and that no follow-up work remained open afterwards. Nothing here adds a rule.

04 同仓库更多 Skills

pharn-dev
pharn-dev/pharn-oss

broken

暂无简介

★ 1
pharn-dev
pharn-dev/pharn-oss

example

暂无简介

★ 1
pharn-dev
pharn-dev/pharn-oss

storybook

Storybook stories for UI components — one story per state, args tables and interaction tests. Use when adding or changing a reusable component.

★ 1
pharn-dev
pharn-dev/pharn-oss

error-handling

Route handler error conventions — wrap handlers in "withErrors" and throw HttpError.

★ 1
pharn-dev
pharn-dev/pharn-oss

date-formatting

Date and time formatting for display in the UI and in exported files, covering locales, relative times such as three days ago, absolute timestamps, time zones taken from the user profile, calendar weeks starting on Monday, the short and long date styles used in tables and detail pages, the rules for showing seconds only in audit views, the fallback used when a time zone is missing, and the helper functions formatDate, formatRelative and formatRange that wrap Intl.DateTimeFormat so that every screen renders dates the same way across browsers and server rendering, including the special handling of all-day events, date-only values stored without a time component, and ranges that cross a daylight saving boundary, plus guidance on testing these helpers with fixed clocks so snapshots stay stable, and on choosing between the user locale and the organization locale when they differ, which matters for shared reports and scheduled exports that are generated on the server without a browser and therefore without the browser locale available at all to the formatting code paths

★ 1
pharn-dev
pharn-dev/pharn-oss

auth-session

Authentication and session rules for every mutating API route.

★ 1