naming-cheatsheet

Structure function names as prefix + action + high context + low context, such as getUserMessages or shouldDisplayMessage. The action is a verb like get or handle, high context is the main entity, and low context adds optional specificity.

Use remove when taking something out of a collection, paired with add. Use delete when permanently erasing something from existence, paired with create. For example, removeFilter filters an array while deletePost erases a database record.

Use is for characteristics or state (isEnabled), has for possession of a value (hasProducts), and should for positive conditionals coupled with an action (shouldUpdateUrl). Avoid forms like isProductsExist in favor of hasProducts.

No, the use prefix is reserved for React hooks that call other hooks. Naming a plain utility useHasDifferentBillingAddress is misleading; name it hasDifferentBillingAddress instead so linters and readers do not treat it as a hook.

Duplicating context creates redundant names like MenuItem.handleMenuItemClick. Since the class already provides context, handleClick reads naturally as MenuItem.handleClick and keeps names short without losing meaning.