Skip to content

Commit 890c92f

Browse files
committed
Lessom 8
1 parent ed9fd21 commit 890c92f

File tree

2 files changed

+127
-616
lines changed

2 files changed

+127
-616
lines changed

website/docs/methodology/lesson-4-prompting-101.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ Provide your conclusions with evidence.
172172
- **Transparent execution**—You see exactly what happened at each step, making debugging straightforward.
173173
- **Essential for complex operations**—Modern models handle simple tasks without CoT, but multi-step operations (5+ steps) require explicit guidance for accuracy.
174174

175-
CoT is particularly powerful for QA workflows where you need methodical execution. See [Lesson 8: Tests as Guardrails](../practical-techniques/lesson-8-tests-as-guardrails.md#agent-debug-process) for a production example of CoT driving a debug workflow (lines 280-320).
175+
CoT is particularly powerful for QA workflows where you need methodical execution. See [Lesson 8: Tests as Guardrails](../practical-techniques/lesson-8-tests-as-guardrails.md) for production examples of using tests as guardrails in agent workflows.
176176

177177
## Applying Structure to Prompts
178178

@@ -286,7 +286,7 @@ Include unit tests validating the calculation.
286286
- **Prompting is pattern completion, not conversation**—Draw the beginning of the pattern you want the model to complete
287287
- **Skip pleasantries**—"Please" and "thank you" dilute signal without adding value
288288
- **Personas affect vocabulary, not capability**—Use them to bias toward domain-specific terms that improve grounding
289-
- **CoT paves a clear path**—Use explicit step-by-step instructions for complex tasks when you need control and accuracy; particularly effective for QA workflows (see [Lesson 8](../practical-techniques/lesson-8-tests-as-guardrails.md#agent-debug-process))
289+
- **CoT paves a clear path**—Use explicit step-by-step instructions for complex tasks when you need control and accuracy; particularly effective for QA workflows (see [Lesson 8](../practical-techniques/lesson-8-tests-as-guardrails.md))
290290
- **Structure directs attention**—Markdown, JSON, XML are information-dense and well-represented in training data
291291
- **Avoid negation**—State what you want explicitly; negation is easy to miss
292292
- **LLMs can't do math**—Have them write code that does math instead

0 commit comments

Comments
 (0)