— name: word-finder description: Teach the user the precise term the user is reaching for. Use whenever the user describes something in a roundabout or struggling way and an established word or phrase names it, or when the user asks for the word for something. Answer the actual request too; the term is a short add-on. — # word-finder The user often explains an idea in several sentences when one precise term exists. Give the user that term to use next time: in prompts, docs, commits, and conversations. ## When to offer a term Offer one when all hold: - The user described a concept indirectly, with effort, or said the word is missing. - An established term names it (widely used in the field or in plain English, not one you coin). - The term is not already in the user’s message. Skip it when the description is already short and precise, when the match is loose, or when you already taught the same term this session. ## Output Do the requested work first, or alongside. Then add one short block: Word you're looking for: **greenfield codebase** = new project with no legacy users or code to stay compatible with, so you can design cleanly. Use it: "This is a greenfield codebase: no backward compatibility, no legacy shims." Related: pre-launch, no-compat, breaking changes allowed Rules: - One main term. Add 1 to 3 related or near-miss terms only when each sharpens the meaning (say how each differs in a few words if it is not obvious). - The definition is one line, in the user’s context, not a dictionary entry. - The usage line is a sentence the user could paste into a prompt or message today. - If the closest term only partly fits, say so: “closest term: X (but X usually also implies Y)”. - If the user asked only for the word, the block is the whole answer. ## Examples User says: “code is new, not launched, don’t keep backward compat for legacy stuff, reorganize clean” Term: greenfield codebase (related: pre-launch, no-compat break) User says: “the text sounds weird, too formal and stiff, like a robot or a school essay, not how a person actually talks” Term: stilted (related: wooden, stiff; not purple prose, which means flowery) User says: “check it really hard, every detail, assume it’s wrong and try to break it, don’t just skim and say looks good” Term: rigorous review (related: adversarial review, which tries to break it; not a sanity check, which is a quick surface pass) User says: “make it look exactly like the real thing, every detail, not a rough sketch or placeholder boxes” Term: high fidelity (related: pixel-perfect, which matches a design exactly; not low fidelity or a wireframe, which is a rough layout)
submitted by
/u/RisaPulseance
Originally posted by u/RisaPulseance on r/ClaudeCode
You must log in or # to comment.