Validate TypeScript API mappers for exact field count and completeness.
npx skills add https://github.com/zerobias-org/module --skill mapper-validation
Please help me install this Agent Skill. Skill: mapper-validation Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/mapper-validation Command: npx skills add https://github.com/zerobias-org/module --skill mapper-validation
This Skill provides a rigorous, end-to-end workflow to enforce zero missing fields when mapping API interfaces to mapped types, preventing runtime errors and drift between spec and implementation.
Validate a new API resource by running the mapper-validation process to ensure all fields are mapped and validated before deployment.
High-intent search queries and answers about installing and using this skill.
You validate TypeScript API mappers by enforcing exact field-count parity between generated interfaces and mapper outputs, ensuring every required and optional field is present. This runtime validation catches API-spec drift and guarantees zero missing fields across modules and nested objects.
Field-count parity in API mapping ensures the number of fields in the mapper output exactly matches the generated TypeScript interface. It validates required and optional fields, including nested objects, to enforce end-to-end correctness and prevent drift between spec and implementation.
To check for API spec drift, apply runtime validation rules to mapper outputs against generated TypeScript interfaces from api.yml. This process validates field counts and nested object mappings, catching discrepancies between the API schema and implementation during integration.
Yes, mapper validation works with nested objects in TypeScript interfaces by explicitly validating their field mappings. It ensures both required and optional nested fields are present in the mapping output, enforcing strict field counting for end-to-end correctness across modules.
You validate optional and required fields by running a validation process that enforces exact field-count parity between the API schema and mapper outputs. This includes helper mappers and nested objects, ensuring zero missing fields before deployment.
You need runtime validation for TypeScript API mapping when you want to catch API-spec drift during integration and testing. It enforces zero missing fields by validating exact field-count parity between generated interfaces and mapped types.
zerobias-orgRegenerate TypeScript interfaces from api.yml after API changes.
zerobias-orgCompare raw API responses with mapped outputs to detect missing or mismapped fields.
bobmatnycDefine TypeScript database schemas and build type-safe SQL queries.
luyi985Validate runtime data against predefined schemas using zod or io-ts.
