The Glossary-First Prompt: Align on Terms Before You Ask for Code

If you use an assistant for coding, debugging, or docs, you’ve probably seen this failure mode: You ask for something “simple” and get a solution that’s technically correct — but not correct for your meaning of the words. Most of the time, it’s not a capability problem. It’s a vocabulary problem. Words like “fast” , “secure” , “migration” , “done” , “MVP” , “production-ready” , “idempotent” , or even “API” can mean very different things depending on the team, product, and constraints. The fix is a tiny habit that pays back immediately: The Glossary-First Prompt Before you ask for code, ask for a shared glossary . It sounds bureaucratic. It isn’t. It’s a 2–4 minute alignment step that prevents 30 minutes of rewrites. When it helps most Use this whenever: The task has ambiguous terms ("optimize", "scale", "secure", "clean") You’re interacting with a new codebase or domain You’re writing specs or tickets from a vague request You’re iterating on a prompt and outputs keep drifting The templ