phoenix-typescript

Booleans must use verb prefixes like isAllowed, hasError, or canSubmit, and functions must start with an action verb such as getUser or normalizeTimestamp. Single-letter variables are banned, and complex conditions should be extracted into named booleans.

Functions with two or more parameters should use object destructuring instead of positional arguments, documented with JSDoc @param dot notation. This keeps call sites readable and resilient to parameter reordering.

Without noUncheckedIndexedAccess, a Record lookup is typed as V but returns undefined at runtime for missing keys. Use Partial<Record<K, V>> or Record<K, V | undefined> so every access site is forced to handle undefined.

No, any is banned; use unknown and narrow explicitly with type guards. If any is genuinely unavoidable, such as interfacing with an untyped external API, add a comment explaining why.

Use path imports like import debounce from "lodash/debounce" rather than barrel imports from "lodash". Barrel imports defeat tree shaking, so bundles end up carrying unused utilities.

Expose ambient values like Date.now() or new Date() as optional parameters whose defaults are the constant, prefixed with DEFAULT_. This keeps the function pure so tests can pin the inputs and predict the output.