From Scenario Templates and the Prompt Plaza to a Private Workspace

Scenario templates provide structure, the Prompt Plaza contains intentionally published work, and the private workspace holds personal material under a different visibility boundary.

Three surfaces with different responsibilities

Scenario templates, the Prompt Plaza, and the private workspace all involve prompts, but they are not one shared content pool. Templates provide editorially prepared task structures. The Plaza helps people discover work that authors intentionally publish. The workspace contains personal drafts, uploads, generations, and versions. Keeping these responsibilities separate prevents “I can browse this” from turning into “my private work must also be public.”

The product navigation at https://lingmofang.com/ connects these surfaces. Before running a prompt, users should still check the live model capability page. A public template can remain useful for a long time while the models capable of running it change.

Templates are starting structures, not final answers

A scenario template solves the blank-page problem by reminding a user to define an audience, source, format, and exclusions. It must still be adapted. Replace every variable, remove irrelevant sections, and verify that its claims fit the present task. A writing framework cannot become a production incident conclusion without evidence. A marketing framework must not promise features that are not available.

The official site already contains detailed templates and tutorials. An AppHub product guide should explain how to navigate the system rather than duplicate those pages. Use official content when a concrete writing pattern is needed; use the private workspace when personal context, generation, comparison, and history are required.

The Plaza contains intentional publications

The Prompt Plaza is a discovery surface, not a mirror of private drafts. A prompt should appear there only after an author takes an explicit publishing action. Generating, saving, comparing, or versioning private work does not create a public URL. People adopting Plaza material must check its source, suitability, and safety boundaries; popularity is not evidence that every claim is accurate.

Before publication, make a dedicated public copy. Replace customer names with variables, remove internal metrics, access tokens, private URLs, and unreleased plans, and ensure examples do not leak source documents. Explain what another user must supply and where human review is required. Some prompts depend so heavily on confidential context that they should not be published at all.

The workspace supports real iteration

The private workspace is appropriate for incomplete requests, controlled source material, and multiple generations. A user can start from a template, add relevant context, run a currently enabled model, compare candidates, and save a version. “Private,” however, does not remove the need for data minimization. Unnecessary personal information should still be excluded, and third-party processing, retention, deletion, and legal obligations should be reviewed in the current privacy policy.

The workspace is also not an automatic executor. A coding suggestion does not commit to Git. Image or video reverse engineering does not create finished media. Campaign copy does not publish itself. Lingmo prepares and evaluates prompt work; accountable actions happen in the systems designed for them.

A simple routing rule

Use a template when you need structure, visit the Plaza when you want to study intentionally public work, and move into the workspace when the task requires private sources, generation, comparison, or versions. Free use does not promise permanent unlimited quota. Membership does not renew automatically, and policy refusals carry no quota charge. A template should never rewrite those live product rules into a more dramatic claim.

Will my adaptation enter the Plaza when I use a public template?

No. Copying a public structure into a personal workflow does not publish the resulting prompt or attachments. Private work remains private unless the user deliberately chooses to publish. Even then, create a redacted copy and confirm that every piece of text, image, and video information is safe and authorized for public use.