Choose global or project scope
Global prompts are reusable across work. Project prompts belong to one project’s language, constraints, and workflow.
Project prompts belong to one project’s language, constraints, and workflow.
Name prompts by outcome
Use names such as Client brief review or Release-risk scan instead of Prompt 4.
Use variables carefully
Variables such as project, file, task, audience, and output format make a prompt reusable without hiding what will be sent.
Attach only necessary context
A reusable prompt should not automatically include every project file or private note.
Capture the result
When a prompt produces something valuable, save the output as an artifact, decision, note, or next action.
NEED A GUIDED ANSWER?
Ask LobeWork about this guide.
The support assistant uses the same published guide library and will link you back to the most relevant article.
WAS THIS GUIDE HELPFUL?Help us improve the documentation.