chore: willboosterify this repo

Author: WillBooster-bot

.cursor/rules/general.mdc

@@ -6,25 +6,31 @@ alwaysApply: true
 
 ## Project Information
 
-- Name: firebase-private-key-to-env
+- Name: `firebase-private-key-to-env`
 - Description: undefined
 - Package Manager: yarn
 
 ## General Instructions
 
-- Do not write tests unless explicitly requested.
+- Create a new branch if the current branch is `main`.
+- Run any `git` commands sequentially.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
+  - Follow the conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
+- Prefer using a single template literal for prompts instead of `join()` with an array of strings.

.husky/pre-commit

@@ -1,3 +1,5 @@
+#!/bin/bash
+
 changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)"
 
 run_if_changed() {
@@ -6,7 +8,5 @@ run_if_changed() {
   fi
 }
 
-run_if_changed "\..+-version" "awk '{print \$1}' .tool-versions | xargs -I{} asdf plugin add {}"
-run_if_changed "\..+-version" "asdf plugin update --all"
-run_if_changed "\..+-version" "asdf install"
+run_if_changed "(mise\.toml|\.mise\.toml|\.tool-versions|\..+-version)" "mise install"
 run_if_changed "package\.json" "yarn"

.husky/pre-push

@@ -0,0 +1 @@
+yarn run typecheck

.husky/post-merge .lefthook/post-merge/prepare.sh.husky/post-merge renamed to .lefthook/post-merge/prepare.sh

@@ -1,24 +1,30 @@
 ## Project Information
 
-- Name: firebase-private-key-to-env
+- Name: `firebase-private-key-to-env`
 - Description: undefined
 - Package Manager: yarn
 
 ## General Instructions
 
-- Do not write tests unless explicitly requested.
+- Create a new branch if the current branch is `main`.
+- Run any `git` commands sequentially.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
+  - Follow the conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
+- Prefer using a single template literal for prompts instead of `join()` with an array of strings.

.lefthook/pre-push/check.sh

@@ -1,24 +1,30 @@
 ## Project Information
 
-- Name: firebase-private-key-to-env
+- Name: `firebase-private-key-to-env`
 - Description: undefined
 - Package Manager: yarn
 
 ## General Instructions
 
-- Do not write tests unless explicitly requested.
+- Create a new branch if the current branch is `main`.
+- Run any `git` commands sequentially.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
+  - Follow the conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
+- Prefer using a single template literal for prompts instead of `join()` with an array of strings.

AGENTS.md

@@ -1,24 +1,30 @@
 ## Project Information
 
-- Name: firebase-private-key-to-env
+- Name: `firebase-private-key-to-env`
 - Description: undefined
 - Package Manager: yarn
 
 ## General Instructions
 
-- Do not write tests unless explicitly requested.
+- Create a new branch if the current branch is `main`.
+- Run any `git` commands sequentially.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
+  - Follow the conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
+- Prefer using a single template literal for prompts instead of `join()` with an array of strings.

CLAUDE.md

@@ -0,0 +1,20 @@
+post-merge:
+  scripts:
+    prepare.sh:
+      runner: bash
+pre-push:
+  scripts:
+    check.sh:
+      runner: bash
+pre-commit:
+  commands:
+    cleanup:
+      glob: '*.{astro,cjs,css,cts,gql,htm,html,java,js,json,json5,jsonc,jsx,md,mjs,mts,scss,svelte,ts,tsx,vue,yaml,yml}'
+      run: yarn run format && yarn run lint-fix && git add -- {staged_files}
+    check-migrations:
+      glob: '**/migration.sql'
+      run: |-
+        if grep -q 'Warnings:' {staged_files}; then
+          echo "Migration SQL files ({staged_files}) contain warnings! Please solve the warnings and commit again."
+          exit 1
+        fi

GEMINI.md

@@ -1,25 +1,25 @@
 {
   "name": "firebase-private-key-to-env",
   "version": "1.0.0",
-  "repository": "github:WillBooster/firebase-private-key-to-env",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/WillBooster/firebase-private-key-to-env.git"
+  },
   "license": "Apache-2.0",
   "author": "WillBooster Inc.",
   "main": "src/index.ts",
   "scripts": {
     "check-all-for-ai": "yarn check-for-ai && yarn test",
-    "check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
+    "check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
     "cleanup": "yarn format && yarn lint-fix",
     "format": "sort-package-json && yarn prettify",
-    "postinstall": "husky || true",
     "lint": "eslint --color",
     "lint-fix": "yarn lint --fix",
-    "prepack": "pinst --disable",
-    "postpack": "pinst --enable",
-    "prepare": "husky || true",
+    "prepare": "lefthook install || true",
     "prettify": "prettier --cache --color --write \"**/{.*/,}*.{cjs,css,cts,htm,html,java,js,json,json5,jsonc,jsx,md,mjs,mts,scss,ts,tsx,vue,yaml,yml}\" \"!**/test{-,/}fixtures/**\" || true",
     "start": "babel-node -x .js,.jsx,.es6,.es,.ts src/index.ts",
     "test": "echo \"No tests configured\"",
-    "typecheck": "tsc --noEmit --Pretty"
+    "typecheck": "tsc --noEmit"
   },
   "prettier": "@willbooster/prettier-config",
   "dependencies": {
@@ -34,14 +34,17 @@
     "@babel/plugin-proposal-numeric-separator": "7.18.6",
     "@babel/preset-env": "7.29.2",
     "@babel/preset-typescript": "7.28.5",
+    "@eslint/js": "10.0.1",
+    "@tsconfig/node-lts": "24.0.0",
+    "@tsconfig/node-ts": "23.6.4",
     "@types/eslint": "9.6.1",
     "@types/micromatch": "4.0.10",
     "@types/node": "24.12.0",
     "@types/yargs": "17.0.35",
-    "@willbooster/eslint-config-ts": "11.4.12",
-    "@willbooster/prettier-config": "10.2.4",
-    "eslint": "9.39.1",
-    "eslint-config-flat-gitignore": "2.2.1",
+    "@willbooster/eslint-config-ts": "11.5.0",
+    "@willbooster/prettier-config": "10.3.0",
+    "eslint": "10.1.0",
+    "eslint-config-flat-gitignore": "2.3.0",
     "eslint-config-prettier": "10.1.8",
     "eslint-import-resolver-typescript": "4.4.4",
     "eslint-plugin-import-x": "4.16.2",
@@ -50,15 +53,14 @@
     "eslint-plugin-unicorn": "63.0.0",
     "eslint-plugin-unused-imports": "4.4.1",
     "globals": "17.4.0",
-    "husky": "9.1.7",
+    "lefthook": "2.1.4",
     "lint-staged": "16.4.0",
     "micromatch": "4.0.8",
-    "pinst": "3.0.0",
     "prettier": "3.8.1",
     "prettier-plugin-java": "2.8.1",
     "sort-package-json": "3.6.1",
-    "typescript": "5.9.3",
-    "typescript-eslint": "8.57.1"
+    "typescript": "^5",
+    "typescript-eslint": "8.57.2"
   },
   "packageManager": "yarn@4.13.0",
   "publishConfig": {