liveBook · Manning

Prompt engineering

As explained in The Art of AI Product Development

Prompt engineering is the deliberate design and refinement of instructions provided to a generative model to elicit desired outputs.

A content-generation app may need to write for several clients, each with a different voice. Prompt engineering starts by changing the instructions given to a language model: asking for an “authoritative, professional tone” rather than a “friendly, approachable voice” can noticeably change a draft without changing the model itself. The useful question is not whether a prompt sounds clever, but whether it reliably produces content that meets a user’s need. section 5.4.3 section 6.0

A prompt can combine context, instructions, and examples. Start with a simple request, inspect the output, and add structure only where the task calls for it. Prompting is an empirical practice: a formulation that works for one task or model may not work for another. section 6.4.1 section 6.5

Choose a technique to match the difficulty or failure you observe:

  • Use a zero-shot prompt for a straightforward task; add examples with few-shot prompting when the task is more complex. section 6.5
  • Use chain-of-thought prompting for tasks requiring multiple steps, or reflection prompts to have the model review and improve an output. section 6.5
  • Try multiple prompt versions and select an output for a creative task; compress context and examples when token consumption becomes a concern. section 6.5

As a prototype approaches release, prompt changes need more discipline. Learn the model’s capabilities, limitations, and biases; compare outputs and errors; then evaluate changes rather than relying on a single good result. Reusable templates, version control, and collaborative prompt-management tools help a team track improvements, avoid duplicate work, and roll back changes that disrupt existing behavior. Continue adjusting prompts against real user interactions. section 6.4.1 section 6.4.2 section 6.5

Prompt engineering also shapes the product interface. An open conversation lets users make flexible requests, but many struggle to phrase requests in ways that work well for an AI model. A more graphical interface may be preferable when successful use would otherwise demand specialized prompting skills. Nontechnical teammates can still use prompts to prototype ideas and test them with users. section 3.3.1 section 2.3.2

Prompts are a useful first adjustment, not a complete reliability strategy. They cannot fully capture a distinctive brand voice or eliminate hallucinations. Retrieval-augmented generation can supply relevant information for accuracy, while fine-tuning offers another route to a particular style. Prompting remains important in retrieval-augmented generation, where it supplies context and frames questions for the model. section 5.4.3 section 7.0

How The Art of AI Product Development covers it

How deep it goes
Develops a practical progression from zero-shot prompts to examples, reasoning prompts, evaluation, templates, and version control rather than model internals.
Examples
Uses client blog-post tone instructions, content-app prompt management, and conversational versus graphical interfaces.
What it assumes
Starts with simple prompts accessible to nontechnical teammates while asking practitioners to learn their model’s capabilities, limitations, and biases.
What you can do after
Practice/perform iterative prompt design, compare outputs, and manage revisions collaboratively as an application matures.
How it connects
Links prompt engineering to conversational interfaces, retrieval-augmented generation, fine-tuning, and model evaluation.

Also explained in

Compare how 38 books explain prompt engineering →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Art of AI Product Development. The section links point to the parts of the book it draws on.