rr-cursor-rules

cpf-rules.mdc

---
description: A set of high
globs: 
alwaysApply: false
---

# Your rule content

- You can @ files here
- You can use markdown but dont have to

git-rules.mdc

---
description: These are rules that govern git branching and git flow
globs: 
alwaysApply: false
---

# Git Branching and Git Flow

- branches and prs are managed using `gt`
- prs must include `[ENG-123]` ticket prefix in the title
- pr template is [pull_request_template.md](mdc:reprally/pull_request_template.md)
- pulls must always be rebased
- prs can be squashed
- prs must be no larger than 1000 SLOC
- branches follow the naming convention `jarad/some-feature/some-milestone/some-phase`
- pr branches follow the naming convention `jarad/PR-1-some-chunk`
- Common Project Framework (CPF) `docs` hub is an externally located repo `reprally-cpf`
- CPF repo `reprally-cpf` is symlinked to `reprally/docs`

typescript-rules.mdc

---
description: A set of strict coding standards that must be followed
globs: 
alwaysApply: true
---
# Typescript Rules

- no barrel files
- verbatimModuleSyntax is enabled
- prefer importing functions globally
- `*.test.ts`, not `*.spec.ts`
- all blocks must be wrapped in braces
- prefer strong-typing over loose-typing

yarn-package-test-rules.mdc

---
description: These rules dictate how to install packages and run tests
globs: *.test.ts, package.json
alwaysApply: false
---

# Server Yarn Package and Test

- use yarn, not npm
- use `--no-watch` flag when running tests
- use `yarn test packages/server/src/events --no-watch` to run tests
- use `vi` not `jest`
- unit tests live in their component's immediate `__tests__` folder
- event integration tests live in the root component test folder: `packages/server/src/events/__tests__`