What problem does it solve? When @northguild/gmt-eslint flags Date-related violations in a codebase, developers need a safe, behavior-preserving way to replace native Date APIs and legacy date libraries with @northguild/gmt equivalents without breaking output shape, timezone intent, or boundary behavior. ## Core Features & Use Cases - Guided violation resolution: Maps common Date APIs (Date.now, new Date, Date.parse, Date.UTC) to the appropriate gmt plain/zoned helpers. - Legacy library migration: Replaces imports of moment, moment-timezone, dayjs, luxon, date-fns, date-fns-tz, and spacetime (including require, dynamic import, and re-export forms) with gmt equivalents. - Missing-helper workflow: When no gmt helper exists, directs you to open a GitHub issue with expected behavior, or implement a custom Temporal-based method with robust tests and a PR. - Use Case: After enabling gmt-eslint on a project that uses date-fns, you run ESLint, see dozens of violations, and use this Skill to systematically convert each call site while flagging semantic differences like date-fns setYear rolling to March 1 versus Temporal clamping to February 28. ## Quick Start Ask the assistant to fix the gmt-eslint Date violations in your project by replacing them with @northguild/gmt helpers while preserving existing behavior.