chapter three

3 Prompt Design: Linguistic Elements

 

This chapter covers

  • Using Precision to balance implementation reliability and creative range
  • Using Directness (implicit vs explicit instructions) to steer exploration and execution-oriented outputs
  • Using Brevity to reduce unnecessary token cost while preserving output quality
  • Using tone, framing, and format as secondary refinements for communication alignment

You defined the task clearly, added context, specified the output format, and the model still returned something too generic to act on, or an open-ended exploration when you needed a decision, or no better result than a one-line prompt would have given. You revise the prompt, but nothing in the structure tells you what to change. The gap is in how the prompt is expressed.

Linguistic Elements govern how the prompt is expressed: how specific the requirements are, how explicit the instruction style, and how concise the wording.

  • Precision: controls how specifically you state requirements, so the model has less room to interpret the task.
  • Directness: controls whether instructions are implicit (indirect) or explicit (direct).
  • Brevity: controls how much wording you use to get the output you need.

Together, they replace trial-and-error revision with targeted adjustment: when output falls short, each element points to a distinct cause.

3.1 Precision

3.1.1 Practical Example 1: API Migration Notice

3.1.2 Practical Example 2: Sequence Diagram Generation

3.2 Directness

3.2.1 Practical Example 1: Backend API Change Review

3.2.2 Practical Example 2: Flaky CI Test Strategy

3.3 Brevity

3.3.1 Practical Example 1: Incident Summary Analysis

3.3.2 Practical Example 2: Technical Diagram Generation

3.4 Additional Linguistic Considerations

3.4.1 Hands-On Practice

3.5 Summary