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

integration-contract-alignment

스타0

포크0

업데이트2026년 5월 20일 20:18

Align frontend consumers with backend API contracts. Use for route or DTO changes, compatibility windows, rollout sequencing, and cross-stack acceptance criteria.

설치

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

Manus에서 실행

출처

kwkraus

kwkraus/edgefront-builder

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

다운로드

Manus에서 실행

Integration Contract Alignment

When to Use

Backend route/DTO changes that impact frontend consumption
Frontend integration work against evolving backend responses
PR review focused on cross-stack API compatibility

Quick Checklist

Identify changed routes and response fields.
Map frontend consumers to impacted contract fields.
Define compatibility impact and migration strategy.
Align payload expectations before implementation merge.

Deep Workflow

Inventory affected backend endpoints and frontend call sites.
Confirm route, verb, request shape, and response shape alignment.
Classify compatibility impact (additive, soft-breaking, hard-breaking).
Define transition plan for non-additive changes (versioning, fallback, phased rollout).
Ensure frontend type/model updates are consistent with backend contract.
Produce explicit integration acceptance checks for key user flows.

Decision Points

If change is hard-breaking, block merge until migration path is explicit.
If frontend and backend cannot ship simultaneously, require backward-compatible contract window.
If response semantics changed, route to status-code-decision-matrix for status consistency.

Completion Checks

Contract changes and frontend updates are mutually consistent.
Compatibility impact is documented with rollout assumptions.
Key integration flow checks are defined and testable.

이 저장소의 다른 Skills

같은 저장소

api-contract-design

kwkraus/edgefront-builder

Design ASP.NET Core minimal API request and response contracts. Use for DTO shapes, route and verb decisions, OpenAPI metadata, and compatibility planning before implementation.

2026-05-200

api-test-strategy

kwkraus/edgefront-builder

Define focused tests for ASP.NET Core minimal APIs. Use for endpoint branch coverage, contract assertions, regression planning, and choosing the narrowest useful verification command.

2026-05-200

data-schema-migration

kwkraus/edgefront-builder

Design EF Core schema changes, constraints, and migrations for the backend data model. Use for entity updates, indexes, uniqueness rules, cascade behavior, and migration planning.

2026-05-200

delegated-data-sync-pipeline

kwkraus/edgefront-builder

Design and implement the delegated Graph sync pipeline from fetch through normalization, upsert, and metrics recompute. Use for user-initiated registrations or attendance sync, idempotency, and atomic recomputation.

2026-05-200

deployment-safety-and-rollback

kwkraus/edgefront-builder

Define deployment safeguards, environment protections, and rollback readiness for CI/CD releases. Use when adding or reviewing release jobs, promotion controls, or recovery plans.

2026-05-200

domain-metrics-computation

kwkraus/edgefront-builder

Apply email and domain normalization plus session and series metric rules, including W1/W2 warm-account logic and internal-domain exclusion. Use for domain logic changes, recompute behavior, and mandatory unit-test coverage.

2026-05-200

name	integration-contract-alignment
description	Align frontend consumers with backend API contracts. Use for route or DTO changes, compatibility windows, rollout sequencing, and cross-stack acceptance criteria.
argument-hint	Describe the backend contract change, affected frontend consumers, rollout constraints, and compatibility expectations.

Integration Contract Alignment

When to Use

Backend route/DTO changes that impact frontend consumption
Frontend integration work against evolving backend responses
PR review focused on cross-stack API compatibility

Quick Checklist

Identify changed routes and response fields.
Map frontend consumers to impacted contract fields.
Define compatibility impact and migration strategy.
Align payload expectations before implementation merge.

Deep Workflow

Inventory affected backend endpoints and frontend call sites.
Confirm route, verb, request shape, and response shape alignment.
Classify compatibility impact (additive, soft-breaking, hard-breaking).
Define transition plan for non-additive changes (versioning, fallback, phased rollout).
Ensure frontend type/model updates are consistent with backend contract.
Produce explicit integration acceptance checks for key user flows.

Decision Points

If change is hard-breaking, block merge until migration path is explicit.
If frontend and backend cannot ship simultaneously, require backward-compatible contract window.
If response semantics changed, route to status-code-decision-matrix for status consistency.

Completion Checks

Contract changes and frontend updates are mutually consistent.
Compatibility impact is documented with rollout assumptions.
Key integration flow checks are defined and testable.