verify-type-parity

What problem does it solve?

This Skill prevents bugs and integration issues by ensuring that the TypeScript types used in the frontend precisely match the Kotlin Data Transfer Objects (DTOs) and Entities defined in the backend.

Core Features & Use Cases

• Detects Loose Types: Identifies the use of any, unknown, Record<string, any>, and Record<string, unknown> in API contracts, promoting stricter typing.
• Checks Inline Types: Ensures API response/request types are defined in shared type files rather than inline within API client code.
• Validates DTO Location: Verifies that backend data class definitions are appropriately placed in DTO packages, not scattered within controllers.
• Identifies Missing Types: Flags backend DTOs that lack corresponding frontend TypeScript interfaces.
• Verifies Field Matching: Compares fields between frontend types and backend DTOs/Entities for discrepancies.
• Use Case: After adding a new field to a backend User DTO, run this Skill to confirm that the corresponding User interface in the frontend has also been updated correctly, preventing runtime errors.

Quick Start

Run the verify-type-parity skill to check for any discrepancies between frontend TypeScript types and backend Kotlin DTOs.