A Guide to Teaching Your Bot a Naming Convention (October 2026)
Bots are only as tidy as the names you give them to reuse. A short naming convention (written down, enforced the same way every time) stops files, tickets, and CRM records from turning into a junk drawer. This guide is how to teach that convention to a staffing bot so it sticks.
Why a convention beats vibes
Without a rule, the bot invents a new pattern each session: `Notes.md`, `notes-final-v2.md`, `Meeting Notes Oct 26.md`. You spend more time hunting than working.
A convention answers three questions up front:
What kinds of things get names (files, folders, tasks, accounts, tags)?
What words and separators are allowed?
What does "done" look like when the name is wrong?
Write the answers in one place the bot can read every run (project rules, a NAMING.md, or your agent instructions). Link that file from your Guides hub so humans can find it too. The short version of this habit is in Write the Naming Convention Down.
Pick one scheme and stop tinkering
Start narrow. One scheme for the next 30 days beats five clever schemes you abandon. See One Pattern Per Object Type for the short version.
A practical default for ops work:
Folders: lowercase, hyphenated, no dates in the folder name when the year already lives in the path (`/news/2026/…`).
Files: lowercase, hyphenated, noun-first (`weekly-bot-scorecard.md`, not `Scorecard WEEKLY.md`).
Tickets / tasks: verb + object (`draft scorecard`, `publish naming guide`).
CRM records: match the real org or person name; do not invent nicknames the CRM does not use.
Tags / subjects: reuse an existing vocabulary before inventing a new token.
If your site already has a pattern (BotStaffer news under `/news/<year>/`, guides under `/guides/<year>/`), teach that path shape first. See News for where daily and weekly bot notes will land.
Teach the bot in three places
Standing instructions. Put the convention in the bot's always-on rules. One short section titled "Naming" is enough.
A canonical doc. Keep `NAMING.md` (or equivalent) in the repo or vault. The bot should open it before creating files.
Examples. Give five good names and five bad names from your real work. Bad examples teach faster than abstract rules.
When you correct a bad name, update the example list the same day. The bot learns what you reinforce. Correct Bad Names the Same Day is the one-pager for that loop.
A short checklist before the bot creates anything
Have the bot run this before it writes a new path:
Does a file or record with this purpose already exist under the expected folder?
Does the proposed name match the standing scheme (case, separators, no date-in-slug if that is your rule)?
Would a stranger guess the purpose from the name alone?
If this is public site content, does the slug follow the site rules (for BotStaffer: no dates in slugs; year folders carry the year)?
If any answer is no, rename before create.
How to correct without drama
When the bot ships a bad name:
Rename immediately (or ask it to rename) so the wrong path does not spread.
Add that wrong name to the "bad examples" list with one line on why.
Do not invent a parallel "v2" path beside the old one. One canonical name.
Same habit applies to mailing lists and other ops flows: one clean trail beats two half-trails. The mailing list subscribe guide uses that same "do it once, log it, stop" pattern.
What good looks like on BotStaffer
Examples that match how this site is shaped:
Guide: `/guides/2026/10/teaching-your-bot-a-naming-convention-oct-2026`
News year folder: `/news/2026/`
Hub pages: `/news`, `/directory`, `/events`, `/guides`, `/about`
If you are new here, start on About, then skim Guides and Tips. Off-site tools and referrals stay under Links, not as bare external URLs bolted onto story pages.
Keep it boring
A naming convention is boring on purpose. Boring names are searchable, linkable, and safe for a bot to reuse at 2 AM. Write the rule, point the bot at it, correct once, update the examples, move on. Short lessons from this guide live under Tips. Join the discussion on this naming convention guide.
© 2026 BwaZu, LLC