agentleFS
lgzarturolgzarturo/codeconductor/.agents/skills/drizzle-schema-architect/SKILL.md

drizzle-schema-architect

Skill0 starsChanged 27 days agoMITView on GitHub

Generates strictly typed Drizzle ORM schemas for PostgreSQL with indexes, foreign keys, and Zod schema deduction.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Strict Typing: All table columns must be explicitly typed.

    line 23
  2. Very specific:

    PostgreSQL Focus: Use pg-specific column types (e.g.

    line 24
  3. Very specific:

    Zod Validation Integration: Always output Zod schemas inferred from Drizzle schemas using drizzle-zod's createInsertSchema and …

    line 25
  4. Very specific:

    Primary Keys: Prefer UUIDs generated by gen_random_uuid() or autoincrementing integers depending on the table volume.

    line 29
  5. Very specific:

    Dates: Always store timestamps using timestamp('created_at', { withTimezone: true, mode: 'date' }).defaultNow().notNull().

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Drizzle Schema Architect

Core Principles

  1. Strict Typing: All table columns must be explicitly typed. Do not rely on loose implicit types.
  2. PostgreSQL Focus: Use pg-specific column types (e.g. pgTable, uuid, timestamp, varchar, integer).
  3. Zod Validation Integration: Always output Zod schemas inferred from Drizzle schemas using drizzle-zod's createInsertSchema and createSelectSchema.

Schema Guidelines

  • Primary Keys: Prefer UUIDs generated by gen_random_uuid() or autoincrementing integers depending on the table volume.
  • Indices: Declare explicit indexes on foreign key columns and query filters.
  • Dates: Always store timestamps using timestamp('created_at', { withTimezone: true, mode: 'date' }).defaultNow().notNull().

Example Schema Pattern

import { pgTable, uuid, varchar, timestamp, index } from 'drizzle-orm/pg-core';
import { createInsertSchema, createSelectSchema } from 'drizzle-zod';

export const users = pgTable('users', {
  id: uuid('id').defaultRandom().primaryKey(),
  email: varchar('email', { length: 255 }).notNull().unique(),
  name: varchar('name', { length: 255 }),
  createdAt: timestamp('created_at', { withTimezone: true, mode: 'date' }).defaultNow().notNull(),
}, (table) => [
  index('email_idx').on(table.email)
]);

export const insertUserSchema = createInsertSchema(users);
export const selectUserSchema = createSelectSchema(users);

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.