Job Resiliens
← More from the Knowledge Hub
Job Resiliens · Knowledge Hub · By Anurodh Arun Gupta

Five Prompting Habits That Actually Change Claude's Output Quality

The advice to "just be clear" about what you want from an AI assistant is true but not specific enough to actually change anything -- these five habits are the mechanical version of clear.

Naming a role, a goal, an output format, and a constraint in the same request does more work than any one of those four alone -- "as a hiring manager, review this resume for a data analyst role, and return three specific gaps in bullet-point form" gives a model a lens to read through, a target, a shape for the answer, and a boundary, instead of leaving all four to guesswork. For a genuinely complex prompt mixing instructions, background material, and the actual content to work on, wrapping each piece in a simple tag -- something like instructions, context, and output -- keeps the model from confusing your directions with the material you handed it to process, a real and well-documented source of confused output on longer prompts.

Asking a model to reason step by step before giving a final answer measurably helps on math, multi-part logic, and strategy questions specifically -- it is not free for every task, but it is close to free for the tasks where a wrong first-instinct answer is genuinely likely. The same logic applies to giving one concrete example of the output you want rather than only describing it in words: showing beats telling, especially for tone, format, or style that is hard to fully specify in a sentence. And naming an exact output length or shape -- "three sentences, under twenty words each" rather than "keep it short" -- removes an entire category of back-and-forth, since "short" means something different to a model than it does to you.

Extended thinking, a real setting that gives a model more room to reason before answering, is worth turning on specifically for complex coding, multi-step math, or strategic analysis, where the first-instinct answer is genuinely likely to be wrong -- it adds real latency and cost, so switching it on by default for simple classification or formatting tasks pays for reasoning depth the task never needed. Artifacts, a real feature that generates a live, interactive output such as a working webpage, a chart, or a small interactive tool instead of plain chat text, is the right call whenever what you actually want is a thing to look at or use, not a paragraph describing it.

The single highest-leverage habit is structural, not stylistic: separate your instructions from your source material explicitly, name the exact shape of the output you want, and reserve the more expensive settings -- extended thinking especially -- for tasks that actually need the extra reasoning depth.

Based on Anthropic's documented prompting guidance (role/format/constraint framing, tag-based structuring, chain-of-thought prompting) and real, current Claude features (extended/adaptive thinking, Artifacts).

in X f WhatsApp Email

Get your own AI exposure score

Two minutes, free — see how exposed your specific role is and what to do about it.

Get your AI Vulnerability Score