Category naming conventions that scale
Descriptive vs creative, singular vs plural, numbered vs lettered, length and casing — the format decisions that keep category systems consistent as they grow.
Conventions are the boring decisions that make category systems feel effortless: singular or plural, numbered or named, descriptive or creative. Get them right once and every future category names itself. Get them wrong and every new category is a fresh argument.
Descriptive vs creative
Descriptive names say what is inside: "Kitchen Essentials", "Fixed Bills", "Active Drafts". They win wherever the category is a tool — budgets, folders, pantries, file systems. Creative names sell a feeling: "Little Luxuries", "The Weekend Edit". They win wherever the category is marketing — homepage collections, gift guides, seasonal drops. The mistake is mixing the two jobs: a pantry labeled "Little Luxuries" is a pantry you cannot find the cumin in.
Singular vs plural
Plural for containers that hold many things ("Spices", "Invoices", "Socks"); singular for concepts and single-purpose buckets ("Sale", "Emergency Fund", "In Progress"). Pick one rule for each context and never deviate — inconsistency here is the fastest way to make a system feel sloppy.
Numbered, lettered or plain
| Format | Example | Best for |
|---|---|---|
| Plain | Spice Jars | Most categories — cleanest to read |
| Numbered (01, 02) | 01 — Inbox, 02 — Active | Workflows and folders where order matters |
| Lettered (A, B, C) | Pantry A, Pantry B | Physical zones and shelves |
| Dated | Backups 2025 | Archives — date is the point |
Numbered prefixes force a sort order, which is exactly what you want for a Kanban board or a recipe workflow — and exactly what you do not want for a blog, where "01 — Recipes" looks odd next to "Travel". Use them deliberately.
Length and casing
One to three words. Title Case for display names ("Kitchen Essentials"); lowercase with hyphens for anything that becomes a URL slug ("kitchen-essentials"). Avoid ALL CAPS (reads as shouting), avoid excessive punctuation, and never put the year in a category name unless the year is the category — "Backups 2025" is fine, "Summer 2025 Collection" is a rename waiting to happen.
One pattern per set
This is the master rule. A category set is a family: "Bills", "Groceries", "Fun Money" works; "Bills", "The Epicurean Provisions Collection", "stuff" does not. When you add a category, check it against its siblings before you check it against your taste.
Write it down
For any system with more than a handful of categories — a store, a blog, a shared drive — keep a one-page naming guide: the pattern, singular/plural rule, casing, and three examples. Future you, and anyone who inherits the system, will follow it. The generator can produce candidates in bulk; the convention document is what turns candidates into a system.