Skip to content

Commit 1765d93

Browse files
WillBooster-botWillBooster-bot
committed
chore: willboosterify this repo
1 parent 4fb71d4 commit 1765d93

File tree

12 files changed

+549
-398
lines changed

12 files changed

+549
-398
lines changed

‎.cursor/rules/general.mdc‎

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,32 @@ alwaysApply: true
88

99
- Name: willbooster-shared
1010
- Description: undefined
11-
- Package Manager: yarn
11+
- Package Manager: yarn on zsh
1212

13-
## General Instructions
13+
## Development Workflow
1414

15-
- Do not write tests unless explicitly requested.
16-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
17-
- 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.
18-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
19-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
20-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
21-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
22-
- Always create new commits. Avoid using `--amend`.
15+
When changing code, complete these steps before responding to the user.
16+
17+
1. If the current branch is `main`, create a new branch.
18+
- Include unexpected changes since they are mine.
19+
2. Make code changes as needed.
20+
3. If possible, write e2e tests for your changes.
21+
4. Fix your changes until `yarn check-all-for-ai` (running all tests, taking 30 mins) or `yarn check-for-ai` (only type checking and linting) passes.
22+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
23+
5. Commit your changes to the current branch and push.xd
24+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
25+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
26+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
27+
6. Create a pull request using `gh`.
28+
- The pull request title should match your commit message.
29+
7. Repeat the following steps until the test workflow passes:
30+
1. Monitor the CI results using `gh` until the test workflow completes.
31+
- e.g., `while :; do gh run list -b "$(git branch --show-current)" --json status,conclusion | jq -e '.[] | select(.conclusion=="failure")' && exit 1; gh run list -b "$(git branch --show-current)" --json status | jq -e '.[] | select(.status=="completed" | not)' || exit 0; sleep 1m; done`
32+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
33+
3. Fetch unresolved review comments from the pull request using `gh`. Address them and then mark them as resolved.
34+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved | not)'`
35+
4. Commit your changes and push.
36+
5. Write `/gemini review` in the pull request.
2337

2438
## Coding Style
2539

‎AGENTS.md‎

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,18 +2,32 @@
22

33
- Name: willbooster-shared
44
- Description: undefined
5-
- Package Manager: yarn
5+
- Package Manager: yarn on zsh
66

7-
## General Instructions
7+
## Development Workflow
88

9-
- Do not write tests unless explicitly requested.
10-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
11-
- 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.
12-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
13-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
14-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
15-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
16-
- Always create new commits. Avoid using `--amend`.
9+
When changing code, complete these steps before responding to the user.
10+
11+
1. If the current branch is `main`, create a new branch.
12+
- Include unexpected changes since they are mine.
13+
2. Make code changes as needed.
14+
3. If possible, write e2e tests for your changes.
15+
4. Fix your changes until `yarn check-all-for-ai` (running all tests, taking 30 mins) or `yarn check-for-ai` (only type checking and linting) passes.
16+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
17+
5. Commit your changes to the current branch and push.xd
18+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
19+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
20+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
21+
6. Create a pull request using `gh`.
22+
- The pull request title should match your commit message.
23+
7. Repeat the following steps until the test workflow passes:
24+
1. Monitor the CI results using `gh` until the test workflow completes.
25+
- e.g., `while :; do gh run list -b "$(git branch --show-current)" --json status,conclusion | jq -e '.[] | select(.conclusion=="failure")' && exit 1; gh run list -b "$(git branch --show-current)" --json status | jq -e '.[] | select(.status=="completed" | not)' || exit 0; sleep 1m; done`
26+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
27+
3. Fetch unresolved review comments from the pull request using `gh`. Address them and then mark them as resolved.
28+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved | not)'`
29+
4. Commit your changes and push.
30+
5. Write `/gemini review` in the pull request.
1731

1832
## Coding Style
1933

‎CLAUDE.md‎

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,18 +2,32 @@
22

33
- Name: willbooster-shared
44
- Description: undefined
5-
- Package Manager: yarn
5+
- Package Manager: yarn on zsh
66

7-
## General Instructions
7+
## Development Workflow
88

9-
- Do not write tests unless explicitly requested.
10-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
11-
- 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.
12-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
13-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
14-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
15-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
16-
- Always create new commits. Avoid using `--amend`.
9+
When changing code, complete these steps before responding to the user.
10+
11+
1. If the current branch is `main`, create a new branch.
12+
- Include unexpected changes since they are mine.
13+
2. Make code changes as needed.
14+
3. If possible, write e2e tests for your changes.
15+
4. Fix your changes until `yarn check-all-for-ai` (running all tests, taking 30 mins) or `yarn check-for-ai` (only type checking and linting) passes.
16+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
17+
5. Commit your changes to the current branch and push.xd
18+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
19+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
20+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
21+
6. Create a pull request using `gh`.
22+
- The pull request title should match your commit message.
23+
7. Repeat the following steps until the test workflow passes:
24+
1. Monitor the CI results using `gh` until the test workflow completes.
25+
- e.g., `while :; do gh run list -b "$(git branch --show-current)" --json status,conclusion | jq -e '.[] | select(.conclusion=="failure")' && exit 1; gh run list -b "$(git branch --show-current)" --json status | jq -e '.[] | select(.status=="completed" | not)' || exit 0; sleep 1m; done`
26+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
27+
3. Fetch unresolved review comments from the pull request using `gh`. Address them and then mark them as resolved.
28+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved | not)'`
29+
4. Commit your changes and push.
30+
5. Write `/gemini review` in the pull request.
1731

