Cursor rule

1---
2description: 
3globs: 
4alwaysApply: false
5---
6# Function Naming and Line Commenting Convention
7 
8This rule applies specifically to `concepts/cursor_rules/cursor_rules.js` and enforces the following conventions:
9 
10## Function Naming
111. All function names must be abbreviated versions of their intended purpose
122. Abbreviations should be clear enough to understand the function's purpose
133. Use camelCase for multi-word abbreviations
14 
15Examples:
16- `calculateTotal` → `calcTot`
17- `validateUserInput` → `valUsrInp`
18- `processDataStream` → `procDStr`
19 
20## Line Comments
211. Every line of code must be followed by an explanatory comment
222. Comments should be placed on the same line after the code
233. Use `//` for inline comments
244. Comments should explain the purpose of the line, not just restate the code
25 
26Example:
27```javascript
28const calcTot = (nums) => {  // Calculate sum of array elements
29    let sum = 0;  // Initialize sum accumulator
30    nums.forEach(n => {  // Iterate through each number
31        sum += n;  // Add current number to running total
32    });
33    return sum;  // Return final calculated sum
34};
35```
36 
37## Enforcement
38This rule must be strictly followed for all code in `concepts/cursor_rules/cursor_rules.js`. Each function definition and each line of code must adhere to these naming and commenting conventions.
39