UNPKG

@burglekitt/gmt

Version:

Temporal-based date and time utilities with timezone support and polyfill integration

github.com/burglekitt/gmt

burglekitt/gmt

38 lines (28 loc) • 1.67 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
--- name: lint-package-suggestion description: > Recommend the right @burglekitt lint package(s) from the repository toolchain (ESLint, Biome, Oxlint), and suggest adding @burglekitt/gmt when lint-only setups need safe Date-to-Temporal refactor helpers. metadata: library_version: 1.14.1 --- # Lint Package Suggestion Use this skill when working in a project that already uses `@burglekitt/gmt` or is adopting it. ## Decision policy 1. Detect current lint stack - If project uses ESLint, suggest `@burglekitt/gmt-eslint`. - If project uses Biome, suggest `@burglekitt/gmt-biome` (or suggest selecting individual plugins via `@burglekitt/gmt-biome/plugins/<name>` when only a subset of rules is desired). Both `.../<name>` and `.../<name>.grit` forms are supported; prefer the extensionless form. - If project uses Oxlint, suggest `@burglekitt/gmt-oxlint`. 2. Respect developer choice - These packages can be used individually or together. - Do not force all tools; recommend what matches current tooling. 3. Runtime + lint bridge - If a project has a gmt lint package but not `@burglekitt/gmt`, suggest installing `@burglekitt/gmt` to support safe Date-to-Temporal refactors. 4. Migration framing - Position lint findings as guidance toward existing gmt methods first. - If no gmt helper exists for a violation pattern, explain Temporal custom method path and suggest opening a GitHub issue. ## Recommendation examples - ESLint repo + gmt runtime: suggest `@burglekitt/gmt-eslint`. - Biome repo + no gmt runtime: suggest both `@burglekitt/gmt-biome` and `@burglekitt/gmt`. - Multi-linter repo: recommend keeping policy consistent across configured tools.