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 https //app archbee com/docs/ pqaippaejjusq2q91mg9/moptb53ayy9mwv1xi0nmo#irezycxiwpidesu6tiz k ) 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 generate meta information docid\ iglmj p1d83iqje2nghqd ) and not e g article rewriting 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 rewrite article when "use prompt as" is set to rewrite article , one additional setting appears disable editing prompt in editor when enabled, editors can select and run this prompt as usual, but they neither see its prompt text nor can they adjust it beforehand in the purple prompts sidebar, the text field and the 'edit' button are not shown for this prompt (see rewriting articles docid\ vdlzy5nwvpecu3lrb1xkg ) use this for prompts whose wording has to stay exactly as defined, for example a house style or spelling correction prompt that should be applied identically by everybody when the setting is off (the default), the prompt behaves as before editors see its text in the sidebar and can adapt it spontaneously for a single rewrite generate taxonomy terms when "use prompt as" is set to generate taxonomy terms , three additional settings appear taxonomy select which wordpress taxonomy this prompt targets — for example tags , categories , or any other public taxonomy registered in the system provide existing terms to ai when enabled, all existing terms of the selected taxonomy are included in the prompt sent to the ai this is useful for classification tasks where the ai should pick from a defined list rather than invent terms freely ⚠️ for taxonomies with hundreds or thousands of terms, this significantly increases prompt length and therefore execution time and api cost allow creating new terms when enabled, the ai may suggest terms that do not yet exist in the taxonomy, and those terms will be created automatically when applied when disabled, the ai is instructed to only use existing terms, and any non existing terms it tries to assign will be discarded g enerate dam media metadata generate dam media metadata is used by the ai metadata suggestions in purple dam selecting this usage area reveals a dam metadata field selector for the field this prompt is responsible for next to the four standard fields (title, alt text, description, caption) it lists this site's generatable media fields, prefixed so they are easy to tell apart acf {field label} for an acf field on media files and taxonomy {taxonomy label} for a taxonomy assigned to media you normally do not create these prompts by hand purple creates one prompt per generatable field (named "dam metadata ") when the ai metadata generation toggle in settings ❭ media ❭ general is switched on, seeded with a default instruction the usual workflow is to edit those deleting one opts its field out of generation, and it is not recreated — see uploading media docid\ xcdxtroopsufsgyarvq1m for a prompt whose target is a taxonomy, the provide existing terms to ai toggle can be enabled so the taxonomy's current terms are sent along as context, which makes the ai pick terms that actually exist allow creating new terms is deliberately not offered here dam metadata generation only ever selects existing terms 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