22건 · 관련도순
Designs database schemas with proper normalization, indexing, constraints, and tenant isolation patterns. Use when someone needs to create a new database schema, add multi-tenant support, design row-level security policies, or optimize table structures. Trigger words: database schema, table design, RLS, row-level security, foreign keys, indexes, migrations, ERD, data model, normalization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill for graphql-schema-design tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design PostgreSQL tables by choosing data types, validation rules, and indexes that match actual queries. The skill also guides JSONB usage, partitioning large tables, and planning schema changes with attention to read and write workloads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design relational database tables from requirements and generate relationship diagrams, migration code, type definitions, and test data. Also covers indexes, audit history, and row-level access rules for applications serving multiple organizations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore an existing PostgreSQL database before answering questions about its data or writing SQL. Use this skill whenever a user asks for a query or a data-backed answer against an unfamiliar schema (counts, missing or failed records, recent changes), asks where a business concept lives, or asks how tables, joins, views, routines, triggers, RLS, or extensions work. Find the relevant objects with read-only pg_catalog queries, then request approval before inspecting data-derived statistics or rows. Not a schema-design or migration guide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design relational schemas from requirements with normalization, migrations, ERDs, RLS policies, and indexes for PostgreSQL, MySQL, and SQLite. Use when designing new features, reviewing schemas, or adding multi-tenancy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs relational and document database schemas from requirements or an existing app - tables and collections, keys, relationships, constraints, indexes driven by real query patterns, ERDs, and reversible migration scripts - with PostgreSQL (including Supabase) as the default and MySQL, SQLite, and MongoDB supported. Use when the user wants to model data for a new app or feature, review or fix an existing schema, choose keys or indexes, plan multi-tenancy, normalize or denormalize, or write CREATE TABLE statements or migrations, even if they just describe their app and ask "how should I store this". For moving data between database providers, use database-migrator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and validate model-facing tool definitions with clear names, action-oriented descriptions, bounded JSON Schema parameters, explicit side effects, safe defaults, idempotency, errors, and realistic tests. Use when creating function-calling tools, MCP tools, agent actions, structured tool inputs, or when a model selects the wrong tool, invents arguments, or causes unsafe side effects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design normalized database schemas with tables, relationships, indexes, and constraints for any application domain. Use when the user requests database schema design or provides relevant inputs for this workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
World-class database schema design - data modeling, migrations, relationships, and the battle scars from scaling databases that store billions of rowsUse when "database schema, data model, migration, prisma schema, drizzle schema, create table, add column, foreign key, primary key, uuid, auto increment, soft delete, normalization, denormalization, one to many, many to many, junction table, polymorphic, enum type, index strategy, database, schema, migration, data-model, prisma, drizzle, typeorm, postgresql, mysql, sqlite" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route HugeGraph MCP schema design, validation, and dry-run preview tasks to stable public tools. Use when the user asks to design vertex labels, edge labels, properties, primary keys, indexes, or preview schema operations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
设计数据库实体、表结构、字段类型和约束时使用。适用于新业务建模、API 契约落库、已有表结构重构和 ER 设计。融合 DDD 实体识别 + 关系范式 + 业务约束 + 演进策略。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Projete esquemas de banco de dados robustos e escaláveis para SQL e NoSQL. Fornece diretrizes de normalização, estratégias de indexação, padrões de migração, design de restrições e otimização de desempenho. Garante integridade de dados, desempenho de consultas e modelos de dados mantíveis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design database schemas with normalization, relationships, and constraints. Use when creating new database schemas, designing tables, or planning data models for any database paradigm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Database Architect IA — Expert en conception de bases de données (PostgreSQL, MongoDB, Redis, schema design, migrations). Optimise le stockage et l'accès aux données.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs robust function/tool calling schemas for LLMs with JSON schemas, validation strategies, typed interfaces, and example calls. Use when implementing "function calling", "tool use", "LLM tools", or "agent actions".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs GraphQL schemas with types, queries, mutations, subscriptions, resolvers, and DataLoader patterns for efficient data fetching. Use when users request "GraphQL API", "schema design", "GraphQL setup", "resolvers", or "Apollo Server".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.