@clipboard-health/ai-rules 0.3.2 → 1.0.0

package/README.md

@@ -56,7 +56,7 @@ npm install --save-dev @clipboard-health/ai-rules
 4. Commit the generated files:
 
    ```bash
-   git add AGENTS.md CLAUDE.md
+   git add .
    git commit -m "feat: add AI coding rules"
    ```
 
@@ -74,10 +74,10 @@ npm update @clipboard-health/ai-rules
 npm install
 
 # Review the changes
-git diff AGENTS.md CLAUDE.md
+git diff .
 
 # Commit the updates
-git add AGENTS.md CLAUDE.md
+git add .
 git commit -m "chore: update AI coding rules"
 ```
 

package/backend/AGENTS.md

@@ -96,8 +96,10 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
        EXAMPLE_NOTIFICATION_JOB_NAME,
        // Important: Read the TypeDoc documentation for additional context.
        {
-         // Set expiresAt at enqueue-time so it remains stable across job retries.
-         // Use date-fns in your service instead of this manual calculation.
+         /**
+          * Set expiresAt at enqueue-time so it remains stable across job retries. Use date-fns in your
+          * service instead of this manual calculation.
+          */
          expiresAt: new Date(Date.now() + 60 * 60_000).toISOString(),
          // Set idempotencyKey at enqueue-time so it remains stable across job retries.
          idempotencyKey: {
@@ -169,6 +171,7 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -183,15 +186,6 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/backend/CLAUDE.md

@@ -94,8 +94,10 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
        EXAMPLE_NOTIFICATION_JOB_NAME,
        // Important: Read the TypeDoc documentation for additional context.
        {
-         // Set expiresAt at enqueue-time so it remains stable across job retries.
-         // Use date-fns in your service instead of this manual calculation.
+         /**
+          * Set expiresAt at enqueue-time so it remains stable across job retries. Use date-fns in your
+          * service instead of this manual calculation.
+          */
          expiresAt: new Date(Date.now() + 60 * 60_000).toISOString(),
          // Set idempotencyKey at enqueue-time so it remains stable across job retries.
          idempotencyKey: {
@@ -167,6 +169,7 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -181,15 +184,6 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/common/AGENTS.md

@@ -13,6 +13,7 @@
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -27,15 +28,6 @@
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/common/CLAUDE.md

@@ -11,6 +11,7 @@
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -25,15 +26,6 @@
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/frontend/AGENTS.md

@@ -13,6 +13,7 @@
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -27,15 +28,6 @@
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/frontend/CLAUDE.md

@@ -11,6 +11,7 @@
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -25,15 +26,6 @@
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/fullstack/AGENTS.md

@@ -96,8 +96,10 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
        EXAMPLE_NOTIFICATION_JOB_NAME,
        // Important: Read the TypeDoc documentation for additional context.
        {
-         // Set expiresAt at enqueue-time so it remains stable across job retries.
-         // Use date-fns in your service instead of this manual calculation.
+         /**
+          * Set expiresAt at enqueue-time so it remains stable across job retries. Use date-fns in your
+          * service instead of this manual calculation.
+          */
          expiresAt: new Date(Date.now() + 60 * 60_000).toISOString(),
          // Set idempotencyKey at enqueue-time so it remains stable across job retries.
          idempotencyKey: {
@@ -169,6 +171,7 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -183,15 +186,6 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/fullstack/CLAUDE.md

@@ -94,8 +94,10 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
        EXAMPLE_NOTIFICATION_JOB_NAME,
        // Important: Read the TypeDoc documentation for additional context.
        {
-         // Set expiresAt at enqueue-time so it remains stable across job retries.
-         // Use date-fns in your service instead of this manual calculation.
+         /**
+          * Set expiresAt at enqueue-time so it remains stable across job retries. Use date-fns in your
+          * service instead of this manual calculation.
+          */
          expiresAt: new Date(Date.now() + 60 * 60_000).toISOString(),
          // Set idempotencyKey at enqueue-time so it remains stable across job retries.
          idempotencyKey: {
@@ -167,6 +169,7 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Use camelCase for files and directories (e.g., modules/shiftOffers.ts).
 - When declaring functions, use the `function` keyword, not `const`.
 - Prefer data immutability.
+- Use Conventional Commits 1.0 for commit messages.
 
 <!-- Source: .ruler/common/errorHandlingAndValidation.md -->
 
@@ -181,15 +184,6 @@ Send notifications through [Knock](https://docs.knock.app) using the `@clipboard
 - Implement proper error logging and user-friendly error messages.
 - Favor `@clipboard-health/util-ts`'s `Either` type for expected errors instead of `try`/`catch`.
 
