Prompt Management

purple prompts summary prompts in purple hub are defined via a custom post type (similar to create a custom post type in hub ) therefore, you can find them near the top of the left side menu in the purple hub and can manage them similarly to how posts are managed overview clicking on 'purple prompts' (1) > 'all prompts' (2) shows the list of all prompts defined in your purple hub editing when editing a prompt, you find no block editor, but instead a simple text box next to some additional settings the text box is used to define the prompt, and you can use placeholders to add e g the post content into the prompt at the fitting location on the right side, you need to define firstly the intended usage area for this prompt the prompt can then be used for this feature only as an example, this prompt here asks for a specific tone and style of the post title, and therefore it should only be used for the title generation feature (see generating meta information docid\ iglmj p1d83iqje2nghqd ) and not e g article rewriting below that a setting that affect the language model itself temperature this controls the "creativity" of the model a higher temperature results in a more diverse and creative output, while a lower temperature makes the output more deterministic and focused (read more here , or dive into technical details here ) below that options for how the prompt is used use for finalize article if this toggled on, then the prompt is included in the prompt sequence that is activated when the user clicks finalize article button in the purple prompt sidebar prompts that have the usage 'rewrite article' cannot be included in the finalize article sequence use prompt for standard a prompt is available for all article (post) types, this field therefore can be left empty however, when a prompt is only usable for selected article (post) types, (e g only online variants, not print variants) then multiple post types can be selected here saving 'saving' (1) a prompt makes it available for all editors if a prompt gets moved to the trash, it can not be used for its configured use case and will not be shown there this can be helpful when you want to experiment with many different prompts and clean up afterwards without permanently deleting the prompts