Name things the way your business already talks

When I describe a tool to Claude Code, I use the exact words my team already uses for a client, a job, a status, a stage. Not generic labels a coding tutorial would use.

If your tool calls something a "record" and your team calls it a "job," you'll spend energy translating in your head every time you look at it. Matching your own language makes the tool easier to trust, easier to explain to a new hire, and easier to check for mistakes, because the words on the screen already mean something to you.

Try this today: before your next build, list the five or six words your team uses most for the thing this tool touches, and tell Claude Code to use those exact words throughout.

• what you call the customer
• what you call the job or order
• what you call each stage it moves through