// docs / patterns
Don't start from a blank page.
The pattern library is a set of prompt structures that hold up in practice. Each one is a {{variables}} template you copy into your own library and adapt.
Browsing patterns
/patterns is public, so no account is needed. Each card shows the structure (chain-of-thought, few-shot, structured output, critique-then-revise, and more), when to reach for it, and the full template with its {{variables}} marked.
From pattern to working prompt
1. /patterns → pick a structure → Copy template
2. Dashboard → New prompt → paste → Commit
3. The {{variables}} become a fillable form on copy
(web, extension, and ple copy --var all fill them)Because templates use variables, the pattern stays reusable after you adopt it: the structure is fixed, the specifics are filled per use. Commit your adaptation and it's versioned like everything else, so you can always diff back to where you started.
Why patterns, not examples
Example prompts age fast; structures don't. A few-shot scaffold or an explicit-output-format block survives model upgrades better than any clever wording. When a pattern stops pulling its weight, run it through Loop against your own agent and let the results decide.