ai-ops-cli 0.2.2 → 0.2.4

package/data/rules/code-philosophy.yaml

@@ -19,6 +19,8 @@ content:
     - 'For non-trivial business rules, start with a failing test (TDD).'
     - 'Use a functional-core / imperative-shell structure.'
     - 'Use immutable updates (const/final, copy/spread patterns).'
+    - 'Within a file, order declarations by role: types → constants → validators/guards → helper functions → main logic/exports.'
+    - 'When a file contains multiple semantic groups, add section divider comments (e.g., // ----- types -----) between groups.'
   decision_table:
     - when: 'Implementing complex business logic'
       then: 'Write failing tests first, then implement pure functions'
@@ -28,3 +30,6 @@ content:
       avoid: 'Early shared abstraction'
     - when: 'Similar code appears in three or more places'
       then: 'Extract a clearly named shared function'
+    - when: 'A file has two or more distinct semantic groups (types, constants, logic, etc.)'
+      then: 'Order declarations by role and add section divider comments between groups'
+      avoid: 'Flat interleaving of unrelated declarations without visual separation'

package/data/skills/reference-skills/backend-ts-nestjs-runtime/references/reference.md

@@ -19,6 +19,7 @@
 ## Backend TS Library Constraints
 
 - Do not use moment/dayjs.
+- Do not parse date strings with `new Date(string)`. It applies implicit local timezone coercion and silently shifts dates.
 - Do not use jsonwebtoken.
 - Do not handle Express req/res directly in NestJS handlers.
 - Do not import lodash as a full bundle.
@@ -29,6 +30,7 @@
 
 - Use class-validator and class-transformer DTO validation.
 - Use jose for JWT sign/verify and JWKS workflows.
+- Use date-fns for date manipulation; import functions individually (e.g. `import { parseISO, format } from 'date-fns'`).
 - Use pino via nestjs-pino for structured logs.
 - Use rxjs operators in interceptors, guards, and event streams.
 - Use Vitest with @nestjs/testing and supertest.
@@ -40,4 +42,5 @@
 - When auth or roles depend on handler metadata, use guards.
 - When response transformation or timing is needed, use interceptors.
 - When JWT auth is needed, use jose.
+- When parsing an ISO date string, use `parseISO()` from date-fns; avoid `new Date(string)`.
 - When structured logging is needed, use pino via nestjs-pino.

package/data/skills/reference-skills/frontend-web-react-next-runtime/references/reference.md

@@ -27,6 +27,7 @@
 ## Web Frontend Library Constraints
 
 - Do not use moment.js or dayjs.
+- Do not parse date strings with `new Date(string)`. It applies implicit local timezone coercion and silently shifts dates.
 - Do not use react-icons.
 - Do not use axios in browser code.
 - Do not build conditional className strings manually.
@@ -36,6 +37,7 @@
 ## Web Frontend Library Guidelines
 
 - Keep styling on Tailwind and design tokens.
+- Use date-fns for date formatting and manipulation; import functions individually (e.g. `import { parseISO, format } from 'date-fns'`).
 - Use next-intl for i18n and next-themes for theme switching.
 - Render Recharts only inside client components.
 - Mount one Sonner toaster at the app root.
@@ -48,4 +50,5 @@
 - When page data is needed for first render, fetch in server components.
 - When internal form mutation is needed, use server actions.
 - When form validation is needed, use zod with react-hook-form.
+- When parsing an ISO date string, use `parseISO()` from date-fns; avoid `new Date(string)`.
 - When client UI state is needed, use a zustand slice.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-ops-cli",
-  "version": "0.2.2",
+  "version": "0.2.4",
   "description": "CLI for ai-ops scaffolding — manage AI tool rules and presets",
   "license": "MIT",
   "repository": {