A Short Guide to Component Naming

1. Brevity is Key

Names should be short, but never cryptic. A good rule is: if a new engineer can understand it in context without asking, the name is likely good.

Prefer BillingAddressForm over BAF, and ProjectSettingsModal over PSM. You optimize for team speed, not typing speed.

2. Rank High in Search

Use names that match the domain language your team uses in tickets and product docs. This makes searching the codebase far easier.

Instead of generic names like ItemCard, prefer intent-rich names like InvoiceCard or SubscriptionPlanCard.

3. Mix Languages

Pick one naming language for code and keep it consistent. Most teams choose English for interoperability across tooling and documentation.

You can still support multilingual teams through clear comments, strong docs, and shared glossary terms in your product documentation.