Write comments that make Cursor's Tab complete the way you actually want

COMMENT STYLE FOR THIS FILE — Form validation helpers for the signup flow

Write comments as forward-looking intent statements immediately above the line they describe, not as after-the-fact descriptions of code already written. State what happens next before writing it — that's what a predictive completion reads to guess the following lines.

NAMING CONVENTIONS TO FOLLOW SO COMPLETIONS MATCH THEM
Boolean validators are named isX (isValidEmail, isStrongPassword); error messages are named xError (emailError).

EXAMPLES OF THE COMMENT STYLE TO MATCH
// check password length before checking character variety
const hasMinLength = password.length >= 8

RULES
- One comment per logical step, not one per line.
- Name the next variable or function before it appears — e.g. "// validate email" immediately before assigning to isValidEmail — so a completion suggesting isValidEmail is reading stated intent, not guessing from indentation.
- Don't leave a bare TODO with no reason; a TODO with nothing after it gives a completion model nothing to extend correctly.
- Keep the file's existing terms consistent — don't introduce a synonym for a concept the file already names something else, since a completion model weights whichever term appeared most recently in the file.