Pathwise

Manuals / Prompt Engineering / Chapter 11

C · Production · advanced · ~40 min · Chapter 11 of 12

Team libraries, versioning & privacy

Prompts at scale need ownership, changelogs, and privacy review. Never paste secrets, PII, or proprietary code into public models.

Path progress
88%

Step 1 of 2

Prompt README

Purpose, owner, version, eval score, known failures, change log. Treat like API docs.

Prompt READMEDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Prompt READMEdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Write a README for one team prompt. Include eval score and last tested date.

Was this step clear?
Chapter learning outcomes
  • Prompt versioning
  • Team workflows
  • Privacy & compliance

Clear these before you leave

Side quest

Team contribution

Propose adding one prompt to a shared library with eval results.