원클릭으로 Manus에서 모든 스킬 실행

시작하기

graphql-contract

스타3

포크0

업데이트2026년 1월 15일 22:25

Use when changing GraphQL schema, resolvers, or frontend GraphQL documents so the contract and codegen stay in sync.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

lmiguelvargasf

lmiguelvargasf/nova

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

GraphQL contract & sync

When to use

You modify backend GraphQL types/resolvers or the schema.
You add or edit frontend .graphql documents.
You suspect schema and generated types are out of sync.

Steps

Backend: implement changes under backend/src/backend/apps/**/graphql/.
Sync: run task frontend:codegen from the repo root.
- This runs task backend:schema:export to update frontend/schema/schema.graphql.
- Then runs pnpm codegen to regenerate TypeScript types.
Frontend: update frontend/src/ to use the newly generated types/fragments.
Verify: run task frontend:check.

Constraints and guardrails

The Strawberry backend is the source of truth; do not manually edit frontend/schema/schema.graphql.
Do not hand-write TypeScript interfaces for GraphQL results; use generated types in frontend/src/lib/graphql/.
Schema changes and frontend sync should be in the same change set.
Breaking changes (removing/renaming fields, Nullable → Non-Null, adding required args) require immediate frontend updates after codegen.
Avoid N+1 by using SQLAlchemy eager loading (selectinload/joinedload) and moving complex logic into services.

References

backend/src/backend/apps/**/graphql/
frontend/schema/schema.graphql
frontend/src/lib/graphql/
frontend/**/codegen.*

이 저장소의 다른 Skills

같은 저장소

advanced-alchemy

lmiguelvargasf/nova

Expert knowledge for Advanced Alchemy / SQLAlchemy ORM patterns. Use when working with models, services, repositories, or database migrations.

2026-02-173

litestar

lmiguelvargasf/nova

Expert knowledge for Litestar Python web framework. Use when working with Litestar routes, plugins, middleware, dependency injection, or configuration.

2026-02-173

workflow-taskfile

lmiguelvargasf/nova

Use when running installs, dev servers, tests, lint/format, codegen, or Docker lifecycle tasks; Taskfile is the source of truth.

2026-01-203

backend-async-tasks

lmiguelvargasf/nova

Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend.

2026-01-153

guardrails

lmiguelvargasf/nova

Use for change discipline, validation expectations, and safety checks when making repo changes.

2026-01-153

name	graphql-contract
description	Use when changing GraphQL schema, resolvers, or frontend GraphQL documents so the contract and codegen stay in sync.

GraphQL contract & sync

When to use

You modify backend GraphQL types/resolvers or the schema.
You add or edit frontend .graphql documents.
You suspect schema and generated types are out of sync.

Steps

Backend: implement changes under backend/src/backend/apps/**/graphql/.
Sync: run task frontend:codegen from the repo root.
- This runs task backend:schema:export to update frontend/schema/schema.graphql.
- Then runs pnpm codegen to regenerate TypeScript types.
Frontend: update frontend/src/ to use the newly generated types/fragments.
Verify: run task frontend:check.

Constraints and guardrails

The Strawberry backend is the source of truth; do not manually edit frontend/schema/schema.graphql.
Do not hand-write TypeScript interfaces for GraphQL results; use generated types in frontend/src/lib/graphql/.
Schema changes and frontend sync should be in the same change set.
Breaking changes (removing/renaming fields, Nullable → Non-Null, adding required args) require immediate frontend updates after codegen.
Avoid N+1 by using SQLAlchemy eager loading (selectinload/joinedload) and moving complex logic into services.

References

backend/src/backend/apps/**/graphql/
frontend/schema/schema.graphql
frontend/src/lib/graphql/
frontend/**/codegen.*