PostgreSQL conventions overview for Supabase projects. Use when: (1) Need overview of database design principles, (2) Understanding tight-fit design philosophy, (3) Quick reference for standard table structure
/plugin marketplace add ninyawee/armed-claude/plugin install supabase-skills@armed-claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Overview of database design principles for Supabase projects.
Environment: PostgreSQL 17 on Supabase.
MUST NOT add speculative columns:
| Don't Add Speculatively | Add When |
|---|---|
deleted_at | Soft delete confirmed |
created_by, updated_by | Audit trail required |
metadata jsonb | Flexible data needed |
| Indexes | Query patterns known |
CREATE TABLE tb_examples (
id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
created_at timestamptz NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated_at timestamptz NOT NULL DEFAULT CURRENT_TIMESTAMP
);
| Skill | Use For |
|---|---|
| supabase-migration | Creating migrations, naming conventions, security patterns |
| supabase-seeding | Populating test data, bulk loading |
| supabase-bootstrap | Setting up new projects, tooling config |
Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.
Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.