What problem does it solve?
Frontend-backend interface contracts often drift silently: list endpoints return raw arrays while the frontend expects paginated objects, filter options come back empty, and temporary frontend compatibility shims end up masking the real backend contract problems indefinitely. This Skill provides a structured checklist to detect and fix contract drift at the root cause.
Core Features & Use Cases
- Response Wrapping Audit: Verifies that list, detail, enum, and filter endpoints all use the project's unified success response helper instead of ad-hoc shapes.
- Pagination & Filter Contract Checks: Confirms field naming (page, pageSize, total, items), page index base, and that filter options come from real data rather than contract mismatches.
- Temporary Compatibility Governance: Requires every frontend compatibility branch to document its exit condition and removal plan, separating root-cause fixes from short-term fallbacks.
- Use Case: During frontend-backend integration, a list page renders but pagination is broken and filters are empty. Use this Skill to inspect the real API responses, identify that the backend returns a bare array instead of the paginated wrapper, fix the backend contract, and schedule removal of the frontend dual-format shim.
Quick Start
Use the cc-api-contract-safety skill to review the list, detail, and filter endpoints of this feature and check whether the response wrapping and pagination contracts are consistent.
