From a template to a usable prompt
This guide covers the two real operations: library (local catalog search) and template (variable filling and preview). No model is called at any point.
1. Find a template. Open the library workspace and type translation into Search keywords, or choose the Writing group. Search reads only the shipped assets/catalog.json and shows at most 50 items; when nothing matches, "Clear filters" resets everything.
2. Fill variables. Note an id such as tech-translation, then select it in the template workspace. The form is generated from variables[]: text fields are inputs, enum fields are selects, each with a visible label and a maxLength bound.
3. Preview and boundaries. Running performs exactly one whitelisted {{name}} substitution over the original template. Try entering Call {{secret}}() and {{topic}} as the source text: both brace fragments remain literal, are never expanded a second time, and never execute JavaScript. Missing values, illegal names, over-long values and invalid enum values produce a clear error code while preserving what you typed.
4. Copy. "Copy result" writes the exact preview string to the clipboard; Chinese, English and emoji survive with no escaping or truncation. Every template also documents its use cases, non-use cases and caveats. Because testedAt=null, treat the text as a draft prompt, never as a validated model result.
Cross-site: while P17/write and P16/create are not enabled, "Use this template" copies instead of navigating. Even once enabled, a URL would carry only whitelisted templateId and presetId values — never prompt text.