What problem does it solve?
Refactoring often breaks field mappings silently: TypeScript type checks pass while wrong dataIndex values, incomplete enum maps, or sync overwrites cause runtime failures like "Invalid Date", blank cells, or lost user edits. This Skill prevents field-name guessing and ensures mappings match the original code's actual behavior.
Core Features & Use Cases
- Field Name Verification: Enforces checking original code (e.g., via git show) and backend API responses instead of inferring field names from type definitions, catching subtle differences like changedAt vs createdAt.
- Enum Mapping Completeness: Provides checklists to verify every enum value, spelling, color, and text is preserved during refactoring of typeMap or statusMap.
- Sync Overwrite Protection: Implements a last-sync-value pattern so external data synchronization (ERP, CRM imports) never clears target fields on null source values or overwrites manual user adjustments.
- Use Case: When refactoring a table component with 10 operation-type enum values, use this Skill to compare against the original code and confirm no enum entries, rowKey fields, or date renderers were broken.
Quick Start
Ask the AI to review your refactored table columns and enum mappings against the original code using the field-mapping-safety checklist before committing.
