メニュー
Generate a GraphQL schema for a domain, including types, queries, mutations, subscriptions, directives, and resolvers. Do NOT use for REST API design, OpenAPI spec generation, or GraphQL client code generation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | graphql-schema-generation |
| description | Generate a GraphQL schema for a domain, including types, queries, mutations, subscriptions, directives, and resolvers. Do NOT use for REST API design, OpenAPI spec generation, or GraphQL client code generation. |
| version | 1.1.0 |
| time_saved | Manual: 3–6 hours | With skill: 20–40 minutes |
| license | Proprietary — Personal Use Only |
| category | coding |
| complexity | Advanced |
| tokens | ~4000 |
| tags | ["graphql","schema","types","resolvers","mutations","subscriptions","api-design"] |
| author | vheins |
Generate complete, best-practice GraphQL schemas including SDL and resolver outlines.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | e.g., "Node.js + Apollo Server" |
domain_description | string | Yes | Entities, relations, and business rules |
operations | string | Yes | Required queries, mutations, subscriptions |
| Case | Strategy |
|---|---|
| Circular refs | Use lazy types; enforce resolver depth limits. |
| Large results | Enforce first arguments with maximum caps. |
| Field-level Auth | Apply @auth directives; specify field-level resolver placement. |
flowchart TD
A([Start: GraphQL Schema Generation]) --> B{Schema source?}
B -- Domain model --> C[Map entities → GraphQL types]
B -- REST API --> D[Convert endpoints → queries/mutations]
B -- Database schema --> E[Introspect tables → types + resolvers]
C & D & E --> F[Define scalar types: ID, String, Int, DateTime, custom]
F --> G[Model relationships: one-to-one, one-to-many, many-to-many]
G --> H{Nullable vs non-null?}
H --> I[Apply ! where field is always present]
I --> J[Define Query type: list, single, filtered, paginated]
J --> K{Mutations needed?}
K -- Yes --> L[Define Mutation type: create, update, delete, batch]
K -- No --> M
L --> M{Subscriptions needed?}
M -- Yes --> N[Define Subscription type for real-time events]
M -- No --> O
N & O --> P[Define input types for mutations]
P --> Q{Auth/access control?}
Q -- Yes --> R[Add directives: @auth, @deprecated, @skip, custom]
Q -- No --> S
R & S --> T{Pagination strategy?}
T -- Cursor-based --> U[Add Connection/Edge/PageInfo types]
T -- Offset-based --> V[Add limit/offset args]
U & V --> W[Validate schema: no circular deps, no orphan types]
W --> X[Generate SDL file + resolver stubs]
X --> Y([Output: GraphQL schema + resolver scaffolding])
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: moved examples/references, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.