Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .cursor/rules/general.mdc
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ alwaysApply: true
- Do not write tests unless explicitly requested.
- 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.
- 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 current branch using the `--no-verify` option and push to the current branch.
- 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>`.
- Always create new commits. Avoid using `--amend`.
Expand Down
4 changes: 4 additions & 0 deletions .yarnrc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,10 @@ npmPreapprovedPackages:
- '@willbooster/eslint-config-ts-react'
- '@willbooster/prettier-config'
- '@willbooster/wb'
- next
- '@next/*'
- react
- react-dom

plugins:
- checksum: d387bf474c315e463ddcbda77aabda9ba0b28ab3723fccccf40a310a3225d073963841bc255b2d2d8de9c1111548a7308b6af27eb31db57c75c4b9cb05aea73e
Expand Down
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
- Do not write tests unless explicitly requested.
- 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.
- 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 current branch using the `--no-verify` option and push to the current branch.
- 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>`.
- Always create new commits. Avoid using `--amend`.
Expand Down
2 changes: 1 addition & 1 deletion CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
- Do not write tests unless explicitly requested.
- 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.
- 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 current branch using the `--no-verify` option and push to the current branch.
- 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>`.
- Always create new commits. Avoid using `--amend`.
Expand Down
2 changes: 1 addition & 1 deletion GEMINI.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
- Do not write tests unless explicitly requested.
- 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.
- 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 current branch using the `--no-verify` option and push to the current branch.
- 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>`.
- Always create new commits. Avoid using `--amend`.
Expand Down
Loading