Skill

data-integrity-patterns

Constraints, triggers, audit trails, referential integrity, and data validation.

npx claudepluginhub sethdford/claude-skills --plugin engineer-database-engineering

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/database-engineering:data-integrity-patterns

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Maintaining data correctness through database constraints and patterns.

SKILL.md

45 lines · ~388 tokens

Similar Skills

validating-database-integrity

2.2k

Audits PostgreSQL/MySQL data for integrity issues (NULLs, orphans, formats, ranges, duplicates) and generates/enforces CHECK constraints, foreign keys, triggers.

5 files7 tools

data-validation-engine

database-schema-design

149

Designs PostgreSQL/MySQL schemas with normalization (1NF-3NF), relationships, constraints, audit columns. For new databases, reviews, migrations, or fixing missing PKs/FKs, wrong types, denormalization, EAV.

10 files

database-schema-design

schema-validation

Database schema validation tools - SQL syntax checking, constraint validation, naming convention enforcement, and schema integrity verification. Use when validating database schemas, checking migrations, enforcing naming conventions, verifying constraints, or when user mentions schema validation, migration checks, database best practices, or PostgreSQL validation.

16 files5 tools

supabase

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Data Integrity Patterns

Maintaining data correctness through database constraints and patterns.

Context

You are ensuring data stays correct. Use database constraints, not just application validation.

Domain Context

Constraints: NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY, CHECK

Triggers: Automatic actions on data changes; use sparingly

Audit Trail: Record of what changed and when

Referential Integrity: Foreign keys prevent orphaned records

Validation: Business rules enforced at database level

Instructions

NOT NULL: Columns that must have values

UNIQUE: Columns/combinations that must be unique

FOREIGN KEYS: References to other tables; prevent orphans

CHECK: Business rules (price > 0, status IN (values))

Triggers: Rarely; keep business logic in application

Audit Trail: Timestamp, user columns; or trigger for history table

Enforcement: Database enforces; application can't bypass

Anti-Patterns

No constraints; trust application to validate (it won't)

Over-reliance on triggers; hard to test, understand

Audit table with triggers; complex and slow

CHECK constraints that are wrong; don't trust them until tested

Not testing constraint enforcement