1832
## Coding Style
1933

‎GEMINI.md‎

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,18 +2,32 @@
22

33
- Name: willbooster-shared
44
- Description: undefined
5-
- Package Manager: yarn
5+
- Package Manager: yarn on zsh
66

7-
## General Instructions
7+
## Development Workflow
88

9-
- Do not write tests unless explicitly requested.
10-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
11-
- 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.
12-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
13-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
14-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
15-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
16-
- Always create new commits. Avoid using `--amend`.
9+
When changing code, complete these steps before responding to the user.
10+
11+
1. If the current branch is `main`, create a new branch.
12+
- Include unexpected changes since they are mine.
13+
2. Make code changes as needed.
14+
3. If possible, write e2e tests for your changes.
15+
4. Fix your changes until `yarn check-all-for-ai` (running all tests, taking 30 mins) or `yarn check-for-ai` (only type checking and linting) passes.
16+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
17+
5. Commit your changes to the current branch and push.xd
18+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
19+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
20+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
21+
6. Create a pull request using `gh`.
22+
- The pull request title should match your commit message.
23+
7. Repeat the following steps until the test workflow passes:
24+
1. Monitor the CI results using `gh` until the test workflow completes.
25+
- e.g., `while :; do gh run list -b "$(git branch --show-current)" --json status,conclusion | jq -e '.[] | select(.conclusion=="failure")' && exit 1; gh run list -b "$(git branch --show-current)" --json status | jq -e '.[] | select(.status=="completed" | not)' || exit 0; sleep 1m; done`
26+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
27+
3. Fetch unresolved review comments from the pull request using `gh`. Address them and then mark them as resolved.
28+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved | not)'`
29+
4. Commit your changes and push.
30+
5. Write `/gemini review` in the pull request.
1731

1832
## Coding Style
1933

‎package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
"scripts": {
1212
"build": "yarn workspaces foreach --all --parallel --verbose run build",
1313
"check-all-for-ai": "yarn check-for-ai && yarn test",
14-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
14+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
1515
"cleanup": "yarn format && yarn lint-fix",
1616
"format": "sort-package-json && yarn prettify && yarn workspaces foreach --all --parallel --verbose run format",
1717
"postinstall": "husky || true",
@@ -34,7 +34,7 @@
3434
"@types/eslint": "9.6.1",
3535
"@willbooster/prettier-config": "10.2.4",
3636
"conventional-changelog-conventionalcommits": "9.1.0",
37-
"eslint": "9.39.1",
37+
"eslint": "9.39.2",
3838
"husky": "9.1.7",
3939
"lint-staged": "16.2.7",
4040
"micromatch": "4.0.8",

‎packages/shared-lib-blitz-next/package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -50,7 +50,7 @@
5050
"@willbooster/prettier-config": "10.2.4",
5151
"blitz": "3.0.2",
5252
"build-ts": "17.0.9",
53-
"eslint": "9.39.1",
53+
"eslint": "9.39.2",
5454
"eslint-config-flat-gitignore": "2.1.0",
5555
"eslint-config-prettier": "10.1.8",
5656
"eslint-import-resolver-typescript": "4.4.4",

‎packages/shared-lib-next/package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -49,7 +49,7 @@
4949
"@willbooster/eslint-config-ts": "11.4.12",
5050
"@willbooster/prettier-config": "10.2.4",
5151
"build-ts": "17.0.9",
52-
"eslint": "9.39.1",
52+
"eslint": "9.39.2",
5353
"eslint-config-flat-gitignore": "2.1.0",
5454
"eslint-config-prettier": "10.1.8",
5555
"eslint-import-resolver-typescript": "4.4.4",

‎packages/shared-lib-node/package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -56,7 +56,7 @@
5656
"@willbooster/eslint-config-ts": "11.4.12",
5757
"@willbooster/prettier-config": "10.2.4",
5858
"build-ts": "17.0.9",
59-
"eslint": "9.39.1",
59+
"eslint": "9.39.2",
6060
"eslint-config-flat-gitignore": "2.1.0",
6161
"eslint-config-prettier": "10.1.8",
6262
"eslint-import-resolver-typescript": "4.4.4",

‎packages/shared-lib-react/package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
"build": "build-ts lib",
3030
"build-storybook": "build-storybook",
3131
"check-all-for-ai": "yarn check-for-ai && yarn test",
32-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
32+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3333
"cleanup": "yarn format && yarn lint-fix",
3434
"format": "sort-package-json && yarn prettify",
3535
"lint": "eslint --color",
@@ -59,7 +59,7 @@
5959
"@willbooster/prettier-config": "10.2.4",
6060
"babel-loader": "10.0.0",
6161
"build-ts": "17.0.9",
62-
"eslint": "9.39.1",
62+
"eslint": "9.39.2",
6363
"eslint-config-flat-gitignore": "2.1.0",
6464
"eslint-config-prettier": "10.1.8",
6565
"eslint-import-resolver-typescript": "4.4.4",

‎packages/shared-lib/package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -49,7 +49,7 @@
4949
"@willbooster/eslint-config-ts": "11.4.12",
5050
"@willbooster/prettier-config": "10.2.4",
5151
"build-ts": "17.0.9",
52-
"eslint": "9.39.1",
52+
"eslint": "9.39.2",
5353
"eslint-config-flat-gitignore": "2.1.0",
5454
"eslint-config-prettier": "10.1.8",
5555
"eslint-import-resolver-typescript": "4.4.4",

0 commit comments

Comments
 (0)