schema-designer

Generate PostgreSQL, OpenAPI, JSON Schema, and GraphQL schemas with migration guidance.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill schema-designer-prathmesh2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-designer
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/schema-designer
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill schema-designer-prathmesh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing robust data schemas across databases, APIs, and contracts is error-prone and time-consuming.

Core Features & Use Cases

  • Unified schema design for PostgreSQL, OpenAPI, JSON Schema, GraphQL, and API contracts.
  • Schema validation, evolution planning, and automatic migration guidance.
  • Use Case: When starting a new service, generate a coherent data model with entities, relations, and contracts.

Quick Start

Create a comprehensive data-schema blueprint for a new user service, including entities, relationships, and API contracts.

Frequently Asked Questions about schema-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a database schema and API contracts for a new service?

To generate a database schema and API contracts for a new service, provide a data model description to produce coherent entities, relationships, PostgreSQL schemas, OpenAPI, and GraphQL definitions automatically.

Can I create both JSON Schema and GraphQL schemas from the same data model?

Yes, you can create both JSON Schema and GraphQL schemas from a unified data model, ensuring consistent API contracts and database structures across different services.

How does schema evolution and migration guidance work for PostgreSQL?

Schema evolution for PostgreSQL includes versioned migration guidance to safely modify database structures over time while maintaining data integrity and backward compatibility across services.

What's the best way to design an ERD with API contract drafting?

The best way to design an ERD with API contract drafting is to define entities and relationships first, then automatically generate OpenAPI specifications to enforce validation across your services.

Do I need to manually validate data models against OpenAPI specifications?

No, manual validation is unnecessary because schema validation is built into the generation process, checking JSON Schema and OpenAPI outputs for consistency and contract compliance automatically.