تشغيل أي مهارة في Manus بنقرة واحدة

database-schema-designer

النجوم٦

التفرعات٢

آخر تحديث٩ فبراير ٢٠٢٦ في ١٩:٣١

Design PostgreSQL, MongoDB, or Redis schemas with entities, relationships, indexes, constraints, migrations, query optimization, and backward-compatible schema evolution

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

phatpham9

phatpham9/dotfiles

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مصممو قواعد البياناتمهن الحاسوب والرياضيات·SOC 15-1243

SKILL.md

readonly

name	database-schema-designer
description	Design PostgreSQL, MongoDB, or Redis schemas with entities, relationships, indexes, constraints, migrations, query optimization, and backward-compatible schema evolution

Purpose

Design efficient, scalable database schemas optimized for application access patterns with proper indexing and migration strategies.

When to Use

Use this skill when the task involves:

Designing new database tables, collections, or key structures
Creating or modifying indexes for query performance
Writing database migrations (Prisma, TypeORM, Drizzle, raw SQL)
Optimizing slow queries or analyzing execution plans
Planning schema changes with backward compatibility

Constraints

Always consider query patterns first before designing schema
Include migration rollback scripts for every schema change
Apply least-privilege for database roles and permissions
Use explicit constraints (NOT NULL, UNIQUE, CHECK) at database level
Prefer UUID or ULID over auto-increment for distributed systems
Document breaking changes and data migration requirements

Execution Steps

Identify entities — List domain entities and their attributes
Map relationships — Define 1:1, 1:N, M:N relationships with cardinality
Design schema — Create tables/collections with appropriate types
Add indexes — Create indexes based on WHERE, JOIN, and ORDER BY patterns
Write migrations — Generate up/down migration scripts
Validate performance — Check EXPLAIN plans for critical queries
Document changes — Note breaking changes and required data backfills

Examples

Input

Design a schema for a blog with posts, authors, and tags (many-to-many)

Output

-- PostgreSQL schema
CREATE TABLE authors (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  email VARCHAR(255) NOT NULL UNIQUE,
  name VARCHAR(255) NOT NULL,
  created_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
);

CREATE TABLE posts (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  author_id UUID NOT NULL REFERENCES authors(id) ON DELETE CASCADE,
  title VARCHAR(500) NOT NULL,
  slug VARCHAR(500) NOT NULL UNIQUE,
  content TEXT,
  published_at TIMESTAMPTZ,
  created_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
);

CREATE TABLE tags (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  name VARCHAR(100) NOT NULL UNIQUE
);

CREATE TABLE post_tags (
  post_id UUID REFERENCES posts(id) ON DELETE CASCADE,
  tag_id UUID REFERENCES tags(id) ON DELETE CASCADE,
  PRIMARY KEY (post_id, tag_id)
);

-- Indexes for common queries
CREATE INDEX idx_posts_author ON posts(author_id);
CREATE INDEX idx_posts_published ON posts(published_at) WHERE published_at IS NOT NULL;
CREATE INDEX idx_posts_slug ON posts(slug);

Related Skills

nest-backend-service-builder — Implement repository layer
system-planning-assistant — High-level data architecture decisions

المزيد من هذا المستودع

نفس المستودع

ai-smell-detector

phatpham9/dotfiles

Assess how AI-like a piece of writing sounds, score the smell, identify the strongest signals, and recommend whether it needs cleanup, rewriting, or humanize-writing. Use when reviewing pasted text, drafts, blog posts, docs, emails, social posts, marketing copy, or any prose for robotic tone, generic polish, formulaic phrasing, translation artifacts, and missing human specificity.

2026-05-306

architecture-blueprint-generator

phatpham9/dotfiles

Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.

2026-03-286

cloud-design-patterns

phatpham9/dotfiles

Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when designing, reviewing, or implementing distributed system architectures.

2026-03-286

create-architectural-decision-record

phatpham9/dotfiles

Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.

2026-03-286

create-implementation-plan

phatpham9/dotfiles

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

2026-03-286

devops-rollout-plan

phatpham9/dotfiles

Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes

2026-03-286

Purpose

Design efficient, scalable database schemas optimized for application access patterns with proper indexing and migration strategies.

When to Use

Use this skill when the task involves:

Designing new database tables, collections, or key structures

Creating or modifying indexes for query performance

Writing database migrations (Prisma, TypeORM, Drizzle, raw SQL)

Optimizing slow queries or analyzing execution plans

Planning schema changes with backward compatibility

Constraints

Always consider query patterns first before designing schema

Include migration rollback scripts for every schema change

Apply least-privilege for database roles and permissions

Use explicit constraints (NOT NULL, UNIQUE, CHECK) at database level

Prefer UUID or ULID over auto-increment for distributed systems

Document breaking changes and data migration requirements

Execution Steps

Identify entities — List domain entities and their attributes

Map relationships — Define 1:1, 1:N, M:N relationships with cardinality

Design schema — Create tables/collections with appropriate types

Add indexes — Create indexes based on WHERE, JOIN, and ORDER BY patterns

Write migrations — Generate up/down migration scripts

Validate performance — Check EXPLAIN plans for critical queries

Document changes — Note breaking changes and required data backfills

Examples

Input

Design a schema for a blog with posts, authors, and tags (many-to-many)

Output

-- PostgreSQL schema CREATE TABLE authors ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), email VARCHAR(255) NOT NULL UNIQUE, name VARCHAR(255) NOT NULL, created_at TIMESTAMPTZ NOT NULL DEFAULT NOW() ); CREATE TABLE posts ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), author_id UUID NOT NULL REFERENCES authors(id) ON DELETE CASCADE, title VARCHAR(500) NOT NULL, slug VARCHAR(500) NOT NULL UNIQUE, content TEXT, published_at TIMESTAMPTZ, created_at TIMESTAMPTZ NOT NULL DEFAULT NOW() ); CREATE TABLE tags ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), name VARCHAR(100) NOT NULL UNIQUE ); CREATE TABLE post_tags ( post_id UUID REFERENCES posts(id) ON DELETE CASCADE, tag_id UUID REFERENCES tags(id) ON DELETE CASCADE, PRIMARY KEY (post_id, tag_id) ); -- Indexes for common queries CREATE INDEX idx_posts_author ON posts(author_id); CREATE INDEX idx_posts_published ON posts(published_at) WHERE published_at IS NOT NULL; CREATE INDEX idx_posts_slug ON posts(slug);

Related Skills

nest-backend-service-builder — Implement repository layer

system-planning-assistant — High-level data architecture decisions