You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .cursorrules
+14-1Lines changed: 14 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -53,4 +53,17 @@ Always use conventional commit format for all commits and PR titles:
53
53
- Use the body to explain what and why vs. how
54
54
- Wrap the body at 72 characters
55
55
56
-
When creating PRs, always follow this conventional commit style for both the commit messages and PR titles.
56
+
When creating PRs, always follow this conventional commit style for both the commit messages and PR titles.
57
+
58
+
## Principles
59
+
The following list of principles should be honoured when introducing changes:
60
+
- always check what's the best practice in the industry
61
+
- raise with the user if there is a package out there that is a 80-90% fit instead of writing from scratch
62
+
- always clean up after changes
63
+
- focus on root cause instead of fixing symptoms
64
+
- trace changes applied locally and in-branch against main when debugging issues locally to first understand if it's a pre-existing bug
65
+
- do not come up with new requirements or alter requirements by yourself. Propose alternatives first.
66
+
- follow the same architecture pattern in the repo. If there is significant benefit to do things differently, raise it first.
67
+
- when refactoring, check if any existing functionality has been changed/broken or new functionality has been added. if inevertible, call it out.
68
+
- always check or ask if a problem/bug exists after certain changes. trace back and find all the changes applied in between and use that as scope for debugging.
69
+
- when coming up with a fix, keep going after the first layer of root cause until you can reason about the entire data flow/userflow is sound.
message: "❌ Failed to publish SDK version ${{steps.release.outputs.RELEASE_NAME}} to NPM. ${{ github.triggering_actor }} please check the logs for more details."
0 commit comments