-<!-- Source: .ruler/common/keyConventions.md -->
-
-# Key conventions
-
-- You are familiar with the latest features and best practices.
-- You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
-- You always write correct, up-to-date, bug-free, fully functional, working, secure, easy-to-read, and efficient code.
-- If there might not be a correct answer or do not know the answer, say so instead of guessing.
-
 <!-- Source: .ruler/common/testing.md -->
 
 # Testing

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@clipboard-health/ai-rules",
   "description": "Pre-built AI agent rules for consistent coding standards.",
-  "version": "0.3.2",
+  "version": "1.0.0",
   "bugs": "https://github.com/ClipboardHealth/core-utils/issues",
   "devDependencies": {
     "@intellectronica/ruler": "0.3.10"

package/scripts/constants.js

@@ -1,11 +1,14 @@
 "use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.PROFILES = exports.PATHS = void 0;
-const node_path_1 = require("node:path");
-const packageRoot = (0, node_path_1.join)(__dirname, "..");
+const node_path_1 = __importDefault(require("node:path"));
+const packageRoot = node_path_1.default.join(__dirname, "..");
 exports.PATHS = {
     packageRoot,
-    outputDirectory: (0, node_path_1.join)(packageRoot, "..", "..", "dist", "packages", "ai-rules"),
+    outputDirectory: node_path_1.default.join(packageRoot, "..", "..", "dist", "packages", "ai-rules"),
 };
 exports.PROFILES = {
     frontend: ["common", "frontend"],

package/scripts/sync.js

@@ -1,14 +1,17 @@
 "use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
 Object.defineProperty(exports, "__esModule", { value: true });
-/* eslint-disable unicorn/no-process-exit */
-/* eslint-disable n/no-process-exit */
+/* eslint-disable unicorn/no-process-exit, n/no-process-exit */
+// eslint-disable-next-line n/no-unsupported-features/node-builtins
 const promises_1 = require("node:fs/promises");
-const node_path_1 = require("node:path");
+const node_path_1 = __importDefault(require("node:path"));
 const constants_1 = require("./constants");
 const toErrorMessage_1 = require("./toErrorMessage");
 const PATHS = {
-    projectRoot: (0, node_path_1.join)(__dirname, "../../../.."),
-    rules: (0, node_path_1.join)(__dirname, ".."),
+    projectRoot: node_path_1.default.join(__dirname, "../../../.."),
+    rules: node_path_1.default.join(__dirname, ".."),
 };
 function getProfileFromArguments() {
     const profile = process.argv[2];
@@ -24,7 +27,7 @@ async function sync() {
     try {
         const profile = getProfileFromArguments();
         // Force copy files; rely on `git` if it overwrites files.
-        await (0, promises_1.cp)((0, node_path_1.join)(PATHS.rules, profile), PATHS.projectRoot, { recursive: true, force: true });
+        await (0, promises_1.cp)(node_path_1.default.join(PATHS.rules, profile), PATHS.projectRoot, { force: true, recursive: true });
         console.log(`✅ @clipboard-health/ai-rules synced ${profile}`);
     }
     catch (error) {
@@ -35,5 +38,4 @@ async function sync() {
 }
 // eslint-disable-next-line unicorn/prefer-top-level-await
 void sync();
-/* eslint-enable n/no-process-exit */
-/* eslint-enable unicorn/no-process-exit */
+/* eslint-enable unicorn/no-process-exit, n/no-process-exit */