vocabularylisted

# Writing a jit-context entry **The test:** an entry loads, and the reader still gets it wrong. Then the entry failed. It is a cheat sheet, not a reminder — exact command, exact path, exact pattern. Never "go look it up". ## 1. Pick the dimension first — this is the whole decision | Dimension | Fires on | Use when | | --- | --- | --- | | **paths** | a file path in the tool call | knowledge belongs to a *folder* — "before you touch this, know X" | | **tools** | tool name + command pattern | you want to intervene *before a specific call runs* | | **vocabulary** | keywords in the prompt | a *domain* the user names out loud | **Default to paths.** The folder is the situation. Keywords fire on what someone is talking about; paths fire on what they are touching, and the expensive mistakes happen while touching. **Measured noise, one session:** `folder` pulled a Google-Drive entry, `time` pulled activity reports, `property` pulled a real-estate client module, `setup` pulled a preproduction monitor. Four injections, four irrelevant, thousands of tokens. Every one was a *keyword* match. Zero path matches misfired. **Use tools when the fix is an interception**, not information: a `require` that fails the call is worth more than a paragraph that gets skimmed. Evidence: a `| head` reminder existed, in bold, said aloud twice — and was violated three times in six hours. A `mode: block` rule was not. ## 2. Frontmatter ```markdown --- title: "Short, states the rule not the topic" mat